I built a simple demo app that implements the code that Apple provides here for instantiating an WKWebView.
https://developer.apple.com/documentation/webkit/wkwebview
This code causes a crash when launched from Xcode but I don't seem to have a problem if I run the installed app directly from the simulator.
Has anyone else run into this issue while testing iOS 15? Are there new considerations that I need take into account when migrating my app to support iOS 15?
I'm running Xcode version 13.0 beta 5 (13A5212g).
Thank you!
Here's the backtrace:
* thread #7, queue = 'com.apple.root.default-qos', stop reason = EXC_BREAKPOINT (code=1, subcode=0x10058c530)
* frame #0: 0x000000010058c530 libdispatch.dylib`_dispatch_sema4_timedwait.cold.3 + 36
frame #1: 0x0000000100555f84 libdispatch.dylib`_dispatch_sema4_timedwait + 128
frame #2: 0x0000000100556508 libdispatch.dylib`_dispatch_semaphore_wait_slow + 72
frame #3: 0x0000000196af2a0c MediaAccessibility`_copyResultPreferenceXPCCall(__CFString const*, bool, void const*, bool*) + 236
frame #4: 0x0000000196af1ea8 MediaAccessibility`MAPreferencesCopyProfileValue + 136
frame #5: 0x0000000196af20a0 MediaAccessibility`MAPreferencesCopyProfileValueWithExpectedType + 28
frame #6: 0x0000000196aefcc8 MediaAccessibility`MACaptionAppearancePrefCopyPreferredLanguages + 40
frame #7: 0x0000000196aeb990 MediaAccessibility`MACaptionAppearanceCopySelectedLanguages + 32
frame #8: 0x000000018af971c0 WebCore`WebCore::CaptionUserPreferencesMediaAF::platformPreferredLanguages() + 40
frame #9: 0x000000018921c244 WebKit`invocation function for block in WebKit::WebProcessPool::setMediaAccessibilityPreferences(WebKit::WebProcessProxy&) + 36
frame #10: 0x0000000100554028 libdispatch.dylib`_dispatch_call_block_and_release + 24
frame #11: 0x0000000100555828 libdispatch.dylib`_dispatch_client_callout + 16
frame #12: 0x0000000100558118 libdispatch.dylib`_dispatch_queue_override_invoke + 960
frame #13: 0x0000000100567d24 libdispatch.dylib`_dispatch_root_queue_drain + 432
frame #14: 0x0000000100568814 libdispatch.dylib`_dispatch_worker_thread2 + 188
frame #15: 0x00000001c80effec libsystem_pthread.dylib`_pthread_wqthread + 212
Rodrigo G
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
From
San Francisco, CA, United States
Post
Replies
Boosts
Views
Activity
I'm building something that includes functionality that allows a user to import a HealthKit workout and any associated heart rate samples. I've noticed that workouts that happened in the last 60 days or so (I don't know if it's a hard date cutoff) have what appears to be a full stream of heart rate samples. After that, the resolution of the heart rate sample data drops significantly. We go from having somewhere around ~500 heart rate samples to about 10 for an hour-long workout. I've confirmed with several other people that this is also happening to their data by asking them to go into their Health app to look at the heart rate samples for workouts that occurred a few months ago.
This issue is verifiable without writing any code, so I feel comfortable that the problem isn't with how I've implemented HealthKit queries in my code.
Is this expected behavior from HealthKit?