Zero
Zero

Reputation: 194

xamarin IllegalStateException activity has been destroyed on app closing

I get an IllegalStateException with "activity has been destroyed" when I close my app.

In my App.cs I declare a public static MasterPage:

protected override void OnStart()
    {
        // Handle when your app starts
        if (Device.OS == TargetPlatform.Android)
        {
            Device.BeginInvokeOnMainThread(() =>
            {
                masterdetail = new MasterPage();
                MainPage = masterdetail;
            });
        }
        else
        {
            masterdetail = new MasterPage();
            MainPage = masterdetail;
        }
    }

And in the MasterPage.cs I declare the Master and the DetilPage:

public partial class MasterPage : MasterDetailPage
{

    public MasterPage()
    {

        var IsLoggedIn = false;

        if (CrossSecureStorage.Current.HasKey("isLoggedIn"))
        {
            IsLoggedIn = string.Equals(CrossSecureStorage.Current.GetValue("isLoggedIn"), "true", System.StringComparison.CurrentCultureIgnoreCase);
        }

        Master = SetMasterContentPage();
        if (IsLoggedIn)
        {   
            Detail = new NavigationPage(new TaxonomyOverviewPage());
        }
        else {
            Detail = new NavigationPage(new LoginPage());
        }
    }

    ContentPage SetMasterContentPage()
    {
        var masterPage = new ContentPage { Title = "Test"};
        masterPage.Content = new StackLayout
        {
            Children = {
                new Label{Text="Label1"},
                new Label{Text="Label2"},
                new Label{Text="Label3"}
            }
        };

        return masterPage;
    }

    protected override void OnDisappearing()
    {
        base.OnDisappearing();
        GC.Collect();
    }
}

Upvotes: 1

Views: 469

Answers (1)

Zero
Zero

Reputation: 194

Ok, that was a bug in Xamarin.Forms Version 2.3.3.175. To fix this bug install an earlier version of Xamarin.Forms. I get my app running with version 2.3.0.107.

The bug in version 2.3.3.175 should be fixed in version 2.3.4-pre1.

Upvotes: 2

Related Questions