There are no errors in the dev app, but the release app is simply stuck at white screen after the splash screen. How do I solve this? please help. Also the app which was working and was published on the play store started showing the white screen for some reason.
“dependencies”: {
“@agm/core”: “^1.1.0”,
“@angular/animations”: “~11.0.2”,
“@angular/cdk”: “~11.0.0”,
“@angular/common”: “~11.0.2”,
“@angular/core”: “~11.0.2”,
“@angular/forms”: “~11.0.2”,
“@angular/material”: “~11.0.0”,
“@angular/platform-browser”: “~11.0.2”,
“@angular/platform-browser-dynamic”: “~11.0.2”,
“@angular/router”: “~11.0.2”,
“@ionic-native/app-center-analytics”: “^5.30.0”,
“@ionic-native/base64”: “^5.30.0”,
“@ionic-native/camera”: “^5.30.0”,
“@ionic-native/code-push”: “^5.30.0”,
“@ionic-native/core”: “^5.30.0”,
“@ionic-native/date-picker”: “^5.30.0”,
“@ionic-native/dialogs”: “^5.30.0”,
“@ionic-native/file”: “^5.30.0”,
“@ionic-native/file-path”: “^5.30.0”,
“@ionic-native/file-transfer”: “^5.30.0”,
“@ionic-native/geolocation”: “^5.30.0”,
“@ionic-native/google-maps”: “^5.5.0”,
“@ionic-native/ionic-webview”: “^5.30.0”,
“@ionic-native/mobile-accessibility”: “^5.30.0”,
“@ionic-native/network”: “^5.30.0”,
“@ionic-native/onesignal”: “^5.30.0”,
“@ionic-native/splash-screen”: “^5.30.0”,
“@ionic-native/status-bar”: “^5.30.0”,
“@ionic-native/web-intent”: “^5.30.0”,
“@ionic/angular”: “^5.5.0”,
“@ionic/storage”: “^2.3.1”,
“@ngx-translate/core”: “^12.1.1”,
“@ngx-translate/http-loader”: “^4.0.0”,
“bootstrap”: “^4.5.3”,
“chart.js”: “^2.9.4”,
“cordova-android”: “9.0.0”,
“cordova-plugin-androidx-adapter”: “^1.1.3”,
“cordova-plugin-appcenter-analytics”: “^0.5.1”,
“cordova-plugin-appcenter-crashes”: “^0.5.1”,
“cordova-plugin-appcenter-push”: “^0.5.1”,
“cordova-plugin-appcenter-shared”: “^0.5.1”,
“cordova-plugin-camera”: “^4.1.0”,
“cordova-plugin-code-push”: “^1.13.1”,
“cordova-plugin-datepicker”: “^0.9.3”,
“cordova-plugin-dialogs”: “^2.0.2”,
“cordova-plugin-file”: “^6.0.2”,
“cordova-plugin-file-transfer”: “^1.7.1”,
“cordova-plugin-ionic-webview”: “^5.0.0”,
“cordova-plugin-statusbar”: “^2.4.3”,
“core-js”: “^2.5.4”,
“moment”: “^2.29.1”,
“ngx-order-pipe”: “^2.1.1”,
“node-properties-parser”: “0.0.2”,
“onesignal-cordova-plugin”: “^2.11.1”,
“phonegap-plugin-mobile-accessibility”: “^1.0.5”,
“rxjs”: “^6.6.3”,
“tslib”: “^2.0.3”,
“zone.js”: “~0.10.3”
},
“devDependencies”: {
“@angular-devkit/build-angular”: “^0.1002.0”,
“@angular-devkit/build-ng-packagr”: “^0.1002.0”,
“@angular/cli”: “^11.0.2”,
“@angular/compiler”: “~11.0.2”,
“@angular/compiler-cli”: “~11.0.2”,
“@angular/language-service”: “~11.0.2”,
“@ionic/angular-toolkit”: “^2.3.3”,
“@ionic/cli”: “^6.12.2”,
“@types/jasmine”: “~3.3.8”,
“@types/jasminewd2”: “~2.0.3”,
“@types/node”: “~8.9.4”,
“code-push”: “^3.0.1”,
“codelyzer”: “^5.2.2”,
“com-darryncampbell-cordova-plugin-intent”: “git+https://github.com/darryncampbell/darryncampbell-cordova-plugin-intent.git”,
“cordova-android-support-gradle-release”: “^3.0.1”,
“cordova-plugin-advanced-http”: “^3.1.0”,
“cordova-plugin-appcenter-push”: “^0.5.1”,
“cordova-plugin-device”: “git+https://github.com/apache/cordova-plugin-device.git”,
“cordova-plugin-filepath”: “^1.5.8”,
“cordova-plugin-ionic-keyboard”: “^2.2.0”,
“cordova-plugin-network-information”: “git+https://github.com/apache/cordova-plugin-network-information.git”,
“cordova-plugin-splashscreen”: “^5.0.4”,
“cordova-plugin-whitelist”: “^1.3.4”,
“cordova-plugin-zip”: “^3.1.0”,
“cordova-sqlite-storage”: “^3.4.1”,
“jasmine-core”: “~3.4.0”,
“jasmine-spec-reporter”: “~4.2.1”,
“karma”: “^5.1.1”,
“karma-chrome-launcher”: “~2.2.0”,
“karma-coverage-istanbul-reporter”: “~2.0.1”,
“karma-jasmine”: “~2.0.1”,
“karma-jasmine-html-reporter”: “^1.5.4”,
“ng-packagr”: “^11.0.2”,
“protractor”: “^7.0.0”,
“ts-node”: “~8.3.0”,
“tsickle”: “^0.37.0”,
“tslint”: “~6.1.3”,
“typescript”: “~4.0.5”
},
Generally speaking, don’t upgrade Angular versions past the major version supplied with a currently spawned new project, unless you enjoy being the canary in the proverbial coalmine that spends a lot of time reporting and diagnosing compatibility problems. So if I were you, I would roll Angular back to the highest 10.x versions you can find and see if that fixes your issues.
If you absolutely, positively have to have Angular 11 right now, then make sure that you upgrade everything in the toolchain. I’m specifically looking at @angular-devkit/ things, that look still 10.x. @ionic/angular-toolkit v3 is also needed for Angular 11 support.