You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MvxAndroidSetup and the other platform setups look for a specific extension to the plugin assembly. So for Android it expects an assembly that is called MyPlugin.Useful.Droid where the Android implementation resides. If it doesn't find that, it doesn't try to fall back to anything else and then just explodes.
This happens due to when switching to Multi-target, the assembly names are now all the same for all assemblies. Platform specific or not.
MvxAndroidSetup and the other platform setups look for a specific extension to the plugin assembly. So for Android it expects an assembly that is called
MyPlugin.Useful.Droid
where the Android implementation resides. If it doesn't find that, it doesn't try to fall back to anything else and then just explodes.This happens due to when switching to Multi-target, the assembly names are now all the same for all assemblies. Platform specific or not.
@AlexStefan was very quick to provide a repro sample https://github.com/AlexStefan/template-app/blob/master/Internationalization/
The Core and Droid projects there point at MvvmCross in the folder
../../mc
Steps to reproduce 📜
Expected behavior 🤔
App should run
Actual behavior 🐛
App crashes
Configuration 🔧
Version: 6.0.0-beta2
The text was updated successfully, but these errors were encountered: