Skip to content
This repository has been archived by the owner on Nov 19, 2018. It is now read-only.

will it work if you have AppStore and Enterprise account #8

Closed
romk1n opened this issue Dec 10, 2015 · 11 comments
Closed

will it work if you have AppStore and Enterprise account #8

romk1n opened this issue Dec 10, 2015 · 11 comments
Labels

Comments

@romk1n
Copy link

romk1n commented Dec 10, 2015

Is there support for having both Enterprise and Normal developer account in one project file ? i.e. some bundle ids singed as adhoc and other are as enterprise account.

What would be the advice in such environment ? (two separate repos?)

@KrauseFx
Copy link
Contributor

Yes, use one repository per account / team. Also, as it is now, match doesn't support Enterprise profiles.

@romk1n
Copy link
Author

romk1n commented Dec 16, 2015

Thanks @KrauseFx would be great to also support enterprise accounts! :)

@KrauseFx
Copy link
Contributor

I know, but check out the security section of the readme.

@Elaz
Copy link
Contributor

Elaz commented Dec 20, 2015

Hi @KrauseFx
For supporting enterprise, why not encrypt the profile when adding to git and decrypt when running match? developers will have the passphrase for decryption.
Currently we have an AppStore + Enterprise accounts and I think the fact that there's no enterprise support is the only thing holding us back from using Match. Other than that it looks like an awesome and much needed tool.

@KrauseFx
Copy link
Contributor

@Elaz top secret, but you should try

MATCH_FORCE_ENTERPRISE=1 ./bin/match --type enterprise

or in your Fastfile

ENV["MATCH_FORCE_ENTERPRISE"] = "1"
match(type: "enterprise")

Let me know how that works for you 👍

@Elaz
Copy link
Contributor

Elaz commented Dec 21, 2015

@KrauseFx I've had issues using a lane with match for both appstore and enterprise (two teams, same developer account),
it seems that the wrong certificate is chosen for the second account that is being accessed ('e55f8969dfe2c7b9866b9e19a6f629b9' is one of my crash logs) - it actually tries to take a certificate from the distribution on the appstore account when it should take or search the enterprise one.
I fixed it by adding in runner.rb:41
,,,
cert_type = :enterprise if ENV["MATCH_FORCE_ENTERPRISE"] && Spaceship.client.in_house? && params[:type] == "enterprise"
,,,
and the whole lane went great. Is it a good solution?

Edit: not so great... still having some issues. Trying to figure out what's wrong.
Edit #2: after manually clearing my keychain certificates, nuking all environments, making sure on dev portal that everything is cleared and running my profiling lane, it worked, for me and 4 other developers.

@Elaz
Copy link
Contributor

Elaz commented Dec 23, 2015

I created a PR for it: #48

@KrauseFx
Copy link
Contributor

KrauseFx commented Jan 2, 2016

I'll push a new release in a few minutes, please update and let me know if that works 👍

@Elaz
Copy link
Contributor

Elaz commented Jan 2, 2016

Hi @KrauseFx, Thanks a lot! - The fix works for enterprise account on the release (enterprise) setup - however, I suspect Match doesn't deal with the development setup for enterprise accounts. It looks like this option is missing currently, since if I set it to type "development" but supply the enterprise team id, it will look at the wrong place for the certificate, the developer account on the portal for the appstore account.
To make it clear, even if I didn't have an appstore account, and only enterprise, it would still mix the two when users try to generate a development certificate/profile on the enterprise account. Users must have one on the enterprise account as well to be able to load apps on devices.

This is what I'm getting when the type in match is set to 'development' but the account i'm trying to provision/cert is the enterprise one.
I think this is an issue at the Spaceship+sigh level.
(needless to say, there aren't any revoked certificates on my account...)

[13:44:42]: Certificate 'XXXXXXXXXX' (stored in your git repo) is not available on the Developer Portal
[13:44:42]: for the user xxxxxxxx@xxxxx.com
[13:44:42]: Make sure to use the same user and team every time you run 'match' for this
[13:44:42]: Git repository. This might be caused by revoking the certificate on the Dev Portal

[!] To reset the certificates of your Apple account, you can use the `match nuke` feature, more information on https://github.com/fastlane/match

Thanks again.
I'll be happy to assist in any way.

@romk1n
Copy link
Author

romk1n commented Jan 7, 2016

thank you!

@fastlanebot
Copy link

This issue was migrated to fastlane/fastlane#2011. Please post all further comments there.

fastlane is now a mono repo, you can read more about the change in our blog post. All tools are now available in the fastlane main repo 🚀

@fastlane-old fastlane-old locked and limited conversation to collaborators Mar 12, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants