What’s the best way to debug when my app works without an error on web and Android but gives me white screen of death on iOS (and no useful info when I run the app using ionic run ios -l -c). I’ve tried disabling and removing all plugins but nothing I’ve tried has shed any light on this.
and the plot thickens. I decided to test this app on iOS 10 (beta 7) and then I can build it and it opens up just fine, but not on my other device running iOS 9.x. I’m just so lost, hope someone can shed a light on what I’m doing wrong.
Are you using IndexedDB of some sort? You’re probably using a technique which isn’t supported on ios9. You could check it by using the safari debugger.
Thanks for the suggestion. I do however think I’ve figured it out and it was such a stupid error. I’ll have to verify it when I get home tonight but out of pure coincidence I opened the app in Safari (usually I have chrome running) and then I saw a JS error which Chrome didn’t flag. Safari showed me a white screen but as soon as I fixed that error Safari ran the damn thing. So crossing my fingers that this might have solved it. WIll write up a better answer tonight if this is the case. Oh, and I had tried WKWebView but that did not work either.
So, I can confirm now that the cause of the white screen of death was iOS 9 did not like when I set a default parameter value for a function. So this is not acceptable:
@UrbanMania, just for the record, I had the WSOD problem when I migrated from UIWebView to WKWebView. I could only resolve it executing these instructions step-by-step.
When i return on webview after I playing a video with cordova jwplayer plugin, I have the blank white screen, but the html is there but not displayed.
Cordova jwplayer plugin is another app and when I return on my ionic app, I have get the White Screen Of Death.
i have same problem in iPhones only am getting white screen on back button navigation tried with $timeout it did not help . Here is my environment on iOS.
I remember getting this at some point, can’t for the life of me remember what caused it. Make sure you look for responses from other services that might be a promise that has not returned when you are trying to use the response. I had some errors like that at some point.