Skip to content
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

The profile does NOT match the application's Team ID #149

Closed
markusmoenig opened this issue Aug 25, 2017 · 9 comments
Closed

The profile does NOT match the application's Team ID #149

markusmoenig opened this issue Aug 25, 2017 · 9 comments
Labels

Comments

@markusmoenig
Copy link

My application builds correctly and uploads to itunesconnect without a complaint (I did not submit it yet).

However I cannot execute it locally (instant crash due to an invalid code signature). When verifying the archive, with RB App Checker Lite, I see one error message:

The profile does NOT match the application's Team ID (xxxxxxx)

which refers to the embedded provisioning profile. I am not sure if this the cause of the local execution crash, but I checked all fields and everything seems to be good. And again, it also uploads to itunesconnect.

Any ideas ?

@sethlu
Copy link
Contributor

sethlu commented Aug 25, 2017

Hi @markusmoenig, thanks for filing this issue! The signed app for submission to iTunes Connect is expected to crash at launch... If Apple doesn't come back with complaints, your app should run fine through Mac App Store distribution.

On the issue with The profile does NOT match the application's Team ID (xxxxxxx) I'm not very sure how this is evaluated/resulted. I tested it myself and got the same warning. 😕 I would recommend waiting to hear back from the app review and then see if there are any concrete issues to fix. It shouldn't take a very long time.

@markusmoenig
Copy link
Author

Thanks for the quick reply! The main issue was the crashing after startup, if that is normal all is good. Just thought the two issues were connected (which they aren't I guess).

Thanks!

@sethlu
Copy link
Contributor

sethlu commented Aug 25, 2017

@markusmoenig let us know how the app review goes! I'm curious if the mismatched profile creates any issue. However, I'm pretty sure it will work. 😸

@markusmoenig
Copy link
Author

Thanks! :)

But now I have another issue, I added code signing for my "mac" target too, and now the app just starts with an empty window (which worked fine before signing). Strange.

@sethlu
Copy link
Contributor

sethlu commented Aug 25, 2017

@markusmoenig mhm, that's interesting. Which module did you use to package the app?

Also, if you export DEBUG=electron-osx-sign* (with the asterisk) and run the code signing command with electron-osx-sign, there should be a comprehensive debug log printed. That, I believe I can help you from there.

@markusmoenig
Copy link
Author

I use electron-builder, where shall I insert this ? I searched around for the issue a bit and found some references, but nothing which would help in my case.

@markusmoenig
Copy link
Author

After playing around with things, I noticed that removing the child / inherited entitlement file solves this.

Mine was just the default (like described in https://electron.atom.io/docs/tutorial/mac-app-store-submission-guide/).

Without the child it works fine. Will also remove the child from the mas build now.

@sethlu
Copy link
Contributor

sethlu commented Aug 25, 2017

@markusmoenig the darwin distribution doesn't support app sandboxing. If you supplied to electron-builder the entitlements used for mas, the app can fail to run due to the app sandbox limitation. Are things working fine now?

@markusmoenig
Copy link
Author

@sethlu No, I did not enable sand boxing, if I do this the app just crashes instantly like the mas version. When I removed the child entitlement everything works fine now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants