-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Enterprise Account - Ad Hoc cert issues. #12133
Comments
There were 2 "distribution" certs in the portal at this time due to debugging this issue. |
Apparently Apple has changed something in the APIs and all "distribution" profiles are now considered "in-house" for enterprise accounts. Recommend
|
@logancautrell Thanks for bringing this up! I will look into this 👌 |
@joshdholtz any news about this issue I am not able to create an adhoc provisionning profile :(, if no one is looking at it, I can try to do a fix. |
As a work around, you can manually modify
That is how I've been working around the issue :) |
@barrault01 Ah sorry, this issue got lost in the shuffle! I 💯 agree this is misleading. I will look into fixing this one. And @logancautrell's temporary solution will solve this (for now) 👌 Thanks for commenting that! |
I forced returned Spaceship.certificate.in_house.all in place of Spaceship.certificate.production.all on the last else of the part @logancautrell quote. It fixed it for the moment. |
Heyyy 👋 I have an open PR out for this fix ^ |
New Issue Checklist
Issue Description
I have an enterprise account and attempting a
fastlane match --verbose adhoc --force
.When issuing this command fastlane will generate the cert in the developer portal and it is installed correctly in my keychain. However, Spaceship is reporting the certs in
Spaceship.provisioning_profile.InHouse
not inSpaceship.certificate.production
source filefastlane-2.86.2/sigh/lib/sigh/runner.rb
Here is the debug code i added to print the info.
Yeilds:
Complete output when running fastlane, including the stack trace and command used
Environment
The text was updated successfully, but these errors were encountered: