Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
LoadApplication throws the following exception when creating a MasterDetailPage:
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.MissingMethodException: Method not found: 'Android.Runtime.JNIEnv.StartCreateInstance'.
at Xamarin.Forms.Platform.Android.MasterDetailRenderer..ctor ()
This issue only affects Xamarin.Android.Support.V4 in version 22.1.1.
Workaround: Go back to Xamarin.Android.Support.V4 in version 22.0.0
For more information see http://forums.xamarin.com/discussion/39256/issue-after-upgrading-v4-support-library
I'm also seeing issues calling AppCompatDelegate.Create where it wants to call JNIEnv.CallStaticMethod that takes in a * instead of JValue as the third parameter.
We'd be happy to help you resolve this issue. On the latest release I can create a master/detail page. If you are still experiencing this exception please help us by attaching a reduced reproduction to the bug by starting with a clean Xamarin.Forms project and adding just the code necessary to demonstrate the issue.
Xamarin Forms Team
Thank you for your bug report. As we have not received the information requested, we cannot properly triage your bug and are marking it resolved.
Xamarin Forms Team