This happens in sandbox and TestFlight, I don't know about production. I haven't released the update with the in-app purchases yet. I've written feedback in feedbackassistent.

This looks related to my problem with IAP pricing. See this thread. I see the same for one of my in-app purchases. I've set the price to 1.99 € / 1.99 $, but in the app 2.29 € is shown. It looks like it is actually setting the price to another tier. Another possible reason might be an upcoming price change in the App Store. Are you setting the price for the entire app or an in-app purchase?

From what I'm seeing today App Store Connect has recovered. It is much faster today and I can edit my in-app purchases. Nevertheless, the issue with the prices still exists. Maybe we should open another thread to raise awareness on this one.

And I've detected another issue. The interface for setting the price of an IAP is out of sync with what is actually set. For instance, I changed the price to $6.99 and in the app it displayed $7.99. Later I changed it to $5.99 and the app displayed $6.99. I think the frontend is setting the wrong value in the backend.

It looks like the same problem I'm having since yesterday. See here: forum thread. There might be some problems with IAP in App Store Connect.

I have the same issue with sandbox testers that I have added in the past. The only way I could get this working is by adding a new sandbox test user. I've also tried to remove a tester and add them again, but the system would not let me do that. There is always the same error: A user with this email address already exists on this team

This is not a problem with WKWebView. It's a general issue with dispatch semaphores in the current beta of iOS 15. It's acknowledged as a known issue under Debugging in the release notes of iOS 15. See: https://developer.apple.com/documentation/ios-ipados-release-notes/ios-ipados-15-beta-release-notes Under Debugging > Known issues Using dispatch semaphores in an iOS app running in a device simulator on a Mac with Apple silicon running macOS 11 will cause the app to crash. (81783378) There is also a workaround for this issue: Workaround: In Xcode, select Product > Scheme > Edit Scheme, then deselect Run > Options > Queue Debugging > “Enable backtrace recording.” This workaround is working and solved this problem for me. I can now work with the simulator again. I need to have a closer look at the release notes in the future to spot this issues earlier.

I have the same problem here. Whenever I'm trying to show a WKWebkitView in a SwiftUI environment the app stops with the following error: Thread 8: EXC_BREAKPOINT (code=1, subcode=0x1053a8530) And this stack trace: #0 0x00000001053a8530 in _dispatch_sema4_timedwait.cold.3 () #1 0x0000000105371f84 in _dispatch_sema4_timedwait () #2 0x0000000105372508 in _dispatch_semaphore_wait_slow () #3 0x0000000196af2a0c in _copyResultPreferenceXPCCall(__CFString const*, bool, void const*, bool*) () #4 0x0000000196af1ea8 in MAPreferencesCopyProfileValue () #5 0x0000000196af20a0 in MAPreferencesCopyProfileValueWithExpectedType () #6 0x0000000196aefcc8 in MACaptionAppearancePrefCopyPreferredLanguages () #7 0x0000000196aeb990 in MACaptionAppearanceCopySelectedLanguages () #8 0x000000018af971c0 in WebCore::CaptionUserPreferencesMediaAF::platformPreferredLanguages() () #9 0x000000018921c244 in invocation function for block in WebKit::WebProcessPool::setMediaAccessibilityPreferences(WebKit::WebProcessProxy&) () #10 0x0000000105370028 in _dispatch_call_block_and_release () #11 0x0000000105371828 in _dispatch_client_callout () #12 0x0000000105374118 in _dispatch_queue_override_invoke () #13 0x0000000105383d24 in _dispatch_root_queue_drain () #14 0x0000000105384814 in _dispatch_worker_thread2 () #15 0x00000001c80effec in _pthread_wqthread () Enqueued from com.apple.main-thread (Thread 1) Queue : com.apple.main-thread (serial) #0 0x0000000105375c54 in dispatch_async () #1 0x000000018921c1b0 in WebKit::WebProcessPool::setMediaAccessibilityPreferences(WebKit::WebProcessProxy&) () #2 0x00000001892e5110 in WebKit::WebProcessPool::initializeNewWebProcess(WebKit::WebProcessProxy&, WebKit::WebsiteDataStore*, WebKit::WebProcessProxy::IsPrewarmed) () #3 0x00000001892e5490 in WebKit::WebProcessPool::createNewWebProcess(WebKit::WebsiteDataStore*, WebKit::WebProcessProxy::IsPrewarmed) () #4 0x00000001892e6ac0 in WebKit::WebProcessPool::processForRegistrableDomain(WebKit::WebsiteDataStore&, WebKit::WebPageProxy*, WebCore::RegistrableDomain const&) () #5 0x00000001892e6ddc in WebKit::WebProcessPool::createWebPage(WebKit::PageClient&, WTF::Ref<API::PageConfiguration, WTF::RawPtrTraits<API::PageConfiguration> >&&) () #6 0x0000000189648214 in -[WKContentView _commonInitializationWithProcessPool:configuration:] () #7 0x0000000189648cac in -[WKContentView initWithFrame:processPool:configuration:webView:] () #8 0x00000001891667f0 in -[WKWebView _initializeWithConfiguration:] () #9 0x00000001891679ec in -[WKWebView initWithFrame:configuration:] () #10 0x0000000104f8a404 in @nonobjc WKWebView.init(frame:configuration:) () #11 0x0000000104f896a0 in WKWebView.__allocating_init(frame:configuration:) () I'm using an M1 MacBook Air with macOS 11.5.2, Xcode 13.0 beta 5 (13A5212g) and the iOS 15 simulator. This only happens on the simulator. It works just fine on my iPhone SE 2020 running iOS 15 beta 8. I also see this somewhat cryptic message in the debug, both when running on simulator and on device: Writing analzed variants.

I've updated to iOS 15 Beta 7 and the device is now working again. This was probably fixed in beta 6 or 7. Thanks Apple. This post should be marked as resolved/answered.

I have the same problem with Xcode 13.0 beta 5 (13A5212g) and an iPhone SE 2020 with iOS 15.0 (19A5318f). Xcode is stuck making the iPhone ready for development.

I worked around this issue by starting Jenkins as LaunchAgent instead of a LaunchDeamon, similar to the solution posted in this stackoverflow post - https://stackoverflow.com/questions/62875323/xcode-12-beta-cannot-find-simulator-runtime. That way it runs as a real user and everything works as expected. There is one caveat with this solution! The jenkins user has to be logged in. I needed to turn on Automatic login for the jenkins user on my Mac mini. That's not great, but at least I can use my build server again. If someone needs more details of my solution, just leave a message here and I will post some more details.

I'm having the same problem on my Mac mini Jenkins CI/CD server. Here's my environment: macOS Catalina 10.15.6 Jenkins 2.257 Xcode 12 (12A7209) - downloaded from the App Store fastlane 2.160 - for automating all the things around build, testing, deployment etc. When I run a build from inside Jenkins, it fails with the above error. When I ssh into the machine, fetch from github and run a build via fastlane directly everything runs through. I stumbled across this stackoverflow post - https://stackoverflow.com/questions/62875323/xcode-12-beta-cannot-find-simulator-runtime where workaround is posted, but looks like a bad hack for me and can only be a temporary solution. What is the root cause of this problem? Why aren't the simulator environments available in a Jenkins job environment?