-
Notifications
You must be signed in to change notification settings - Fork 77
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
codesigning issue with free developer account #113
Comments
Try using -c |
With
|
Drop the -a, its no longer needed |
Thanks for the responses. Still seems the same.
For completions sake from Console.app
|
Hey @leonjza, did you get it working? I wrote up some ways to fix https://gist.github.com/rustymagnet3000/605c333519cd265c7eac9d556f46dc75 Hope it helps. I spent a long time getting |
I did not with applesign, but using this tool I was able to get the signing to work: https://github.com/DanTheMan827/ios-app-signer |
I am experiencing similar issue, and found out that adding |
@leonjza can you confirm the issue is gone? |
@trufae I have to test this myself still, but have heard of some folks still experiencing this. Will feedback with my own results soonest. |
Stolen advice from @Siguza, check what you're allowed to sign with first:
|
Just tested this again, same issue. ios-app-signer however still works. |
I'm able to reproduce this - will try to get a PR in to fix it tomorrow. |
@leonjza When you have a chance, can you try signing with
|
@dki hah! That worked!
|
@leonjza I think there must be different restrictions on free accounts vs. paid that enforce the bundle ID matching between the provisioning file and the ipa. In any case, glad we found a solution! Thanks for reporting it! |
Yeah I also suspect free accounts are to blame here. I'll update the use case in objection to extract the bundle identifier from the mobile provision and set that, regardless of account type for now. Appreciate you looking into this @dki :D |
Happy to help @leonjza! I updated the wiki page as well (https://github.com/nowsecure/node-applesign/wiki/Setting-up-your-resigning-environment#re-signing) to be a bit more explicit about what options work with free accounts too. Feel free to point folks there if you hear of similar issues! |
For free accounts, the bundleid needs to be set. (see: nowsecure/node-applesign#113). A hecky fix to shell out and grep that out of the mobile provision is added. It can also be manually set to something else with the `--bundle-id` flags. Fixes #434
Hi @dki , I've experienced an error while installing the application after I signed it. applesign -m embedded.mobileprovision -i F65C7C7C47767CE97C0FFEFC351726AED5BFB7B0 -I frida-gadget-12.9.7-ios-universal.dylib -c -a Sample.ipa then when I try to install it using ideviceinstaller. This is the error: But when I tried to use IOS App SIgner and tried to patch it again with applesign to inject Frida it worked. I'm using a Free Developer Account. Any help will do! |
@kaleb-g What happens if you try signing with the
|
Hi @dki Different errors occur still when installing the resigned IPA. "Install: PreflightingApplication (30%)ERROR: Install failed. Got error "AppexBundleIDNotPrefixed" with code 0x00000000: Appex bundle at "/var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.xMsKhk/extracted/Payload/Sample.app/PlugIns/OneSignalNotificationServiceExtension.appex" with identifier "com.sample.OneSignalNotificationServiceExtension" does not have expected identifier prefix "com.PT.sample-." |
@kaleb-g I'm going to move discussion to the new issue you opened. |
Hey, I'm hoping I am just being dumb here, but it seems like signing using free developer accounts may be broken at the moment? Using DVIA as an example app, I get error code
0xe8008001
when trying to install a resigned app. I am not really sure why.To reproduce
Using a mobileprovision generated using a blank app deployed to an iPhone, I would first run
applesign
:Next, I would deploy the resultant IPA to the device which bails with the aforementioned error:
Device logs have these:
The text was updated successfully, but these errors were encountered: