-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
MVVMCross 8.0.2 Android 12 support? #4435
Replies: 3 comments · 14 replies
-
Probably related to: #4290 |
Beta Was this translation helpful? Give feedback.
All reactions
-
Some exceptions from logcat
|
Beta Was this translation helpful? Give feedback.
All reactions
-
So first clue. Something is blowing up in your
Have you set a breakpoint there and investigated what is up? The other exception:
What happens in your |
Beta Was this translation helpful? Give feedback.
All reactions
-
(DeviceFinders is the name we have given the Interface/Classes that are responsible for finding multiple different brands and devicetype of Bluetooth devices across protocols (SPP,HDP, BLE) and with differing communication rules ) BluetoothPlugin.Droid/Plugin.cs/Load()
|
Beta Was this translation helpful? Give feedback.
All reactions
-
SettingsViewModel()
base of SettingsViewModel
|
Beta Was this translation helpful? Give feedback.
All reactions
-
@Cheesebaron You were on the right track. It pains me to say that we did not properly read the inner most exception message in logcat (partly because there is no line breaks and the relevant part starts at column 761). The Appinux mobile app is integrating/using many different external Bluetooth devices.
The strange part is that it does not seem to happen on all devices we have with Android 12. Anyhow - it is not a MVVMCross problem. I am sorry to have taken up everyone's time, and a big thank you to all that have contributed. Regards |
Beta Was this translation helpful? Give feedback.
All reactions
-
🎉 1
-
Here my device Samsung Galaxy 10S android 12. on this device I do not have any crash |
Beta Was this translation helpful? Give feedback.
All reactions
-
Splash screen activity is a bad practice. |
Beta Was this translation helpful? Give feedback.
All reactions
-
So then I understand that the best practice would be to not have a dedicated Splash Activity? If that is the case how are we supposed to handle the MvvmCross initialization? Now it is handled by the |
Beta Was this translation helpful? Give feedback.
All reactions
-
Just remove it. Should work fine without it out of the box. Just set |
Beta Was this translation helpful? Give feedback.
-
We have an MVVMCross 8.0.2 application with a splash screen. Android 12 have made quite significant changes to the Splashscreen behaviour. We are facing some strange behaviors in relation to the IoC container that seems to not be initialized properly. This is initialized in the splash screen. When debugging it does seem like everything is being instantiated as it should, but we are faced with exceptions where it complains about null reference exceptions.
Does MVVMCross 8.0.2 at all support Android 12 ?
I am trying to figure out if this is just us not having handled Android 12 splash screen changes or if there is something fundamentally wrong in MVVMCross 8.0.2 in relation to Android 12.
Beta Was this translation helpful? Give feedback.
All reactions