Closed kabirkhaan closed 11 months ago
Hi there,
Thanks for reaching out to us.
Since this issue requires some further investigation related to your personal set up, could you please submit your request via support@phrase.com?
Please make sure to include following details:
This thread will be closed and we will take care of your request submitted at support@phrase.com.
Thank you very much in advance!
Have a great evening and talk to you soon!
Best, Domenica from the Phrase Technical Support Team
Comment by Domenica
Do you maybe have an idea what could be the reason why en translations are showing after the upgrade to 4.0.1 @winkelsdorf?
Do you maybe have an idea what could be the reason why en translations are showing after the upgrade to 4.0.1 @winkelsdorf?
As my understanding it picking up Localization native development region from plist for some reason.
@kabirkhaan I tried to reproduce this, but sadly was unable to.
I would suggest using the callback handler of updateTranslations
to check for any errors (result is .failure(error)
where error.last
gives you the current error) and try log them to see under which circumstances the App falls back to the native development region.
We are validating the downloaded translations (e.g. their version range, release version, the last update timestamp etc) and do a fallback to the MainBundle if nothing valid is found.
Another idea: I can also think of a fallback being done at the Backend side. If it happens in a simulator you could investigate the Localizable.strings
:
inside iOS Simulator Library:
Application Support\com.phrase.phraseSDK\Translations\de-DE.lproj\Localizable.strings
That file should contain german strings, if they are translated. It might contain fallback strings (e.g. english strings), if you have set the OTA release to do so.
Also please try to enable the debugMode
and as said please check the result of the updateHandler
callback.
@theSoenke Do we have any other reports related to this behaviour (App containing the iOS SDK switching the language by itself randomly)?
Closing: This problem has either been fixed by the developer in the meantime or an update has solved it as a side effect. Please reopen this issue and/or submit a new issue if the problem persists.
After updating 4.0.1 we are facing an issue that app use
Localization native development region
Steps to Reproduced:
de
de
en
which is setLocalization native development region