Unable to import Support Files
Symplicityy opened this issue · 56 comments
When trying to import the Support Files, they are grayed out as if they are an unsupported filetype.
Is this installed with AltStore? I think there’s a similar issue on UTM as well. Can you try using https://dantheman827.github.io/ios-app-signer/
Yes it was installed with AltStore. Importing the mobiledevicepairing file worked fine though. I’ll try using iOS app signer right now.
I am still unable to select the files after installing with iOS app signer.
I was able to get the files to appear by using Filza to create a folder named “SupportImages” in the documents folder and copying the files into there. This works for me as a temporary workaround. Assuming iTunes file sharing is enabled, this could also be done on a non-jailbroken device.
Did you use the selector for importing the pairing as well? Or did you open the file? If second can you try the selector and see if there’s the same issue?
I tried that before when I installed the app with iOS app signer. It wasn't grayed out like the other files but when I clicked it to import it nothing happened so I did it the other way instead.
Same thing happens for me, but the files I'm trying to import aren't grayed out. (Tapping them does nothing)
@BluDood what happens if you try to select one?
Nothing happens. Here is a screen recording of what happens when I try https://user-images.githubusercontent.com/70075053/120517468-c6bfbb00-c3d0-11eb-98e6-78e0af9067d6.MOV
@BluDood what happens if you try to select one?
Um sorry, different issue when I run the jitterbugpair script it crates the device pairing file so where is it stored on my mac so I can find it and transfer it to my ios device.
Nvm mind found it its located in a user directory folder
I just wanted to add that I am having the same problems with the support files being grayed out on Altstore installation! I am about to try the App Signer method to see if that will work! I am not going to bother supplying a screenshot because you already know the problems! hahaha
I just wanted to add that I am having the same problems with the support files being grayed out on Altstore installation! I am about to try the App Signer method to see if that will work! I am not going to bother supplying a screenshot because you already know the problems! hahaha
Plus everything happened the same ways as already reported! :)
Hmm I am not able to reproduce both on jailbroken iOS 14.3 as well as AltStore signed 14.5.1. What os are people running?
Hmm I am not able to reproduce both on jailbroken iOS 14.3 as well as AltStore signed 14.5.1. What os are people running?
I am currently on IOS 14.3 unjailbroken
Hmm I am not able to reproduce both on jailbroken iOS 14.3 as well as AltStore signed 14.5.1. What os are people running?
I'm running jailbroken iOS 14.2 (tried in both jailbroken and unjailbroken state) on an iPhone 12 Pro Max.
I am almost positive that I just figured out what is causing the issue and a super easy way to get it working till there's a fix. I copied the 2 files from "iCloud Drive" to "On My Phone" and I was able to import them that way. It must be some kind of a bug with importing certain files from iCloud Drive because the pairing file imports fine through iCloud. Most people probably don't even realize the files are in iCloud because iOS downloads files from Safari into iCloud by default.
I am almost positive that I just figured out what is causing the issue and a super easy way to get it working till there's a fix. I copied the 2 files from "iCloud Drive" to "On My Phone" and I was able to import them that way. It must be some kind of a bug with importing certain files from iCloud Drive because the pairing file imports fine through iCloud. Most people probably don't even realize the files are in iCloud because iOS downloads files from Safari into iCloud by default.
Mine are in On my iPhone, not working
Very weird. I tried putting files into my iCloud and it still works for me. I can't fix this issue until I am able to reproduce it...
Very weird. I tried putting files into my iCloud and it still works for me. I can't fix this issue until I am able to reproduce it...
If I put the files in iCloud, they just get grayed out. Very weird indeed
All right I fixed it with installing it over Appsync unified and not IOS app signer. So its a signing issue
It works just fine for me, signed with iOS App Signer and my dev profile.
This looks like a signing issue. I have seen this happen if the provisioning profile's app id doesn't match the app's bundle id. If using an explicit provisioning profile, such as com.test.123, make sure to change the app's bundle id to the same value, instead of the default com.osy86.Jitterbug.
Quick workaround: it’s possible to add an option to share the files with the share menu
I just have the same problem and I was installed with Abox but not AIstore. However, I just reset my iPad and follow the same step, it just work and have no other problem.
I just want to add that I also recently tried this on my M1 iPad Pro on iOS 14.5 (obviously unjailbroken) and I had the same issue. Copying the files from iCloud to my iPad fixed the issue once again.
I think it's been established that the bug is caused by a signing issue with provisioning profiles's app id not matching the bundle id. It's probably better to install from TestFlight for now.
Did you select the files from iCloud? On my devices, I can select the files from "My iPad/iPhone"
Did you select the files from iCloud? On my devices, I can select the files from "My iPad/iPhone"
No. I was never able to select the files from iCloud. I was only able to select them after copying them to my iPhone/iPad. Apparently installing the TestFlight version should allow you to select it from your iCloud though.
Did you change Bundle ID when you signing it? Maybe because of the Bundle ID.
I think it's been established that the bug is caused by a signing issue with provisioning profiles's app id not matching the bundle id. It's probably better to install from TestFlight for now.
I’m having the same issue. Using TestFlight build 1.2 on iOS 15.0.2 on iPhone 13 pro. Jitterbug doesn’t even have a “on my iPhone” folder listed in the files app for me to try and copy support files manually. It did let me import the mobileprovisioning profile though. Tried AltStore with paid developer account also. Same result. Any ideas?
Not sure if AltStore fixed the bug yet. You have to manually sign. Follow the readme.
You can also sign with: https://github.com/SignTools/ios-signer-service
Not sure if AltStore fixed the bug yet. You have to manually sign. Follow the readme.
You can also sign with: https://github.com/SignTools/ios-signer-service
i just setup the ios-signer-service using my paid developer account and still the same result. mobiledevicepair files import from files app (but not if browsed to from within jitterbug). no Jitterbug folder in 'on my iphone' in files. unable to import support files via files app or browsing via jitterbug.
Not sure if AltStore fixed the bug yet. You have to manually sign. Follow the readme.
You can also sign with: https://github.com/SignTools/ios-signer-service
i just setup the ios-signer-service using my paid developer account and still the same result. mobiledevicepair files import from files app (but not if browsed to from within jitterbug). no Jitterbug folder in 'on my iphone' in files. unable to import support files via files app or browsing via jitterbug.
I tried copying the pairing and support files to another app’s “on my iPhone” folder (chrome in this case) and that worked!
So it was both the manually signing with iOS-signer-service AND copying the files to a “on my iPhone” location first that ended up allowing the files to import.
Thanks for the help!
Copying manually always works. Like I said you have to follow the readme and sign with Xcode. Idk what ios-signer-service is but it probably has the same bug as AltStore.
I beg your pardon @osy, but ios-signer-service is my project and I can assure you that it can sign JitterBug completely fine :)
Copying manually always works. Like I said you have to follow the readme and sign with Xcode. Idk what ios-signer-service is but it probably has the same bug as AltStore.
I followed the readme. Xcode was one of the first things I tried. It, TestFlight and every other signing method has the same issue… no “on my iPhone” folder and can’t import files unless manually copied to another app’s local phone. Jitterbug’s local folder never shows up. Even after getting the files imported, jitterbug still has no “on my iPhone” folder.
Just reporting what I’m experiencing. I really appreciate the JIT magic!
@MrSco I just downloaded https://github.com/osy/Jitterbug/releases/download/v1.2.0/Jitterbug.ipa and signed it using the latest version of ios-signer-service. I used a paid dev account (username and password), all default settings. In-app file importing as well as VPN works great. Are you sure this is exactly what you did? I imported all files from my Downloads folder. I don't think you're supposed to see JitterBug's folder in your Files app.
@MrSco I just downloaded https://github.com/osy/Jitterbug/releases/download/v1.2.0/Jitterbug.ipa and signed it using the latest version of
ios-signer-service. I used a paid dev account (username and password), all default settings. In-app file importing as well as VPN works great. Are you sure this is exactly what you did? I imported all files from my Downloads folder. I don't think you're supposed to see JitterBug's folder in your Files app.
Ya that’s what I did. VPN connects
But now even after getting all the files imported, jitterbug connects to my device and lists installed apps , but I get “ImageMountFailed” when I try select UTM or Dolphin. I’ve tried with and without vpn from a second device. iPhone and an iPad both running iOS 15.0.2.
I’m using the developer image files from 14.5 as that’s the most recent version closest to my iOS version.
Am I doing something wrong?
You can't use iOS 14.X developer image on iOS 15.X. Try (haven't tested):
You can't use iOS 14.X developer image on iOS 15.X. https://github.com/haikieu/xcode-developer-disk-image-all-platforms
Ah the readme links to a repo with only 14.5 as the highest version and says to use the closest version. That probably should be updated…
well i finally got it working... very cool stuff... i notice however, i have to be connected to a wifi ap when using the same device to debug and run app with vpn... is that just a limitation of the vpn tunnel? it needs the connection for the tunnel to run over? or am i doing it wrong?
vpn works great when i'm connected to a wifi ap though! thanks!
@MrSco, how did you get it working on iOS15? Or 15.1. Did those iOS15 links from ViRb3 work for you? I tried importing and doesn't seem to like them. I got the images into Jitterbug via Filza. Only way I could see of doing it.
I get an image mount failed unfortunately.
Yea the 15.x links worked for me ok. Just for importing the files I had to first copy to any app’s local “on iPhone “ folder first, then jitterbug wouldn’t have them greyed out when importing.
Yea the 15.x links worked for me ok. Just for importing the files I had to first copy to any app’s local “on iPhone “ folder first, then jitterbug wouldn’t have them greyed out when importing.
I'm getting mount image failed. I realise after I posted earlier, I had made an error as the dmg was unusually small. It doesn't seem I can just download signature file as it is? Maybe it is cos I am in Firefox on PC? I have the DMG now which is over 11MB in size. I still get Mount image failed. It may be because of the signature.
I am on 15.1, using 15.0 DeveloperDiskImage. I don't see a 15.1 but do see a 15.2.
@MrSco So I got a bit further, the images don't fail to mount now but I do get an error when starting apps. I see this on the device running Jitterbug. It says failed to get the task for process 13099. The numbers will change depending on what application I go to launch.
@MrSco So I got a bit further, the images don't fail to mount now but I do get an error when starting apps. I see this on the device running Jitterbug. It says failed to get the task for process 13099. The numbers will change depending on what application I go to launch.
you have to make sure the app is signed with debug permissions...
Debug entitlement is not necessary. You absolutely need the signature file, though, and it must be the exact one for your image file.
it was for me. got the same 'task for process 13099' error and then i re-uploaded the exact same ipa file but checked that box and then it worked.
Debug entitlement is not necessary. You absolutely need the signature file, though, and it must be the exact one for your image file.
I just tested with app debugging disabled and it works great, but do what works for you.
@MrSco I realized what the problem is. If you look at the bottom of the JitterBug README, you will actually see your exact issue: https://github.com/osy/Jitterbug#launch-fails-with-failed-to-get-the-task-for-process-xxx The description states that this happens when you are trying to use JitterBug to launch an app (like DolphiniOS) which itself does not have get-task-allow (debugging) entitlement. This means that you need to sign DolphiniOS with debugging entitlement, but not JitterBug itself.
@MrSco I realized what the problem is. If you look at the bottom of the JitterBug README, you will actually see your exact issue: https://github.com/osy/Jitterbug#launch-fails-with-failed-to-get-the-task-for-process-xxx The description states that this happens when you are trying to use JitterBug to launch an app (like DolphiniOS) which itself does not have
get-task-allow(debugging) entitlement. This means that you need to sign DolphiniOS with debugging entitlement, but not JitterBug itself.
yes, that's what i was referring too.... UTM and Dolphin ipa's need to have debugger permissions enabled when uploaded/sign
I was finally able to get it working as well. I tried to many other methods, but only thing that worked, was to use that Github/IOS Signer method.
I'm on Windows as well, so I wasn't sure how to get/setup the required? .p12 file, or I didn't use that at first/wrong file maybe and it didn't work.
So I had to go into my Apple Dev account, and request a certificate. Download that. Then I found a tutorial on Youtube, on how to create the .p12 locally, with OpenSSL, and add a password to the .p12 file.
Then I was able to get that Raw Data as the tutorial says/do the rest, and it worked! I didn't enable the Debug option like others said. I just uploaded the Jitterbug.ipa/not Lite. Then I think said to use the existing bundle ID/name maybe even.
As someone said, i think you DO maybe need to have WIFI/Cell signal to run the VPN at first/open an app. But then, you can turn OFF everything networking/go into airplane mode even, and it still works it seems like. If you leave Jitterbug open.
Sometimes it freaks out and says can't find files or something, but I just close Jitterbug/other app i'm trying to open with it, and re-launch Jitter, then it works.
But since I got my pairing file/image files on my phone. Now with Jitterbug, again not lite, and apple dev account, I can launch with VPN and use ONE device/same device to open other apps (JIT enabled), and not have to use my PC/a 2nd phone/etc.
@MrSco I realized what the problem is. If you look at the bottom of the JitterBug README, you will actually see your exact issue: https://github.com/osy/Jitterbug#launch-fails-with-failed-to-get-the-task-for-process-xxx The description states that this happens when you are trying to use JitterBug to launch an app (like DolphiniOS) which itself does not have
get-task-allow(debugging) entitlement. This means that you need to sign DolphiniOS with debugging entitlement, but not JitterBug itself.
DolphiniOS uses get-task-allow they used it for a while since iOS 14.2 from what I know and when using AltStore or another signing program it still works.