Posts

Post not yet marked as solved
3 Replies
You need to add post-archive action and share artifacts with internal/external testing group. https://www.kodeco.com/36548823-getting-started-with-xcode-cloud#toc-anchor-008
Post not yet marked as solved
3 Replies
There are some changes in app launch behavior with "prewarm", which can lead to problems with keychain. Check this article and documentation: https://sourcediving.com/solving-mysterious-logout-issues-on-ios-15-8b818c089466 https://developer.apple.com/documentation/uikit/app_and_environment/responding_to_the_launch_of_your_app/about_the_app_launch_sequence#3894431
Post not yet marked as solved
5 Replies
As for me, there was crash because of breakpointOnError in production.
Post marked as solved
9 Replies
I have erased my apple watch completely and now it works.
Post not yet marked as solved
2 Replies
Agree, is anything else except Yahoo's Flurry?
Post marked as solved
2 Replies
Any updates about opening web url in WatchOS 7?
Post marked as solved
9 Replies
Same problem on watchOS 7.1 :(
Post marked as solved
34 Replies
I have started get this error again after Xcode 12 release :(
Post not yet marked as solved
1 Replies
Just use universal push key instead of separate id with certificate. And send to {bundleId}.watchkitapp.complication in topic and set apns-push-type to complication. More info: https://developer.apple.com/documentation/usernotifications/setting_up_a_remote_notification_server/sending_notification_requests_to_apns
Post not yet marked as solved
7 Replies
Same problem with passcode in Apple Watch simulator.
Post marked as solved
34 Replies
UPD. I have "stopped using Apple ID" (via iPhone's settings) for main app. And login on watch starts working.
Post marked as solved
34 Replies
Same problem on watch in Xcode 12 beta 6.