IMO this definitely should be marked @MainActor (reported as FB14256770) but thanks for the workaround!
frankus
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
At first glance this looks like a straightforward out-of-memory situation.
EXC_BREAKPOINT points to a Swift runtime error, and 16 lines into the swift_slowAlloc method it calls a crash method if malloc (or one of its variants) returns a non-truthy value. (https://github.com/apple/swift/blob/aaff37ffb872117cc2697920f85d8743b26a06cc/stdlib/public/runtime/Heap.cpp#L102)
The canonical use case for this control in our application is an NPS score, which goes from 0 to 10.
We've added an accessibility hint that says "Where 0 is not at all likely and 10 is extremely likely". So the user is given context (assuming they haven't disabled accessibility hints).
In the medium term we plan to make this a custom control, so thank you for the tip about accessibilityRowRange!