Communication with apple failed

Communication with Apple failed A non-HTTP 200 response was received (400) for URL https://developerservices2.apple.com/services/QH65B2/ios/submitDevelopmentCSR.action?clientId=XABBG36SBA

Has someone run into this problem in Xcode?

I was trying to run a sample iOS project on real device with personal team. with automatically manage signing on. But Xcode show the error:

At first I thought this is a problem with apple’s server. But 4 days later I still have this problem in my Xcode.

There are similar topics on apple developer forum but with no replies

Answers

here is the request failed detail:

2018-11-29 02:00:01 +0000 IDEProvisioningLedgerEntry: 2018-11-29 02:00:01 +0000 IDEProvisioningLedgerEntry: Sending request 7D28B80A-3C7B-4535-A776-92FB191DF18B to for account weizhou.feng@***.com. Payload:

«Accept-Encoding» = «gzip, deflate»;

«X-Xcode-Version» = «10.1 (10B61)»;

csrContent = «——BEGIN CERTIFICATE REQUEST——\nXMIICRTCCAS0CAQAwADCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAKhR\nFsNrgoA44yDw2z2FhGnommbnAuEfY/GQhjbfo2uqKyOvJnMIfn5fc4LNK20/Vhs4\nSAIDSJFYIWmlq2Ryof1bRY523Gllz8BQgoI+u9lFw6mK3kq9tIaUJ2cCwdEvOxkY\nDg9VbTUYQ7fM37Bvc49WWKHMHJsJzqOIA9rPHJNzNqIFf9Euj25ezl5JJpWdx4LM\nQbOM8x6CijHDE0PeEtnvswXOKkH1/UlMs0AjdL9LlezynfVK320ZAe+2Af5zo2PN\nhH1knWdwHKE5lznbJAZ5boKvwoc2l6uKQp5JqFwznWQaj0CK1PQ6YbeNHaub+sUh\nTcnl62AbLH0GR7Je/NkCAwEAAaAAMA0GCSqGSIb3DQEBBQUAA4IBAQAXiTPOkM5R\nXa6FJnCEtr3CR95w364T3Fqv9siIZmq6E6YRJr55jMsE718MZasd359EupurrF2h\nBcV9hazty7JxIxdVbZuO0XsOjYEwjJ03n2U50JVMkXckxxqP5E2NC8QA+Y5VTxWH\nragBA32I5vr68qmbwDB2sMUleChgJ5InqRa0FAmTe0FBn3Kk2UfXy3qmRALsEJIx\nmWsThlY3545uRNLSTYsSolFsGIII2+2z6c5cWLEF371pyFI8DiQuRUFbnXm1pwix\nSuekfKOVez8bWPmffVBQ65QeABeo/+Tf2D3AKBLut7WuTeb+lKU5Z9TK64it8YEQ\nXRem8vVxrBnt\n——END CERTIFICATE REQUEST——\n»;

2018-11-29 02:00:02 +0000 IDEProvisioningLedgerEntry: 2018-11-29 02:00:02 +0000 IDEProvisioningLedgerEntry: Received response for 7D28B80A-3C7B-4535-A776-92FB191DF18B @ . Error = Error Domain=DVTPortalResponseErrorDomain Code=0 «Communication with Apple failed» UserInfo=

2018-11-29 02:00:02 +0000 IDEProvisioningLedgerEntry: 2018-11-29 02:00:02 +0000 IDEProvisioningLedgerEntry: Response payload: HTTP 400 Bad Request

Источник

A non-HTTP 200 response was received (400) for URL https://developerservices2.apple.com/services/xxx

Has someone run into this problem in Xcode?

I was trying to run a sample iOS project on real device with personal team. with automatically manage signing on. But Xcode show the error:

At first I thought this is a problem with apple’s server. But 4 days later I still have this problem in my Xcode.

There are similar topics on apple developer forum but with no replies

here is the request failed detail

2018-11-29 02:00:02 +0000 IDEProvisioningLedgerEntry: 2018-11-29 02:00:02 +0000 IDEProvisioningLedgerEntry: Response payload: HTTP 400 Bad Request

2 Answers 2

A week ago I started to run into the same problem. I tried the following:

I logged into the Xcode bot user on the bot machine and opened Keychain Access. It showed several expired Xcode bot certificates. I deleted them and tried again. No success.

I deleted and recreated the whole Xcode bot user. No success. Keychain Access now showed that the «Xcode Server Builder» certificate was invalid (not expired).

I manually trusted the «Xcode Server Builder» certificate in Keychain Access WITH SUCCESS! Now the bots were building again.

This said, I do not know what the root of the problem is. At least this is a way to work around the problem.

I had the same issue, and there were 3 simultaneous problems.

Our Apple Developer Agreement had expired. When logged into developer.apple.com/account there was a large banner saying our Account Holder had to accept new terms and condtions. I also could not access certificates or profiles until that was done.

Also one of my signing certificates had expired.

Xcode server was using an alternate certificate from the expired one. That has a missing private key. So I had to export the private key from KeychainAccess on my computer and install it on the bot server.

Then I archived my project and exported it manually on the bot server Xcode, so Xcode would download or update any other certificates and profiles it used. After that, I was able to do a remote bot build on the project.

Источник

App Store Connect Upload Error «You haven’t been given access to cloud-managed distribution certificates»

Uploading an iOS app to App Store Connect with Xcode (Automatically manage signing) and received this error:

The following errors occurred while locating and generating signing assets. .

Communication with Apple failed. You haven’t been given access to cloud-managed distribution certificates. Please contact your team’s Account Holder or an Admin to give you access. If you need further assistance, contact Apple Developer Program Support at https://developer.apple.com/support

• the cert is installed and valid
• I have access to Certificates, Identifiers & Profiles

2 Answers 2

If you have the Admin rights, you can enable this for anyone with Developer role if you

1. Go to App Store Connect
2. Select the «Users and Access» tab
3. Select the right person and under Additional Resources, check both

• Access to Certificates, Identifiers & Profiles and
• Access to Cloud Managed Distribution Certificate .

If you don’t have the Admin rights, you have to ask someone from your organization with Admin rights to do this for you.

the cert is installed and valid

That doesn’t matter. New in Xcode 13, if you choose Automatic signing, Apple tries to do cloud-based signing; it doesn’t even see the certificate that’s on your computer.

But you do not have the cloud-based signing privilege, so it fails.

You have two choices:

Get the privilege. It is really worth it, because cloud-based signing is great! It allows you to distribute from an archive to App Store Connect without having any distribution identity or distribution certificate at all. This totally solves the problem that there’s only one distribution certificate at a time.

Switch to manual signing. Now the distribution certificate on your computer will be used. You’ll need explicit access to the distribution profile too, obviously; the whole export resigning will be manual. That might be simplest if you’re in a hurry.

Источник

Xcode 10 Failing to download provisioning profiles

Xcode can’t download provisioning profiles, I m getting the error:

Error Downloading Profiles

Xcode encountered a problem downloading profiles for team XXX with account xxxxx@xx.com

The error detail:

Error Domain=IDEProvisioningPortalErrorDomain Code=3 \»Communication with Apple failed\» UserInfo=

• I tried to restart Xcode, Mac but it’s not working!
• I also tried to remove my account and add it again
• I can login to my account via web
• I can download provisioning profiles from developer portal and install them

1 Answer 1

Looks like a bug with Xcode 10, and it was observed earlier with Xcode 8 as well as stated at Xcode Profiles Won’t Download

As a workaround, you can try the following steps,

1) Visit developer.apple.com in Safari

2) Click Account and sign in

3) Click on Certificates, Identifiers, and Profiles

4) Navigate to the profile you’re interested in and download it

5) Drag the downloaded profile onto Xcode’s icon in the dock.

At this point, your profile will be installed on your Mac and usable within Xcode.

Источник

iOS App Groups no longer working

Just over a year ago I signed up for a free Apple developer account. All went well, I was able to build apps and deploy on my iPhone.

One of the apps also has an a Today extension and I created an app group to share data. The provisioning profiles I generated expired, and I can no longer deploy the app on device. It works fine on Simulator, of course.

When I build, I get this error:

None of the valid provisioning profiles allowed the specified entitlements: com.apple.security.application-groups.

If I click «Fix issue», I get this:

Communication with Apple failed

Your account does not have sufficient permissions to modify containers.

Going to Capabilities (both the app and the extension have the same issue), in App Groups, I see this error

Again, «Fix issue» doesn’t do anything. Completely disabling App groups works, but I need this.

I opened the expired .mobileprovision files and noticed that under Entitlements->com.apple.security.application-groups, the group is there, while in the new files, the array is empty. And the most weird part is that somehow the group is there since it appears in XCode and I can select it, but just not in the right place, and this is probably why I get those errors.

I tried cleaning and building the project, deleting all provisioning files, certificates, I created a new project, I tried to create a new group but it didn’t work (it just appeared in red), but I’m all out of options.

Источник