-
Notifications
You must be signed in to change notification settings - Fork 504
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
Mapbox Android 8.5.0 unstable #263
Comments
@m0nac0 here is the log I am getting
|
Thank you for providing the log, have you tried running |
I suppose that 8.5.0 update was pushed to the same 0.0.5 verison of the mapbox_gl library in flutter, because some time ago everything was working. A few variables that, supposedly, changed - Android Studio update and Flutter could have released some minor updates too. I run via Android Studio and I suppose they are using appbundle there already. |
I'm not sure if I understand you correctly, but v0.0.5 of this plugin has come with Mapbox Android SDK 8.5.0 since December 21, 2019, when v0.0.5 was released on pub.dev |
I see. Then either Android Studio update, or flutter or something else in the ecosystem started causing the problem, because I am sure that somewhere in March map was not crashing for me on the Android emulator. |
Just to make sure, are you on flutter version 1.12.13+hotfix.9 from the stable channel? And do you now if you updated flutter since it last worked? |
At the moment I am on 1.12.13+hotfix.8 on stable. |
Could you still try what I suggested above, please? |
@m0nac0 I can try, but at very best it would solve the issue with local testing. I have the same problem when deploying appbundle to the real device, so I assume problem will also be there in Play Store - already trying to test, but google is very slow to review |
@m0nac0 Google have just reviewed my app and I can confirm that crash is there on real device when installed via Google Play. I was uploading appbundle to them, so they should have repackaged it to the proper device requirements. |
@AAverin I'm not sure whether the usage of appbundle really makes a difference, because I think the bundletool just e.g. includes whatever *.so file is in the ARM folder in the appbundle and doesn't actually check whether that lib is really compiled for an ARM architecture. But I suspect that the reason for the error is that flutter from the beginning on somehow mixes up the *.so files. |
I am using X86 emulator. |
@AAverin Thank you, I'm afraid though that at this point we can't really do anything here in the flutter plugin to solve this. |
@m0nac0 Should this issue be escalated to Mapbox Android SDK, rather? It is the one that uses SoLoader which is now buggy. |
@AAverin Yes, please feel free to open an issue over there to ask them to investigate this issue, as this is a community driven project and not an official Mapbox product. |
@m0nac0 should we maybe rollback flutter library to 8.4.0 version of SDK? |
@AAverin I'm not sure if that would solve anything, as you said that the issue previously wasn't there even with 0.0.5 using SDK 8.5.0? |
@m0nac0 There was a fix for this issue in mapbox-android mapbox/mapbox-gl-native-android#111 |
@AAverin Thank you for keeping track of this! I'm currently testing upgrading the core sdk and the two plugins we are using. If I don't encounter any issues I'll supply a PR for it shortly. |
mapbox/mapbox-android-demo#1280
Looks like Mapbox SDK Android 8.5.0 is unstable, could we roll back to 8.4.0?
Additionally, it would be great if version changes in library dependencies would be published as a different mapbox_gl flutter library version. That way we should be able to roll back if needed.
The text was updated successfully, but these errors were encountered: