-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.NET MAUI - Redirecting to AppShell page throws "Can not perform this action after onsaveinstancestate" exception #18159
Comments
We've added this issue to our backlog, and we will work to address it as time and resources allow. If you have any additional information or questions about this issue, please leave a comment. For additional info about issue management, please read our Triage Process. |
Since it is been added to the Backlog. Do we have any workaround for this issue? This is blocking us from our migration. |
I found that doing the change on the mainthread and adding a delay works. on faster phones. MainThread.BeginInvokeOnMainThread(async () =>
{
await Task.Delay(100);
MainPage = new AppShell();
});
}); |
Same issue here - setting MainPage to AppShell causes random crashes on production with callstack like: |
Seems the sleep doesnt always work. still getting the error in google play crash logs. |
Same Issue |
Duplicate of #11501 Try doing it inside |
The app is crashing randomly. |
Description
I am in the progress on migrating my Xamarin project to MAUI with .NET 7.
I have a login page when the app opens, on button click the login process will happen via WebAuthenticator. Once the login is successful I am redirecting to AppShell Page.
On redirecting to appshell, I am getting error ""
Steps to Reproduce
Link to public reproduction project repository
https://github.com/DharunAR/SecureTest
Version with bug
7.0.96
Is this a regression from previous behavior?
Yes, this used to work in Xamarin.Forms
Last version that worked well
Unknown/Other
Affected platforms
Android
Affected platform versions
Android 12 and 13.
Did you find any workaround?
No.
Relevant log output
No response
The text was updated successfully, but these errors were encountered: