Bug 60346 - Android App crashes on startup after updating to Xamarin.Forms 2.4.0.18342
Summary: Android App crashes on startup after updating to Xamarin.Forms 2.4.0.18342
Status: RESOLVED DUPLICATE of bug 60337
Alias: None
Product: Forms
Classification: Xamarin
Component: Android ()
Version: 2.4.0
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2017-10-24 12:40 UTC by Wallace Santos
Modified: 2017-10-24 14:36 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
Full log of the problem. (150.45 KB, text/plain)
2017-10-24 12:40 UTC, Wallace Santos
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:
Status:
RESOLVED DUPLICATE of bug 60337

Description Wallace Santos 2017-10-24 12:40:40 UTC
Created attachment 25418 [details]
Full log of the problem.

After updated my project with the last version on Xamarin.Forms (2.4.0.18342), android version crashes on startup when android app call LoadApplication(new App()) method. 

Here is application output (attached follows full log):

[MonoDroid] UNHANDLED EXCEPTION:
[MonoDroid] System.NullReferenceException: Object reference not set to an instance of an object.
[MonoDroid]   at Xamarin.Forms.Platform.Android.Platform.GetRenderer (Xamarin.Forms.VisualElement bindable) [0x00000] in C:\agent\_work\3\s\Xamarin.Forms.Platform.Android\Platform.cs:292 
[MonoDroid]   at Xamarin.Forms.Platform.Android.FormsAppCompatActivity.LoadApplication (Xamarin.Forms.Application application) [0x00229] in C:\agent\_work\3\s\Xamarin.Forms.Platform.Android\AppCompat\FormsAppCompatActivity.cs:152 
[MonoDroid]   at WiseShopper.Droid.MainActivity.OnCreate (Android.OS.Bundle bundle) [0x000b6] in /Users/wallacesantos/Projects/WiseShopper/Android/MainActivity.cs:53 
[MonoDroid]   at Android.App.Activity.n_OnCreate_Landroid_os_Bundle_ (System.IntPtr jnienv, System.IntPtr native__this, System.IntPtr native_savedInstanceState) [0x0000f] in <c82a099136944d8aa96281cf061cbc12>:0 
[MonoDroid]   at (wrapper dynamic-method) System.Object:fdc85eb9-9619-4fd3-ab2e-fe23d22d43d7 (intptr,intptr,intptr)
[art] JNI RegisterNativeMethods: attempt to register 0 native methods for android.runtime.JavaProxyThrowable
[Mono] DllImport searching in: '__Internal' ('(null)').
[Mono] Searching for 'java_interop_jnienv_throw'.
[Mono] Probing 'java_interop_jnienv_throw'.
[Mono] Found as 'java_interop_jnienv_throw'.
[mono] 
[mono] Unhandled Exception:
[mono] System.NullReferenceException: Object reference not set to an instance of an object.
[mono-rt] [ERROR] FATAL UNHANDLED EXCEPTION: System.NullReferenceException: Object reference not set to an instance of an object.
[TMSDISP] AcsAndroidVirtualDisplayIntfImpl::~AcsAndroidVirtualDisplayIntfImpl - Enter
[TMSDISP] AcsAndroidVirtualDisplayIntfImpl::~AcsAndroidVirtualDisplayIntfImpl - Enter2
[TMSDISP] AcsAndroidVirtualDisplayIntfImpl::~AcsAndroidVirtualDisplayIntfImpl - mSource2
[TMSDISP] AcsAndroidVirtualDisplayIntfImpl::~AcsAndroidVirtualDisplayIntfImpl - Exit
Comment 1 Wallace Santos 2017-10-24 14:13:01 UTC
Updating: I downgrade my app with a previous version of Xamarin.Forms dll (version 2.3.4.270) and the app ran normally.
Comment 2 Paul DiPietro [MSFT] 2017-10-24 14:36:29 UTC
For the moment I'm going to assume this is related to 60337.

*** This bug has been marked as a duplicate of bug 60337 ***