I imagine it’s about user experience (you are far more likely to have both phone and watch together than iPad and watch), but if you have a good use case, let Apple know https://www.apple.com/feedback/

Usually you need to go back up the stack trace a bit to understand why the system code might have thrown an assertion. It looks like the last time it was in your code was 3 Africa #2 0x100c630ec one-time initialization function for videos + 152 (VideoListItem.swift:21) and the error message Africa__2/CodeableBundleExtension.swift:14: Fatal error: Failed to locate video.json in bundle. should be a big hint too.

This seems to be working for me (this is on iPad) but in general, file a bug against the App Store https://feedbackassistant.apple.com

This is happening to me today. Most of my QA team uses TestFlight, so they have not been able to test the build that App Store Review just OKed.

I don’t know the complete answer, but I think the issue was that changing the signing settings didn’t actually sign the app (because Xcode didn’t rebuild it). If I delete the executable, it will be rebuilt with proper Xcode local signing.

I have the opposite question: how to I get this to show up on iPadOS 14? The organization problem is the same, so I would love to have the automatic organization.

I recently got a report which I believe is the same thing, on iPhone8,2; iOS 13.3.1.And looking at the crashes for another app, there are at least 3 in -[GKNotificationBannerViewController supportedInterfaceOrientations].

Ah, it looks like I can add-webkit-text-size-adjust: none;to my CSS and WKWebView will use the size I specify. I didn’t see this documented anywhere…

Right, but knowing your use case might help someone give you a solution.

The documentation says “As a general rule, trust the system to determine whether it should play feedback.” It’s harmless to use a UIFeedbackGenerator on a device that doesn’t support haptics. What would you do differently?