Android 4.1.2: NavigationUI Not Opening #534
Comments
|
@Danny-James it looks like this is a crash in our Maps SDK |
|
Yes, I Can Reproduce This In My App Everytime I Try to Launch Navigation UI on Android 4.1.2 - I Will Put The Logcat Into A File And Upload Here, Cheers @danesfeder |
|
@danesfeder See Attached - GitHub_Logcat_534.log |
|
@danesfeder any news on this? |
|
@Danny-James I tested out the UI with API 19 and it launched fine - I'm wondering if this is related to the device. Can you provide the device info that you're able to produce this on? Thanks! |
|
@danesfeder I could send you a device via post? - But I'm currently using Model: Let me know if you need anymore information |
|
@danesfeder Still Getting This Issue On The Latest Stable Version The API is 16 I believe on the device. Any news on this? |
|
@danesfeder I'm now using the below gradle config. // Mapbox Maps SDK
implementation 'com.mapbox.mapboxsdk:mapbox-android-plugin-traffic:0.3.0'
implementation ('com.mapbox.mapboxsdk:mapbox-android-navigation-ui:0.8.0') {
transitive = true
changing = true
}I'm still getting the crash on open for the Navigation UI. // Generate Navigation Options
NavigationViewOptions.Builder navOptions = NavigationViewOptions.builder()
.awsPoolId(null)
.directionsRoute(currentRoute)
.shouldSimulateRoute(false);
// Launch Navigation UI.
NavigationLauncher.startNavigation(ActivityNavigationMap.this, navOptions.build());See below the error i'm recieving. |
|
@danesfeder The Navigation UI Seems to go a little further than previously see below compared to the ScreenGrab Above.
|
|
@Danny-James Do you mind sending the stack trace from the above gif? Or is it the same |
|
@danesfeder yes the signal 11 error is the error from the above GIF. |
|
@Danny-James Yeah I think this may be device specific. Just tried to reproduce with API 16, without any luck:
@tobrun this looks like a native crash specific to this device when starting up the nav UI. Anything you can get out of that log? I believe it isn't symbolicated |
|
@danesfeder What does this mean? Device Specific Issue, Can this be fixed and would you like me to send one of our device to you? |
|
@Danny-James it means this may be specific to the Motorola device you are producing the crash on and not necessarily the API |
|
@danesfeder Thanks For Looking Into This. |
|
This could be similar to mapbox/mapbox-gl-native#10253. We've blacklisted Adreno 3 chipsets for VAO support, but this backtrace indicates that this device uses an Adreno 2 chipset. The backtrace actually doesn't contain any Mapbox-specific symbols, just the regular Android EGL context destruction routines, which fail when destroying a VAO. It could be possible that there is a bug in Adreno's implementation of VAOs (we know that the newer chipsets are buggy in this regard too). Either way, given that we're not seeing VAO-related crashes with newer devices, I'm inclined to blacklist Adreno 2 for VAO support if we can verify that this fixes the crash. Mapbox GL will continue to work on this device, but will just not take advantage of the performance improvements that VAOs have. |
|
@Danny-James the Maps team cooked up a build of the SDK that has a potential fix for the issue seen in this ticket: https://www.dropbox.com/s/6s667gorh7qiatt/MapboxGLAndroidSDK-release.aar?dl=0 Can you use this version of the library locally and see if you're still able to reproduce? |
|
any updates @Danny-James? |
|
Sorry @tobrun @danesfeder I've been on out of the office Monday and Tuesday, I'm hoping to look at this today and will update you. Sorry again for the delay. |
|
Np @Danny-James, looking forward to the results 🙏 |
|
@tobrun I Get The Following Message on DropBox - |
|
Apologies, updated the link settings, can you try again? |
|
@tobrun, What's the best way to include the dependency locally I've only every worked with external dependencies. |
|
@tobrun my current gradle config is below; Will the local library I've just imported take priority over the dependencies I'm compiling. The way I imported the Library is; |
|
For easy of testing, I'm building a SNAPSHOT version with that change. Will ping here when the build has finished building. |
|
To resolve the SNAPSHOT build add the following to your top build.gradle file: Afterwards change your maps sdk dependency to: |
|
@tobrun I don't currently compile the Maps SDK as this comes with the Navigation UI, by adding the dependency in the gradle will this take priority? |
|
you can verify that by running This will show you a which dependency is bringing in which and which are being overriden by other versions. Since the navigation SDK comes with 5.3.2 it should overwrite but better to be sure and double check with above. |
|
@tobrun thanks for you patience, will report back soon just compiling my application. |
|
@tobrun Absolutely fantastic this has solved this issue and also solved #10030 - I would like to thank everyone involved with this and for your patience with me throughout the month's trying to get this working myself and the company really appreciate all your help. I have one issue remaining and I can then get this application released to our users. (Ability to Disable ReRouting, For the work around of waypoints not working with Navigation UI) but this is for @danesfeder I believe. Again Thank You. |
|
@tobrun, when will this Version be included in the Navigation UI Dependency? @danesfeder |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When trying to Launch the Navigation UI on Android 4.1.2 Device It's crashing my activity.
Gradle Config
Code to Launch Navigation UI
Logcat
See GIF's Below;
Android 4.1.2 (Not Working)
Android 8.1.0 (Working)
The text was updated successfully, but these errors were encountered: