Hello,
We develop an accessibility app that provides real-time captions for phone calls. Our app allows users to enable or disable call forwarding using carrier codes (e.g., **21<phone number>#), allowing them to receive captioned inbound calls.
With the iOS 27 rollout, the new "Trust Insights" feature began blocking these codes with a "Malicious Link Blocked" warning. In iOS 27.2 Beta, the warning changed to "Call Forwarding Link Blocked," directing users to manage call forwarding through Apple's native settings. However, we've observed inconsistent behavior across carriers:
- Tello eSIM: Call forwarding codes are blocked even when manually entered into the native iPhone dialer.
- T-Mobile: Manually entering the same type of code into the native dialer still works, although dialing through our app is blocked.
This inconsistency makes it difficult to provide our users with reliable setup instructions. More importantly, blocking these codes introduces significant friction for users with disabilities who rely on our app for accessible phone calls.
Is there a process for accessibility apps to request an exemption from these restrictions, or an alternative to preserve call forwarding in our app?