From 6b320c12e07e57c866d787841e8a5b41c583808d Mon Sep 17 00:00:00 2001 From: Aleksey Mikhailov Date: Tue, 10 Oct 2023 08:41:13 +0700 Subject: [PATCH] add notes about issues --- README.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/README.md b/README.md index 3ed84913..abeb144f 100755 --- a/README.md +++ b/README.md @@ -805,6 +805,16 @@ with compose you can just call in `commonMain` val assetContent: String? by MR.assets.test.readTextAsState() ``` +## Known issues + +### iOS shows key instead of localized text + +1. check that generated `Localizable.strings` file is valid - open it by Xcode (located in `shared/shared/build/bin/iosSimulatorArm64/debugFramework/shared.framework/:shared.bundle/Contents/Resources/Base.lproj/Localizable.strings` and in other `.lproj` directories. If Xcode show error in file - you should fix content of strings.xml (for example you use some special character that broke file). + +2. check that your generated `.bundle` exist inside application at runtime. In Xcode inside group `Products` select your application and click `Show in Finder`. Then click `Show Package Contents`. Inside `.app` you should see `.bundle` in root directory if you use static framework. And in `Frameworks/shared.framework` if you use dynamic framework. If `bundle` missed - check installation guide. Specifically xcode build phase part if you use static framework. And check that you apply moko-resources plugin in `shared` gradle module. + +3. check that your `strings.xml` contains all keys for language that you use. If you have keys `test1`, `test2` in `Base/strings.xml`, and only `test1` in `ru/strings.xml` then you got key instead of text in ru locale for `test2` key. iOS not fallback to base locale now + ## Samples In `samples` directory you can find multiple projects showed different usages.