Bug 40749 - [Regression] Translation with resx files is broken (version
Summary: [Regression] Translation with resx files is broken (version
Alias: None
Product: Android
Classification: Xamarin
Component: MSBuild ()
Version: unspecified
Hardware: PC Mac OS
: High normal
Target Milestone: 6.1 (C7)
Assignee: dean.ellis
: 40690 ()
Depends on:
Reported: 2016-04-28 01:57 UTC by David CASBONNE
Modified: 2016-05-18 18:06 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 David CASBONNE 2016-04-28 01:57:50 UTC

I don't really know if it's in Mono runtime or somewhere else but since I've upgraded to Xamarin.Android (Beta channel) I'm not able to have my translations that are in an AppResources.fr.resx.

I've downgrade to and everything is OK.

Can you fix this ASAP please ?
Comment 1 Peter Collins 2016-05-04 20:30:48 UTC
@David can you provide a little more context, or ideally a project which reproduces this issue? Also, does this only happen for builds which utilize fast assembly deployment? Or does this also affect Release deployments?

@Dean Could this be a dupe of https://bugzilla.xamarin.com/show_bug.cgi?id=40690?
Comment 2 dean.ellis 2016-05-04 20:39:12 UTC
@peterc that does look like a similar problem
Comment 3 David CASBONNE 2016-05-05 01:15:23 UTC
Hi Peter,

I have followed this tutorial : https://developer.xamarin.com/guides/xamarin-forms/advanced/localization/

I'm not really able to reproduce the bug since I'm on Xamarin Android but in the bug was here.
(it's a little hard to update Xamarin Android "just to reproduce" and then going back to for the daily development).

I hope the previous link would help you to understand the bug.

Thanks a lot!
Comment 4 dean.ellis 2016-05-06 11:34:07 UTC
Fixed in monodroid/master/3946198145

@peterc do we need to get this in to cycle6/7?
Comment 5 dean.ellis 2016-05-06 11:36:36 UTC
*** Bug 40690 has been marked as a duplicate of this bug. ***
Comment 6 David CASBONNE 2016-05-07 04:06:33 UTC
Hi Dean,

Glad to hear you fix it !
Could you tell me in which version of Xamarin.Android is this bug solved ?

Comment 7 dean.ellis 2016-05-09 09:33:36 UTC
Hi David

We'll be testing it in our master branch then hopefully if it passed (which it will :) ) we can get it into the next Alpha/Beta release.
Comment 8 David CASBONNE 2016-05-09 12:25:36 UTC
Great !

Could you write here the Alpha/beta number in which it will be integrate please ? 
I will check the next beta to see it :)

Thanks !
Comment 9 Abhishek 2016-05-16 14:14:44 UTC
As per comment https://bugzilla.xamarin.com/show_bug.cgi?id=40690#c2
this issue is duplicate of bug 40690 and I have checked this issue with latest C7 build  now this issue is working fine.

Hence marking this issue as Verified.

Comment 10 David CASBONNE 2016-05-17 00:52:13 UTC

Is this disponible in the latest alpha or beta of Xamarin.Android ? 

Comment 11 Peter Collins 2016-05-17 20:57:25 UTC
This is not yet available in Alpha or Beta, but should be available in Beta in the coming weeks. I will provide an update here once this fix has been released.
Comment 12 David CASBONNE 2016-05-18 18:06:18 UTC
OK thanks! 

I will update as soon as you include this fix and provide a feedback here.