-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[UTM] App freezes/white screen on launch #32
Comments
I have the same issue on iOS 12.2 on iPhone X. |
Similar issue here, iOS 13.3, iPhone XS |
Same issue on iOS 13.3, iPad Air 3, Jailbroken. |
Same issue, iOS 13.3 iPhone XR, jailbroken. |
This is a known issue and is due to an iOS bug. If an app dies (exception, killed, etc) with |
Same as ppsspp jit debug ver? |
Same issue on iPad Pro 3 12,9" on iOS 13.3 jailbroken |
Same issue on iPad Pro 12.9“ 2018 on iOS 13.3.1 non-jailbroken |
Same issue, iOS 13.2.3 on an iPhone XS, jailbroken |
I believe there are ways around this. I’ll make a PR if I can figure this out. |
Same with iPad Pro 11” on iPadOS 13.3 |
Stuck it in #38, if anyone wants to try it out. |
Thanks, I will test soon! |
It will work again if u installing it on custom bundles, I don’t know why this bug happend |
Would you care to clarify what this means? |
I meant If you installed the app or sign it at different bundle identifier, it will work normal, But the only problem it crashes If you turn any machines |
I see, thank you for the clarification. Edit: I just checked, the app still crashes immediately when it has a different bundle identifier. |
I'm on iOS 13.2, iPhone 11 -- the hardware restart (volume + power button) isn't even working. Not sure how to get this white screen to go away. |
Your problem may be that the hardware restart for the iPhone 11 is actually (click and then release) volume up, then (click and release) volume down, and then (hold down) power button. |
Oh well sure, that may be my problem. That is my problem. Definitely my problem. Thank you. 😅 |
That’s how you normally restart your device. I’m not sure if Apple has a support article detailing how to forcefully power off your device, as it’s presumably not something users normally need to do. |
No worries, that’s the apple page for restarting, not force-restarting. The page that you were looking for is here: https://support.apple.com/en-ca/guide/iphone/iph8903c3ee6/ios |
It might be
Yes as I mentioned before if you installed without changing The bundle it will be white Screen , after installed At different Bundle the it work but crashes If you try to run any virtual machine |
I see, I’ll try doing that and get back to you. |
It’s probably crashing at that point because that’s when the dylibs get loaded, and they’re probably not signed correctly. |
I seem to be unable to do that right now on my phone, would you mind uploading your custom .ipa to somewhere and linking it? |
UTM works correctly on unc0ver. |
@osy86 this issue still occurs on v0.2 fakesigned, even after restarting and ldrestart. |
Ok, so it’s just a general issue then. |
I've never commented on a GitHub issue before so please excuse any informalities, but i'm having this problem too. im running the fakesigned v0.2 build on unc0ver for iOS 13.3. the log suggests that it's a problem loading an outdated dylib but this is just me skimming through it, i could be wrong. i'll attach the crash log that i found. i hope that this is somewhat helpful |
Do you have |
I don't know much about jailbroken systems, but you definitely have libgpg installed. But I can't tell you how to find out what installed it. Don't worry though, I think I have a fix, come back in an hour and I'll give you an ipa to test. |
@osy86 libgpg (aka GnuPG Errors) is installed by unc0ver, and seems to be a requirement for all apt packages. It comes from apt.bingner.com, which I think (but am not sure) is unc0ver's included repo. Link to deb: apt.bingner.com/debs/1443.00/libgpg-error_1.32-1_iphoneos-arm.deb |
@Slapshot300 and any others who are getting crash ON APP OPEN (not launching VM)
|
@osy86 will a release with this done to it be available? Also, just a note, Homebrew is referred to as either Homebrew or Brew. |
There won't be a release until next week. It will have this fix. |
Ok, thanks. |
I have mentioned Before that the app on my iPhone X checkra1n has never facing any issue it will killed properly . So I installed Unc0ver On the same device and since the new version of Unc0ver support old devices Tried to kill the app to see if it will have the bug . And yess it was white screen for the first time So the problem releated only with unc0ver ! so what u may think which prevent to kill the app properly ? |
@osy86 sorry for the late reply, but your fix works perfectly by what i've tested. The app is able to startup and load into a virtual machine without any crashes! |
Please could confirm by this two will u facing any problem: (1) to power off the vm |
Happening to me on iOS 15.4.1 iPad Pro M1. This did not start happening until I tried JITStreamer if that helps. Deleting JITStreamer, AltStore altogether and reinstalling the app still results in white screen. Restarts not helping either. |
iOS 13.3 on iPhone XS.
While not jailbroken, the app itself can be opened as long as it is signed, however, the app will crash right after clicking on any of the VMs. Configuration menu works without issues.
Additionally, the app will crash when a fairly large VM is attempting to be launched even in jailbroken mode (in my case, a Windows XP install with a 2 GB hard drive, it was set up on the device itself and was fully functional until I shut down the VM and attempted to re-launch the virtual machine later on); when reopened, the app will stay on the white splash screen after the initial crash and stop functioning, even after removing the app in the switcher/respringing/su && ldrestart (possibly due to lack of cleanup?). This is also reproducible by shutting down the virtual machine with the power button on the top menu UI; the machine shuts down and the app freezes. Only fixable by rebooting and re-jailbreaking.
The text was updated successfully, but these errors were encountered: