New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
iOS will show 2 LaunchScreen when localized #59855
Comments
May be related to #55952 |
Hi @shily flutter doctor -v
|
Hi @TahaTesser Seen you used a iPhone 8 with 13.5 |
i can reproduce this issue on iOS 12 flutter doctor -v
|
flutter 1.20.2 still has this problem. |
1.20.2 was not the master branch where it was reported fixed. Can you try it on master instead of stable? Try |
Master branch still has this problem.
|
iOS has a bad habit of keeping the old splash screen as a system cache. Simply uninstalling the app will not fix it. Either restart or clear your device cache |
I think it is the Flutter bug not iOS cache issue. I've tried the Native iOS project for localized Launch Screen, it works well. Here is the sample: https://github.com/gaoshanyu/pie/tree/scaling-views-to-complement-text |
This comment was marked as duplicate.
This comment was marked as duplicate.
Verified this issue using latest stable version and running the repo provided in original description, I see that the behavior persists, as below: 59855.movstable, master flutter doctor -v
|
Summary:
I want to localize the LaunchScreen with different images, LaunchScreen will show 2 times.
First localized (Chinese) and Second Default(English).
Steps to Reproduce:
"UILaunchStoryboardName" = "LaunchScreen-ZH";
to the file "ios/zh-Hans.lproj/InfoPlist.strings"Demo project: https://github.com/shily/iOSLaunchScreenBug
Expected Results:
The LaunchScreen will boot with a Chinese Logo and then to MainScreen
Actual Results:
App boot with localized LaunchScreen-ZH.storyboard and then switch to Default LaunchScreen.storyboard before switch to Main.storyboard
Environments:
Devices:
Flutter version: dev & stable channel both have the problem
The text was updated successfully, but these errors were encountered: