-
-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
16.1.5: Androidx error -> crash #29
Comments
@m1ga tried to rebuild all fcm modules: (core, analytics, cloudmessaging) with ti.playservices 1.16.5 - but finding same crash as you. With playservices 1.16.4 or 1.16.3 I'm running into dreaded: Token retrieval failed: SERVICE_NOT_AVAILABLE on Android 7 / 7.1 Hopefully 1.16.5 will fix that, but we should find a way to get things rolling. My apps currently hang on Android 7/7.1 :( |
My case had been fixed with help of @m1ga (using 16.1.4) |
Same with maps btw: Failed resolution of: Landroidx/fragment/app/Fragment;
|
The new play-services libs (17+) seem to be having dependancies on androidx libraries. Better to not use 17+ libs for now. You can check the dependancies here: https://mvnrepository.com/artifact/com.google.android.gms/play-services-base/17.1.0 vs 16.1.0: https://mvnrepository.com/artifact/com.google.android.gms/play-services-base/16.1.0 better to delete the 16.1.5 release of the module |
@jquick-axway I saw the new PR for SDK 9. Can we have a working version for SDK <= 8. So not 16.1.5 (androidx error) but a 16.1.4 without the ads-lite library. Currently the last two released version don't work |
I was testing 16.1.5 today with my FCM test app. It will crash with:
I'm not sure if I need to recompile FCM modules with newer playservice libs or if there is any androidx component inside the libs of ti.playservice 16.1.5 that are not supported (the error points to ArrayMap). So currently the best version to use is 16.1.4 and remove the ads-lite lib.
The text was updated successfully, but these errors were encountered: