No such luck here I'm afraid.
Unsure if the Localize.strings encoding is related to this issue, don't really see how that ties to the issue. I tried forcing UTF-8 on our Localize.strings but without any luck.
No such luck here I'm afraid.
Unsure if the Localize.strings encoding is related to this issue, don't really see how that ties to the issue. I tried forcing UTF-8 on our Localize.strings but without any luck.