This happens when you lock features behind a paywall the user wants access to. They pay, they get use of the feature, and then request a refund. If this happens in high volumes where the refunds exceed the total revenue, the above situation will arise, which means you have a wrong business model. Apple should provide an option where the developer can top up their app's sales balance, just like an overdrawn bank, to release it from the hold they place on the account or provide developers with an option not to offer refunds.

Just branch and prepare your code base for Swift 6 instead of setting up the project for obsolescence.

I originally reported this issue 12/17/2024 under FB16112960. The status says a potential fix has been identified.

The issue was resolved but the conversation was here https://stackoverflow.com/questions/21774899/voice-over-doesnt-read-phone-number-properly if there is no link after posting this then it was removed.

Fast forward, when you mix c++ with swift on the c++ side there’s no precision issue.