-
Notifications
You must be signed in to change notification settings - Fork 56
Activity hangs after java.lang.NoClassDefFoundError #207
Comments
In the meantime, I'm updating to 28.0.0.3 in the hope that this might fix the issue. However, as this is very hard to reproduce or even capture the logs (99% of userbase has a very strict MDM), please give me some feedback if that might fix the issue or not :) |
Unfortunately I highly doubt 28.0.0.3 vs 28.0.0.1 will fix anything here. This looks like some issue on Google's end after a bit of searching. What settings are you using for your TargetFrameworkVersion, and are you using multidex? |
We're using |
Almost the same here. SplashScreenActivity doesn't show anything because of some exception during "SetContentView".
|
OS & SDK version info
https://github.com/bitrise-io/bitrise.io/blob/e99ae1dac2792fdbff55b6e4d1d5268f1195d5da/system_reports/osx-vs4mac-stable.log
Support Libraries Version (eg: 23.3.0): 28.0.0.1
Describe your Issue
We have a Xamarin.Android app with MvvmCross 6.3.1, no Xamarin.Forms. Sometimes (probably race condition or lifecycle/memory related) our app hangs on the
SplashActivity
.The
SplashActivity
does nothing more than continue to the next activity (let's call itLoginActivity
) using the MvvmCross engine (AppStarter
etc.).About 95% of the time this works without issues. The issue never occurs when the app is completely closed (or when you force close it using the OS settings).
Sometimes the app does not continue from the
SplashActivity
andLoginActivity
does not become visible. However, we notice in logcat that the views onLoginActivity
are constructed as the MvvmCross bindings also output some logging information.Steps to Reproduce (with link to sample solution if possible): not found yet, any help for finding a repro is welcome
Include any relevant Exception Stack traces, build logs, adb logs:
We have been able to capture the logs only once on a device with ADB enabled. We noticed that every time we tried to launch the app, the logs below were outputted.
The text was updated successfully, but these errors were encountered: