Phrase OTA on iOS native project, with KMP moko library about ios-sdk HOT 3 OPEN

We solve that with our custom handling of fetching resources from the correct bundle. Whenever we tried to fetch from local data we used the moko bundle, and when we tried to use Phrase OTA data, we used the iOS app bundle.

from ios-sdk.

Hi @BVantur, that's great to hear that both SDKs already work almost out of the box with KMP! Would you mind sharing the snippet that you use to use the correct bundle on iOS if that's possible? I would like to make sure that the KMP support is also properly documented

from ios-sdk.

Yeah, sure.
We have a strange behavior in our app and I am not even sure if the above issue is a valid issue that we observed, In the end, what we needed to do with the iOS part of the app, is to use 2 different bundles in our LocalizationManager class.

For moko-based strings that we want to use in a case when there were no Phrase OTA texts present, we used this bundle:
SharedRes.strings().__platformDetails.nsBundle

But for Phrase OTA texts we needed to use a bundle depending on the language with the URL like this:

let phrasePath = "com.phrase.phraseSDK/Translations/\(languageCode).lproj"
let languageDirectoryURL = applicationSupportDirectory.appendingPathComponent(phrasePath, isDirectory: true)
return languageDirectoryURL
Bundle(url: languageDirectoryURL)

In our LocalizationManager we are always trying to read Phrase OTA text first and if it doesn't exist we fall back to a bundle that has strings from the moko library.

I hope this comment will help someone who might end up in the same situation.

from ios-sdk.