eni9889 / ppsideloader

535 stars 129 forks source link

apps++ crashing upon side load and install #177

Closed mycoolbrah closed 7 years ago

mycoolbrah commented 8 years ago

Hey guys, long time lurker first time poster, been side loading since April 2016 and encountered many problems which have been fixable with time, but this time I'm really stuck. I use a lot of ++ tweaks for work purposes so I'm kinda desperate rn.. updated to iOS 10 GM and running newest Xcode 8 beta 8A218a (7th sep release) as I was having issues with older beta of Xcode 8 with iOS 10 GM.. not sure if its something to do with the .plist files, really stuck on this one. Xcode doesn't seem to display any run time errors but the ++ apps just appear as regular apps without the ++ending after they have been side loaded onto my phone. No runtime errors / warnings :| Hopefully its just a temp issue that we can resolve.

avielc commented 8 years ago

I suggest wait till xcode 8 will be official and ios10 will also be out normally from what i saw if you try to run the sideload project it failed on me with trying to sign an app with something unrelated. (trying to insert dylib @executable_path\jailbreak (which doesn't really exists) so that would generate an error and a fail. try to do the procedure manually and it should work (that's how i did it.)

trewq34 commented 8 years ago

Hi I was encountering the same issue with the latest version of Xcode, Snapchat and iOS. I think I managed to find a fix for this, but it requires you to have sideloaded Snapchat before (and it having worked). The latest time i tried that it failed, I was using a bundle identifier which i hadn't used before, and therefore didn't have it setup in https://developer.apple.com/account/ios/identifier/bundle. Xcode did this itself and that's where I believe the issue lies.

I did a recent sideload of Snapchat using my older bundle identifier (which had a successful sideload of Snapchat) and it worked, but this was using an older version of Snapchat. I will sideload the latest using my old identifier and report back.

I'm not sure if it's the way Xcode creates bundle identifiers in the latest versions that apps don't like, or if there's another reason. But doing this gets us a step closer to having sideloaded apps working again (at least for those of us who've done it before).

EDIT: Can confirm, http://imgur.com/a/yM1zx I'll do a bit more playing about with it to see if I can get it working using a new identifier on the same versions of everything. (Using a newly made identifier with the latest version failed too).

P.S. I have an Apple Developer account so I'm not sure if this is something that's needed, but I don't think it is. To be sure, I'll use a different Apple ID.

avielc commented 8 years ago

That's an excellent point! How about using Xcode 7 to create an IPA and then trying to upload it to the iPhone using Dudi's impactor for example.

Sent from my iPhone

On 12 Sep 2016, at 22:48, trewq34 notifications@github.com wrote:

Hi I was encountering the same issue with the latest version of Xcode, Snapchat and iOS. I think I managed to find a fix for this, but it requires you to have sideloaded Snapchat before (and it having worked). The latest time i tried that it failed, I was using a bundle identifier which i hadn't used before, and therefore didn't have it setup in https://developer.apple.com/account/ios/identifier/bundle. Xcode did this itself and that's where I believe the issue lies.

I did a recent sideload of Snapchat using my older bundle identifier (which had a successful sideload of Snapchat) and it worked, but this was using an older version of Snapchat. I will sideload the latest using my old identifier and report back.

I'm not sure if it's the way Xcode creates bundle identifiers in the latest versions that apps don't like, or if there's another reason. But doing this gets us a step closer to having sideloaded apps working again (at least for those of us who've done it before).

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

trewq34 commented 8 years ago

Thanks for the suggestion. I'll give it a go when I'm home.

EDIT: I gave that a go, but as impactor resigns the app, it's off no use. I'm giving it a go on a OS X VM at the moment which has an older version of Xcode 8 Beta installed. Will update with results.

EDIT2: Using a random bundle identifier (following the usual 'com.domain.app' format) didn't work using Xcode 8 Beta 3, where it used to work normally. I will try this again using Beta 3 once I've done some more investigation. Sorry I couldn't be of more help.... yet :/

On Tuesday, 13 September 2016, avielc notifications@github.com wrote:

That's an excellent point! How about using Xcode 7 to create an IPA and then trying to upload it to the iPhone using Dudi's impactor for example.

Sent from my iPhone

On 12 Sep 2016, at 22:48, trewq34 <notifications@github.com javascript:_e(%7B%7D,'cvml','notifications@github.com');> wrote:

Hi I was encountering the same issue with the latest version of Xcode, Snapchat and iOS. I think I managed to find a fix for this, but it requires you to have sideloaded Snapchat before (and it having worked). The latest time i tried that it failed, I was using a bundle identifier which i hadn't used before, and therefore didn't have it setup in https://developer.apple.com/account/ios/identifier/bundle. Xcode did this itself and that's where I believe the issue lies.

I did a recent sideload of Snapchat using my older bundle identifier (which had a successful sideload of Snapchat) and it worked, but this was using an older version of Snapchat. I will sideload the latest using my old identifier and report back.

I'm not sure if it's the way Xcode creates bundle identifiers in the latest versions that apps don't like, or if there's another reason. But doing this gets us a step closer to having sideloaded apps working again (at least for those of us who've done it before).

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/eni9889/ppsideloader/issues/177#issuecomment-246542433, or mute the thread https://github.com/notifications/unsubscribe-auth/AI-IC48tuHZJ3P7GKjfJ6esyWbiz2wnNks5qpfYDgaJpZM4J55qU .

Kind Regards,

Kamran Ali