Bug 25403 - Android SetPage after async fails. Goes to blank black screen.
Summary: Android SetPage after async fails. Goes to blank black screen.
Status: RESOLVED FIXED
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.3.0
Hardware: All Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2014-12-15 15:02 UTC by Shane
Modified: 2014-12-26 02:05 UTC (History)
3 users (show)

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

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 FIXED

Description Shane 2014-12-15 15:02:26 UTC
Xamarin.Forms.AndroidActivity.SetPage in android goes to a blank black screen if it occurs after async. Several people have been using various bad workarounds to get around this.

Best writeup of the bug: http://forums.xamarin.com/discussion/25079/android-setpage-after-async-fails
Another: http://forums.xamarin.com/discussion/28018/xamarin-forms-android-setpage-doesnt-change-ui
Another: http://forums.xamarin.com/discussion/comment/81153
Another: http://stackoverflow.com/questions/26299632/xamarin-form-setpage-not-worked-second-time
Comment 1 Shane 2014-12-15 17:07:58 UTC
I personally resolved mine by lowering the number of images loaded on the next page. I imagine different people had different issues.
Comment 2 Shane 2014-12-15 17:10:30 UTC
Actually it's still an issue. I just had the fix in still when I tested it. I have verified that it is nothing on my end.
Comment 3 Shane 2014-12-26 02:05:16 UTC
This is fixed with the new way of setting pages in 1.3.0. Closing it.