You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Summary:
Any request for CloudKit will always get CKError - "Internal Error" (1/4000); "Couldn't get a signing certificate". Some of our devices could still connect with CloudKit, some of them couldn't yesterday. But today, all of our devices can't connect with CloudKit and our users also encounter same issues!
Steps to Reproduce:
Launch Loopify App (Apple ID: 1003174079)
You will find there is always "Disconnect with Loopify"
All the errors are the same, CKError - "Internal Error" (1/4000); "Couldn't get a signing certificate".
Expected Results:
Without error, get the records from Loopify (based on CloudKit).
Actual Results:
Disconnect with CloudKit!
Same error: CKError - "Internal Error" (1/4000); "Couldn't get a signing certificate".
Version:
iOS 8.3 and iOS 8.4
Configuration:
iPhone 4s / 5s / 6 / 6 Plus, iPod Touch 4th and iPad. Testing on WiFi and 3G.
Description
Summary:
Any request for CloudKit will always get CKError - "Internal Error" (1/4000); "Couldn't get a signing certificate". Some of our devices could still connect with CloudKit, some of them couldn't yesterday. But today, all of our devices can't connect with CloudKit and our users also encounter same issues!
Steps to Reproduce:
All the errors are the same, CKError - "Internal Error" (1/4000); "Couldn't get a signing certificate".
Expected Results:
Without error, get the records from Loopify (based on CloudKit).
Actual Results:
Disconnect with CloudKit!
Same error: CKError - "Internal Error" (1/4000); "Couldn't get a signing certificate".
Version:
iOS 8.3 and iOS 8.4
Configuration:
iPhone 4s / 5s / 6 / 6 Plus, iPod Touch 4th and iPad. Testing on WiFi and 3G.
Product Version: 8.4
Created: 2015-07-31 03:48:13.761630
Originated: 2015-07-31T00:00:00
Open Radar Link: http://www.openradar.me/22086571
The text was updated successfully, but these errors were encountered: