Xamarin
A Microsoft open-source app platform for building Android and iOS apps with .NET and C#.
5,380 questions
How to resolve Xamarin.Forms crash when navigating between pages on Android?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(121.6, 78%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMA%3C/text%3E%3C/svg%3E)
Muhammad Amiruddin Latief
0
Reputation points
I'm experiencing an issue in a Xamarin.Forms app where the app crashes when navigating between two pages, but only on Android devices. The crash log mentions an ObjectDisposedException related to a renderer. I suspect it has something to do with the way the navigation stack is being managed or a custom renderer that is being disposed prematurely. I've tried wrapping the navigation code in Device.BeginInvokeOnMainThread, but it didn't help.
Does anyone have a reliable pattern for safe navigation between pages in Xamarin.Forms, especially on Android?
This question is related to the following Learning Module
Xamarin
{count} votes
-
Muhammad Amiruddin Latief 0 Reputation points
2025-05-09T13:18:25.6333333+00:00 You may be encountering an
ObjectDisposedExceptiondue to a timing issue when navigating between pages, especially if a custom renderer or view is being disposed before it finishes rendering. Here are a few suggestions that might help:Use
Device.BeginInvokeOnMainThreadMake sure all UI-related operations are executed on the main thread:Device.BeginInvokeOnMainThread(async () => { await Navigation.PushAsync(new YourNextPage()); });Avoid double navigation Ensure that users can’t trigger multiple navigations quickly. You can disable the button temporarily or use a flag:
if (_isNavigating) return; _isNavigating = true; await Navigation.PushAsync(new YourNextPage()); _isNavigating = false;Clean up custom renderers properly If you are using custom renderers, double-check their
Disposeimplementations to make sure they aren’t cleaning up views too early.Use
OnDisappearingandOnAppearingcarefully Avoid heavy operations or further navigation calls within these methods.Update Xamarin and dependencies Some crashes are caused by known bugs. Make sure your Xamarin.Forms and Android SDK versions are up to date.
Let me know if you can share the full stack trace or a sample code, and I can help analyze further.
Sign in to comment
Sign in to answer