fastlane: Provisioning profile 'xxxxxxx' is not available on the Developer Portal

New Issue Checklist

Updated fastlane to the latest version
I have read the Contribution Guidelines

I’m develop one app in iOS and I have a problem with the match option, when I put the “match development” this show me a error: (I send you an image with this error)

I do not know which is the reason or what I have doing for resolve that.

I hope that you can help me or give me a way to clear this issue.

Complete output when running fastlane, including the stack trace and command used

[17:39:55]: Provisioning profile '7336147a-257c-4a3d-b9be-087a67b8cee9' is not available on the Developer Portal
[17:39:55]: for the user dev@chatloud.com
[17:39:55]: Make sure to use the same user and team every time you run 'match' for this
[17:39:55]: Git repository. This might be caused by deleting the provisioning profile on the Dev Portal

Configuration Files

Please copy the complete content of your Fastfile and any other configuration files you use below:

Fastfile:

# INSERT CONTENT HERE

Environment

fastlane version (run fastlane -v):

Do you use bundler to execute fastlane (i.e. bundle exec fastlane)?

Do you use a Ruby environment manager (e.g. chruby, rbenv, rvm)?

About this issue

Original URL
State: closed
Created 8 years ago
Comments: 36 (5 by maintainers)

Most upvoted comments

@davideme You can manually delete profiles (dev and appstore) from your certs repo and then recreate it with match development -a com.company.appname

philipshurpik on Sep 2, 2016

In my case, I think it is probably because the fix issue button.

Is there a way to to only renew that specific provisioning profile instead of nuke all distribution because we also have some other distribution profiles that we don’t want to remove them.

I don’t know nuke all will cause a problem for us or not because all the our distribution profile is enterprise distribution and it may cause the app to be unable to install for current app version if we nuke all the profile (Someone please correct me if I’m wrong)

Thanks.

sainttail on May 13, 2016

Confirm, that manually deleting broken stuff from a git repo, fixes the problem. Maybe we should have a possibility to do it via match itself?

jaroslavas on Nov 9, 2016

But I think match should be able to ask to recreate if the provisioning if not found on dev portal (y/n). The first thing that came to my mind at that time was to nuke everything (recreate the certs) 😦.

hlung on Nov 3, 2016

@philipshurpik omg your suggestion works! delete pp from repo and recreate with match development -a com.company.appname

hlung on Nov 9, 2016

@davideme What happens if you delete the profile on ADP? It seems like if you delete it in the repo and there you’ll be able to get up and running.

TKBurner on Sep 2, 2016