Android.Content.Res.Resources+NotFoundException: Resource ID #0xff303030 RRS feed

  • Question

  • User109544 posted

    I created an empty POL Xamarin Forms project and added the following in the App constructor

            var TabbedPages = new TabbedPage { Title = "Test App" };
            MainPage = new NavigationPage(TabbedPages);

    Then in the LoadApplication(new App()); line I get the following exception

    Android.Content.Res.Resources+NotFoundException: Resource ID #0xff303030

    I've attached my test project, please run within Visual Studio and enable the check box 'thrown' for Exception 'Common Language Runtime Exceptions' in the Debug->Exceptions dialog.

    Please note I also get the error when I do the following which means the issue is with the NavigationPage.

            MainPage = new NavigationPage(new ContentPage());

    When I do the following, then it works. MainPage = new ContentPage();

    Also reproduced the error with the Forms2Native sample project.

    Tuesday, April 21, 2015 8:12 AM

All replies

  • User109544 posted

    Added to the bug tracker system https://bugzilla.xamarin.com/show_bug.cgi?id=29267

    Tuesday, April 21, 2015 8:39 AM
  • User138607 posted

    I have a similar issue but with other id on Android.Content.Res.Resources+NotFoundException: Resource ID #0xffeeeeee

    It happens on this call await Navigation.PushAsync(_detailPage, true);

    Do you have any work around?

    Wednesday, July 8, 2015 2:01 PM
  • User55225 posted

    +1 using Xamarin Android Player running Nexus 4 Lollipop

    Thursday, July 9, 2015 11:14 AM
  • User138607 posted

    Any news about this?

    Tuesday, July 14, 2015 2:53 PM
  • User33 posted

    I've attached my test project, please run within Visual Studio and enable the check box 'thrown' for Exception 'Common Language Runtime Exceptions' in the Debug->Exceptions dialog.

    This is just a first-chance exception, just hit continue, it won't crash your app and is nothing to worry about.

    Tuesday, July 14, 2015 4:59 PM
  • User55225 posted

    Hi @ermau!

    Thanks for the reply. I do not think the issue is whether it will cause an issue, but rather that it can make debugging with CLR exceptions enabled very cumbersome.

    Should the framework be generating known exceptions in this fashion, even if they do not bubble up to our code?


    Tuesday, July 14, 2015 6:14 PM
  • User54590 posted

    @AnthonyRamirez - is it possibly related to this bug (apparently resolved in what version are you on? Although by the looks of it, thats only on Xamarin Studio.

    This one also has a similar issue (you will need to read further down for it become more obvious that its related). https://bugzilla.xamarin.com/show_bug.cgi?id=19608

    I have not had a chance to test it myself yet.

    Wednesday, July 15, 2015 1:58 PM
  • User55225 posted

    Thanks for the reply @RezaMousavi

    I see your post, and I have experienced the same issue, however, if I am reading it correctly that will only happen with web requests to HTTPS. Maybe I am wrong.

    The issue above, occurs when navigating to any page in X.Forms

    I'm using VS 2013 and my version of Xamarin.Android Version: 5.1.4 (Business Edition) Xamarin Android Player Version:

    Wednesday, July 15, 2015 2:33 PM
  • User54590 posted

    No I think you are reading it right. That is what was reported but I have seen it happen in other places too.

    Sounds like it is anywhere that Xamarin internally throws an exception and catches it.

    Try untickting all "Thrown" exceptions from the DEBUG > Exceptions window, do you still get the same issue?

    Wednesday, July 15, 2015 2:37 PM
  • User55225 posted

    ok cool.

    When I untick the box, no error occurs.

    However, I find that ticking the box can allow me to track down bugs easier. Otherwise they just go to the Unhandled Exception block and I lose all of the local variables.

    Wednesday, July 15, 2015 2:39 PM
  • User54590 posted

    Completely agree. It will be a lot more useful when this issue is fixed.

    Maybe worth bumping the bug reports or creating a new one if you don't think its exactly the same.

    Wednesday, July 15, 2015 3:44 PM
  • User55225 posted

    Good idea. I just updated the bug post


    Wednesday, July 15, 2015 3:49 PM