The same here. I wonder why this happen again and again since last month.
Error: HTTP status code: 500. Internal server error. Error communicating with authentication service. Please try again at a later time.
tualatrix
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
I also meet this bug. Please fix this bug in the next macOS Catalina release.
I find a simple way to reproduce this issue with 100%, and I've reported FB9126429.
Please follow these steps:
Open Apple Music. After that, press CMD+W, make sure there’s no window for Apple Music is opened.
Click Apple Logo and choose “Log out”, make sure the “Reopen windows” is checked.
After login again, you will see Apple Music is appearing the Dock, and no window is open. That’s correct.
If you open Activity Monitor, you will see Apple Music with 8KB memory
Do not try to click Apple Music Icon on Dock, now open the project of TestAEDeterminePermissionToAutomateTarget, build and run. Click the “Grant Permission” button. You will see the App stuck at the method of AEDeterminePermissionToAutomateTarget, with semaphore_wait_trap method call.
If you click the Apple Music Icon on Dock, Apple Music will launch normally, then build and run the again, everything will work fine.
I hope these steps will be helpful so that this bug will be fixed soon. Thanks.
Since I can't upload the Xcode project, here's the core code, you can build your own demo in seconds.
let bundleIdentifier = "com.apple.Music"
let targetAppEventDescriptor = NSAppleEventDescriptor(bundleIdentifier: bundleIdentifier)
let status = AEDeterminePermissionToAutomateTarget(targetAppEventDescriptor.aeDesc, typeWildCard, typeWildCard, true)
debugPrint(status)
After upgrading to macOS Big Sur 11.4 Beta, my app finally got the call of "didRegisterForRemoteNotificationsWithDeviceToken". I hope this is fixed.
One of my two Mac devices has this issue, but them are the same OS version, under the same network.
On the problem Mac, none of "didRegisterForRemoteNotificationsWithDeviceToken" and "didFailToRegisterForRemoteNotificationsWithError" has been called. So wired.
Today I can make deployment from Development to Production, but the deployment issue of searchable index still exists.
Today I tried to deployment Development to Production, it just showed "There was a problem loading the environment's status."