-
Notifications
You must be signed in to change notification settings - Fork 46
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
match + ionic results in provisioning profile error for some reason #56
Comments
The error makes me think it's using the wrong cert because |
Can you post the complete output of running that lane? |
Thinking it was bad/old certs or profiles, I deleted a bunch of them up on the portal. Here's output from the last run where the profile was rebuilt. I still got the same error though.
|
After this build, I can open xcode and set the signing profiles manually, and the app builds, however xcode is acting oddly. First, there's no team set in xcode. Strange since other apps I build under different teams are set correctly. I can select the correct team manually, but it seems I shouldn't have to do that since it was set by fastlane. Secondly. I can select the "Signing (Debug)" profile without issue ("match Development"), but when I go to select the "Signing (Release)" profile, the only "eligible" profile in that dropdown is the "match Development" profile. The "match AppStore" profile is listed as inelligible -- but If I select "match AppStore", the items in that dropdown shuffle around and the "match Appstore" becomes eligible. Very odd. After all of that, xcode will build the app. |
As stated above, I run this lane against a few apps on different teams. Only one of them is showing these errors at this point. I couldn't tell you what the difference between the accounts is. For this broken one, I've deleted all certs & profiles directly in the dev portal - and manually out of |
I take that back - I've managed to break it for another org/team now. :/ |
Signing always is a pain, especially for Ionic Cordova projects, that are set up in strange ways (which they are out of the box). I would create a new Ionic app, and set everything up in a clean way (meaning: no manual changes in Xcode, trying only to use Fastlane for everything and see if you can get it to work as expected that way. If yes, you have your base configuration you can/should create for all other projects to get them to hopefully work. |
I fixed it adding |
My release lane looks something like this, but it ultimately fails with a code signing error (see below). The app gets built though, and if I fiddle around in xcode and change
Signing (Release)
then I can get xcode to build my app for release. But, why doesn't the ionic build command finish successfully? It seems like I've matched my app store profile right before building withionic
- so it should work?Thanks!
(I'm using git_branch and team_id with
match
because I work across multiple development teams)Error:
Code Signing Error: Provisioning profile "match AppStore my.app.identifier" doesn't include signing certificate "iPhone Developer: My NAME (ABCDEF1234)".
The text was updated successfully, but these errors were encountered: