You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
iPad running iOS 12 -- Stuck on Splash Screen #22765
The App Store is rejecting my application because of this:
We discovered one or more bugs in your app when reviewed on iPad running iOS 12 on Wi-Fi.
Specifically, App stuck on splash screen.
Everything works fine in the simulator and on my older iPhone. I don't have an actual iPad device to test on, and I see nothing in the simulator logs. Any idea what I can do to fix this? Any idea why it would freeze at the splash screen on iPad but not on iPhone devices?
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, v0.9.7-pre.61, on Mac OS X 10.12.6 16G29, locale en-US)
[✓] Android toolchain - develop for Android devices (Android SDK 27.0.3)
[✓] iOS toolchain - develop for iOS devices (Xcode 9.2)
[✓] Android Studio (version 3.1)
[✓] VS Code (version 1.27.2)
[✓] Connected device (2 available)
• No issues found!
Workaround... by completely removing all Derived Data and all intermediate build files, then building from the command line, then building a release in Xcode, the correct kernel blob is created and the app can progress beyond the launch screen.
Ok, so this is strange. I tried running on the Simulator iPhone and iPad and everything is working fine. Also, a recent build of mine was passed by Apple. (Previous build was rejected because it was stuck on splash screen.) But now, a tester who uses iPad says it doesn't proceed from the splash screen (I asked two people who have iPads to test, and for both of them the problem remains). For an iPhone guy, the app is working fine.
I am unable to debug the issue but can't as everything is working fine on Simulator.
I am experiencing the same issue. I have done around 30 or so successful builds with no issue to iOS and now my app is being rejected being unable to go past the launch (splash) screen on iOS 12.4 on iPad with Wifi. I have tried the suggestions here, but I'm now just being rejected. Despite a fairly large amount of refactoring, there is very little reason I can see in my code or dependencies for this to have happened (in the version which succeeded I added a lot of new dependencies around Firebase, but this succeeded, so I assumed it didn't get stuck on the iPad). I'm going to have to commandeer an iPad to try and see if I can recreate the issue.
It would be helpful to see an example of an app that is reproducing this issue on iPads.
Barring that, we'd like to look at any spindumps or crash logs (Xcode > Window > Devices and Simulators > select iPad > View Device Logs) that happen when the device is stuck.
If you can get a sysdiagnose from the device to check the logs from system_logs.logarchive (please don't post it on GitHub, there's too much personally identifiable information) or watch the Console for the device while it's happening to know if there's any logging when the slash screen first gets stuck that would also be helpful.
Since this seems to be worked around by cleaning DerivedData and flutter cleaning, and we haven't seen reports for more than a year, I suspect this was something like #24887 and was fixed with #42029 and definitely with #70224.
If anyone is seeing this on a recent version of Flutter, please let us know by opening a new bug and completely filling out the template. Closing.
It would be helpful to see an example of an app that is reproducing this issue on iPads.
Barring that, we'd like to look at any spindumps or crash logs (Xcode > Window > Devices and Simulators > select iPad > View Device Logs) that happen when the device is stuck.
If you can get a sysdiagnose from the device to check the logs from system_logs.logarchive (please don't post it on GitHub, there's too much personally identifiable information) or watch the Console for the device while it's happening to know if there's any logging when the slash screen first gets stuck that would also be helpful.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
jeffmikels commentedon Oct 6, 2018
jeffmikels commentedon Oct 9, 2018
Workaround... by completely removing all Derived Data and all intermediate build files, then building from the command line, then building a release in Xcode, the correct kernel blob is created and the app can progress beyond the launch screen.
Hixie commentedon Oct 23, 2018
cc @chinmaygarde any ideas?
Hixie commentedon Oct 23, 2018
or cc @xster
saeedjassani commentedon Dec 22, 2018
@jeffmikels I followed the workaround but still facing the same issue. Any fix/alternate workaround?
zoechi commentedon Dec 22, 2018
Similar to #24887, #25167
saeedjassani commentedon Dec 22, 2018
Yes, I tried that too. Still not working :(
zoechi commentedon Dec 22, 2018
In this case we would at least need more information about what's different in your case.
saeedjassani commentedon Dec 23, 2018
Ok, so this is strange. I tried running on the Simulator iPhone and iPad and everything is working fine. Also, a recent build of mine was passed by Apple. (Previous build was rejected because it was stuck on splash screen.) But now, a tester who uses iPad says it doesn't proceed from the splash screen (I asked two people who have iPads to test, and for both of them the problem remains). For an iPhone guy, the app is working fine.
I am unable to debug the issue but can't as everything is working fine on Simulator.
32 remaining items
jerryzhoujw commentedon Aug 10, 2019
Remove
DerivedDataare the point for me.mulderpf commentedon Sep 5, 2019
I am experiencing the same issue. I have done around 30 or so successful builds with no issue to iOS and now my app is being rejected being unable to go past the launch (splash) screen on iOS 12.4 on iPad with Wifi. I have tried the suggestions here, but I'm now just being rejected. Despite a fairly large amount of refactoring, there is very little reason I can see in my code or dependencies for this to have happened (in the version which succeeded I added a lot of new dependencies around Firebase, but this succeeded, so I assumed it didn't get stuck on the iPad). I'm going to have to commandeer an iPad to try and see if I can recreate the issue.
GyuriMajercsik commentedon Oct 4, 2019
This just happened to us as well:
_
_
iKK001 commentedon Jan 5, 2020
What helped in my case I have documented here...
Maybe somebody from the Flutter community with more knowledge about Flutters startup pickups can explain why the above workaround helps...
jmagman commentedon Jan 23, 2020
It would be helpful to see an example of an app that is reproducing this issue on iPads.
Barring that, we'd like to look at any spindumps or crash logs (Xcode > Window > Devices and Simulators > select iPad > View Device Logs) that happen when the device is stuck.
If you can get a sysdiagnose from the device to check the logs from system_logs.logarchive (please don't post it on GitHub, there's too much personally identifiable information) or watch the Console for the device while it's happening to know if there's any logging when the slash screen first gets stuck that would also be helpful.
Please make sure you're following all the instructions at https://flutter.dev/docs/deployment/ios#create-a-build-archive.
This could be a form of #37850. This could be helped by #38992 if the issue was some cached bits in DerivedData.
davoodio commentedon Jun 12, 2020
Solved for me:
Delete pods folder and podfile.lock
flutter clean
flutter build ios --release
Let's finish
Then Run in emulator via xcode. Its working now.
ljmatan commentedon Apr 6, 2021
jmagman commentedon May 27, 2021
Since this seems to be worked around by cleaning DerivedData and
flutter cleaning, and we haven't seen reports for more than a year, I suspect this was something like #24887 and was fixed with #42029 and definitely with #70224.If anyone is seeing this on a recent version of Flutter, please let us know by opening a new bug and completely filling out the template. Closing.
github-actions commentedon Aug 1, 2021
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.