I don't really know if it's in Mono runtime or somewhere else but since I've upgraded to Xamarin.Android 184.108.40.206 (Beta channel) I'm not able to have my translations that are in an AppResources.fr.resx.
I've downgrade to 220.127.116.11 and everything is OK.
Can you fix this ASAP please ?
@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?
@peterc that does look like a similar problem
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 18.104.22.168 but in 22.214.171.124 the bug was here.
(it's a little hard to update Xamarin Android "just to reproduce" and then going back to 126.96.36.199 for the daily development).
I hope the previous link would help you to understand the bug.
Thanks a lot!
Fixed in monodroid/master/3946198145
@peterc do we need to get this in to cycle6/7?
*** Bug 40690 has been marked as a duplicate of this bug. ***
Glad to hear you fix it !
Could you tell me in which version of Xamarin.Android is this bug solved ?
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.
Could you write here the Alpha/beta number in which it will be integrate please ?
I will check the next beta to see it :)
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.
Is this disponible in the latest alpha or beta of Xamarin.Android ?
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.
I will update as soon as you include this fix and provide a feedback here.