-
Notifications
You must be signed in to change notification settings - Fork 5
"Application has stopped" error while initializing MapboxNavigation #1
Comments
To add more information about the crash, I'm using MvvmCross and using LogCat the device return this:
|
Error message is very clear
Plz make sure your application class is written correctly. MvvmCross won't impact this binding library. Cheers. |
@BoogieMAN2K Haven't heard back from you. Is that ok now? |
@tuyen-vuduc Hello again! I got same java.lang.UnsatisfiedLinkError exception when I call LostLocationEngine.Activate() or others LostLocationEngine methods. There is my sample: Application class is written correctly and works when app starts. I guess Android throws exception due to Mapzen starts service in another process. Generated AndroidManifest contains this line:
So, I google this problem and found this https://bugzilla.xamarin.com/show_bug.cgi?id=51940. Any ideas how to fix this? |
+1, have same problem. Any progress? |
+1 Error happens in the MapboxCoreNavigation library, if someone has a workaround I'll appreciate it. Been trying to somehow get around this issue, it only happens the first time the MapboxNavigation object is instantiated. I'm using my own binding with the latest MapboxNavigation library and getting the same error so I don't think it has to do with this binding library but the actual mapbox native one. |
Hi, I hope this can help, in my case the error happens because I have a custom class for MainApplication which inherits from Application, Application.IActivityLifecycleCallbacks. On this class I have an override for OnCreate (which still calls base.OnCreate). If I remove this override I stop getting the error. It seems that the MapzenLost process gets confused by having this OnCreate override. I'm also using GoogleLocationEngine instead of LostLocationEngine. I've never been able to make LostLocationEngine work with LocationLayerPlugin. |
@JPSiller Experiencing the same issue (with another library binding). Have you ever found a solution/workaround to this problem? |
I was experiencing the exact same problem which weirdly started apparently from nothing. So, after almost 4 hours looking into this, I have decided to move the code from OnCreate() method to the ctor() based on @JPSiller comment and now the problem is gone. I still need to test a little bit more, but at least the app is able to start correctly now. |
I'm initializing the MapboxNavigation class during the OnCreate method and after the line gets executed android is returning me this message. The thing is, the navigation is getting created correctly and everything works fine after that but the Application output doesn't return any message or trace related and I don't know how to fix this issue.
This is the related code, JIC...
` MapboxNavigation navigation;
NavigationMapRoute navigationMapRoute;
`
Any help would be greatly appreciated...
The text was updated successfully, but these errors were encountered: