I'm currently testing our application on android 15 (one ui beta) on the Samsung RTL and the FCM library seems to be unable to retrieve a Firebase Token from Google on this version. I always get this exception "java.util.concurrent.ExecutionException: java.io.IOException: AUTHENTICATION_FAILED". Tested on a S24 in Korea. If tested on Android 14, it's working just fine. I also cannot test this on an actual device since my location isn't part of the OneUI territories.
Thanks for sharing the details of your issue. The problem youāre encountering with the FCM library and the inability to retrieve a Firebase Token on Android 15 (One UI Beta) could be due to compatibility issues between the beta software and Firebase services. Here are some steps and considerations to help troubleshoot:
1. Check Google Play Services Version:
Ensure that the version of Google Play Services on the Samsung RTL (Remote Test Lab) matches the minimum version required by Firebase for Android 15. Beta firmware may sometimes have mismatched or incomplete Play Services components.
2. Verify Firebase SDK Version:
Make sure youāre using the latest version of the Firebase SDK. Check the release notes to confirm compatibility with Android 15 or report the issue to Firebase if itās not yet fully supported.
3. Inspect Network Configuration:
The "AUTHENTICATION_FAILED" error might be related to network restrictions or configurations on the RTL. Verify that the device has full internet access and that no restrictions (like proxies) are interfering with token retrieval.
4. Test on Emulator:
Since you canāt test on a physical device due to regional restrictions, try testing on an Android 15 emulator with the same app and Firebase configuration. This can help determine if the issue is specific to the Samsung RTL or the Firebase SDK.
5. Submit a Bug Report to Samsung and Firebase:
If you believe the issue is related to the One UI beta, submit a detailed bug report through Samsung's developer channels. Include logs, exception details, and the steps to reproduce the issue.
Similarly, report the issue to Firebase support to ensure they are aware of any compatibility problems with Android 15.
6. Workaround for Testing:
If immediate testing is critical, consider downgrading the Firebase library to an earlier version to see if it bypasses the authentication issue temporarily. Alternatively, try testing on Android 14 devices/emulators until Firebase or Samsung addresses the issue.
The One UI beta environment can sometimes introduce unexpected challenges, especially for libraries like FCM that depend on external services. Your feedback is crucial for both Samsung and Firebase to address these compatibility gaps before the stable release. Let us know if any of these suggestions help or if you need further guidance!
Thanks for sharing the details of your issue. The problem youāre encountering with the FCM library and the inability to retrieve a Firebase Token on Android 15 (One UI Beta) could be due to compatibility issues between the beta software and Firebase services. Here are some steps and considerations to help troubleshoot:
1. Check Google Play Services Version:
Ensure that the version of Google Play Services on the Samsung RTL (Remote Test Lab) matches the minimum version required by Firebase for Android 15. Beta firmware may sometimes have mismatched or incomplete Play Services components.
2. Verify Firebase SDK Version:
Make sure youāre using the latest version of the Firebase SDK. Check the release notes to confirm compatibility with Android 15 or report the issue to Firebase if itās not yet fully supported.
3. Inspect Network Configuration:
The "AUTHENTICATION_FAILED" error might be related to network restrictions or configurations on the RTL. Verify that the device has full internet access and that no restrictions (like proxies) are interfering with token retrieval.
4. Test on Emulator:
Since you canāt test on a physical device due to regional restrictions, try testing on an Android 15 emulator with the same app and Firebase configuration. This can help determine if the issue is specific to the Samsung RTL or the Firebase SDK.
5. Submit a Bug Report to Samsung and Firebase:
If you believe the issue is related to the One UI beta, submit a detailed bug report through Samsung's developer channels. Include logs, exception details, and the steps to reproduce the issue.
Similarly, report the issue to Firebase support to ensure they are aware of any compatibility problems with Android 15.
6. Workaround for Testing:
If immediate testing is critical, consider downgrading the Firebase library to an earlier version to see if it bypasses the authentication issue temporarily. Alternatively, try testing on Android 14 devices/emulators until Firebase or Samsung addresses the issue.
The One UI beta environment can sometimes introduce unexpected challenges, especially for libraries like FCM that depend on external services. Your feedback is crucial for both Samsung and Firebase to address these compatibility gaps before the stable release. Let us know if any of these suggestions help or if you need further guidance!
