I see the following crash in OnStart on Android for a handful of my users. I cannot reproduce this myself. Has anyone seen this? Why would it not be able to resolve the INavigationService dependency? The only call to the DependencyResolver in OnStart is await DependencyResolver.Resolve<INavigationService>().InitializeAsync();.
android.runtime.JavaProxyThrowable: at BalanceForecasting.Core.Dependency.DependencyResolver.Resolve[T] () [0x00006] in <da884dc937844bcb825aea050968506b>:0
at BalanceForecasting.App.OnStart () [0x000a6] in <da884dc937844bcb825aea050968506b>:0
at System.Runtime.CompilerServices.AsyncMethodBuilderCore+<>c.<ThrowAsync>b__7_0 (System.Object state) [0x00000] in <7d466fc78986465b98bf8e069ca47b5e>:0
at Android.App.SyncContext+<>c__DisplayClass2_0.<Post>b__0 () [0x00000] in <c2c0528935f749b79020cc27a8a55d69>:0
at Java.Lang.Thread+RunnableImplementor.Run () [0x00008] in <c2c0528935f749b79020cc27a8a55d69>:0
at Java.Lang.IRunnableInvoker.n_Run (System.IntPtr jnienv, System.IntPtr native__this) [0x00009] in <c2c0528935f749b79020cc27a8a55d69>:0
at (wrapper dynamic-method) Android.Runtime.DynamicMethodNameCounter.30(intptr,intptr)
at mono.java.lang.RunnableImplementor.n_run (Native Method)
at mono.java.lang.RunnableImplementor.run (RunnableImplementor.java:30)
at android.os.Handler.handleCallback (Handler.java:883)
at android.os.Handler.dispatchMessage (Handler.java:100)
at android.os.Looper.loop (Looper.java:214)
at android.app.ActivityThread.main (ActivityThread.java:7356)
at java.lang.reflect.Method.invoke (Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:492)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:930)
4 Answer(s)
-
0
Hi @tinytownsoftware
NavigationService is used to set the main view for the app. Did you have a clue why this might happen ? We will also check possible causes.
Thanks,
-
0
No, I am not sure why this may be happening. It is very sporadic and is happening only a handful of times per day. I have a lot of users.
-
0
the reason that you see that error on specific users is that; those specific users might have some extra feature/menu item allowed and you may forgotten to register the objects in the error throwing menu items. so I recommend you to login to the system on behalf of that user and see the missing Dependency Injection registration. The prod app hides the inner exceptions.
-
0
I will try that. Thank you!
