Please update to Xcode 7.3 or later
alexandreaugus opened this issue · 3 comments
Hi, I am getting this error using
Xcode Archive & Export for iOS
Version: 4.5.2
Xcode 13.2.x
Any ideas?
Checking development provisioning profiles
Using certificate for development distribution: Apple Development: XXX (XXX)
Checking bundle id: com.XXX
capabilities:
Exporting outputs...
failed to manage code signing: failed to ensure profiles: failed to find profile: failed to query Developer Portal: Apple provided the following error info:
Please update to Xcode 7.3 or later to continue developing with your Apple ID., stacktrace: /Users/[REDACTED]/.rbenv/versions/2.6.9/lib/ruby/gems/2.6.0/gems/fastlane-2.193.1/spaceship/lib/spaceship/client.rb:763:in parse_response' /Users/[REDACTED]/.rbenv/versions/2.6.9/lib/ruby/gems/2.6.0/gems/fastlane-2.193.1/spaceship/lib/spaceship/portal/portal_client.rb:669:in provisioning_profiles_via_xcode_api'
/Users/[REDACTED]/.rbenv/versions/2.6.9/lib/ruby/gems/2.6.0/gems/fastlane-2.193.1/spaceship/lib/spaceship/portal/provisioning_profile.rb:319:in all' /private/var/folders/jw/g2nxpyn956dffdjs0vn8h9nm0000gn/T/1423197095/profiles.rb:21:in list_profiles'
main.rb:46:in `
Hi @alexandreaugus, yesterday i had same issue, Xcode step v4.5, Xcode 13.1, this solution helped me #287 (comment)
Hello there, I'm a bot. On behalf of the community I thank you for opening this issue.
To help our human contributors focus on the most relevant reports, I check up on old issues to see if they're still relevant.
This issue has had no activity for 90 days, so I marked it as stale.
The community would appreciate if you could check if the issue still persists. If it isn't, please close it.
If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me".
If no comment left within 21 days, this issue will be closed.
I'll close this issue as it doesn't seem to be relevant anymore.
We believe an old issue probably has a bunch of context that's no longer relevant, therefore, if the problem still persists, please open a new issue.