Bug 29574 - Unable to get string values from app pkg table
Summary: Unable to get string values from app pkg table
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: 5.1
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: dean.ellis
Depends on:
Reported: 2015-04-30 04:01 UTC by Casper Skoubo
Modified: 2017-09-14 18:54 UTC (History)
3 users (show)

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:

Description Casper Skoubo 2015-04-30 04:01:16 UTC
As of the new update to xamarin.android 5.1 we are no longer able to get string values from our application package string table. When i debug, i can see that the value is empty.

System.Exception: Input string was not in a correct format.

In our Values folder we have a config.xml with strings that we use to setup our app on init. The values doesn't seem to be there.

This both happens in VS 13 and Xamarin studio.

It might be related to this issue aswell: https://bugzilla.xamarin.com/show_bug.cgi?id=29568
Comment 1 Jonathan Pryor 2015-06-02 17:12:13 UTC
Could you please attach a repro?
Comment 2 Jon Douglas [MSFT] 2017-09-14 18:54:33 UTC
Because we have not received a reply to our request for more information we are closing this issue. If you are still encountering this issue, please reopen the ticket with the requested information. Thanks!