bug: Ionic 6 production build causes white screen in ios versions 14.4 and lower
See original GitHub issuePrerequisites
- I have read the Contributing Guidelines.
- I agree to follow the Code of Conduct.
- I have searched for existing issues that already report this problem, without success.
Ionic Framework Version
- v4.x
- v5.x
- v6.x
- Nightly
Current Behavior
ionic-angular app with production build (–prod) causes “ionic white screen of death” in ios versions 13.5 and 14.4 (both in simulators and real device) but not sure about the real span of version for this behaviour. app works and responds in the background but nothing on screen
Expected Behavior
ionic-angular production build should work without problem in these versions of ios
Steps to Reproduce
create blank ionic-angular app with either capacitor or cordova capacitor: ionic build --prod npx cap sync
cordova: ionic cordova build ios --prod
when running the app no problem in ios 16.0 but white screen on mentioned older versions of ios
Code Reproduction URL
No response
Ionic Info
Ionic:
Ionic CLI : 6.20.3 (/Users/emreakkoc/.nvm/versions/node/v16.10.0/lib/node_modules/@ionic/cli) Ionic Framework : @ionic/angular 6.3.3 @angular-devkit/build-angular : 14.2.7 @angular-devkit/schematics : 14.2.7 @angular/cli : 14.2.7 @ionic/angular-toolkit : 6.1.0
Cordova:
Cordova CLI : 11.0.0 Cordova Platforms : ios 6.0.0 Cordova Plugins : cordova-plugin-ionic-keyboard 2.2.0, cordova-plugin-ionic-webview 5.0.0, (and 3 other plugins)
Utility:
cordova-res : 0.15.4 native-run : 1.7.1
System:
ios-deploy : 1.11.4 ios-sim : 8.0.2 NodeJS : v16.10.0 (/Users/emreakkoc/.nvm/versions/node/v16.10.0/bin/node) npm : 8.19.2 OS : macOS Monterey Xcode : Xcode 14.0.1 Build version 14A400
Additional Information
–prod flag is deprecated since angular 13 but
ionic cordova build ios --configuration production
also did not help and causes the same behaviour
Issue Analytics
- State:
- Created a year ago
- Comments:7 (3 by maintainers)
Top GitHub Comments
Thanks for the report. Can you update your
.browserslistrc
orbrowserslist
file to have the following contents and let me know if it resolves the issue?This also solved the problem for us. Great thought about putting this in the migration notes! Thanks Liam!