search

zhlynn / zsign

Maybe it is the most quickly codesign alternative for iOS12+, cross-platform ( macOS, Linux , Windows ), more features.
BSD 3-Clause "New" or "Revised" License
1.21k stars 373 forks source link

How do I specify two .mobileprovision files? #220

Open moul opened 2 years ago

moul commented 2 years ago

Probably related with #11

We used to use zsign for a long time and everything worked like a charm with a .mobileprovision and a .p12 files, thank you!

We recently added App Extensions in our app, and now the builds are only working when built and signed using XCode, and as soon as we sign/resign them using zsign, they become corrupted.

We gave a look and noticed that the App Extensions requires its own .mobileprovision file. Since App Extensions generates a dedicated binary in the archive, I guess that there is one .mobileprovision file per generated binary.

The error is: this app cannot be installed because its integrity could not be verified

Some links:

/summon @aeddi which managed to provide the two binaries, maybe he can give you some additional info if you need some

Thank you for your help!

orgserj commented 2 years ago

I had a problem with not signing up as there was a watch app in the app! delete solved it

aeddi commented 2 years ago

In our case, we don't want to delete our app extension since it allows us to handle push notifications received when our app is in background through a Notification Service (see @moul's link above).

Our concern is that XCode seems to sign the app and the app extension independently using two distinct provisioning profiles.

thmodz3320 commented 2 years ago

I am also facing this problem without knowing the cause even though using the latest version of zsign

moul commented 2 years ago

Hey @zhlynn, what do you think about this?

Thank you very much for your work

gyke69 commented 2 years ago

this app cannot be installed because its integrity could not be verified

this app cannot be installed because its integrity could not be verified < the latest version of zsign somehow causes that error for some applications and games. i don't think it has to do with the xcode or the app extension which you added to your application.

zhlynn commented 2 years ago

Hey @zhlynn, what do you think about this?

Thank you very much for your work

this should be feasible, try it when I have time

moul commented 2 years ago

hey @zhlynn I don't know how difficult it could be but if you give me some directions, I can try to open a PR?

ghost commented 1 year ago

as a workaround you can unpack the ipa, sign the app extension with one provisioning profile and then sign the app itself with the other provisioning profile (order is important)

emranovin commented 9 months ago

It seems signing app's extensions (in PlugIn folder) is a major problem for lots of people. Does anyone have any plan to add this great feature to our marvelous zsign?

emranovin commented 9 months ago

It seems we need a specific provision profile for each extension. How can I create a proper profile for a special extension? Is it about entitlements? Is it possible to use a wildcard AppID or Should I create a specific AppID for each extension? (it's not possible to choose exactly the same AppID because it must be unique. so what should I choose for AppID?)