We have an messaging application. In which we have a feature where it detect phone number and on tap of it we provide other options to user. Until release of iOS 16.1 version, it was working perfectly fine. But, After realise of iOS 16.1 and above we are experiencing a strange issue where it is not detecting the tap and not showing other options.  After debugging the code, we found that we are using below UIKit function to get the range or number on tap. But, In iOS 16.1 version it is returning null value. whereas, it was returning the range of number where it was tapped.  Below is the function which is returning nil value, Also attaching screenshot of code for better understanding.   **  textRange = [tokenizer rangeEnclosingPosition:tapPosition                           withGranularity:UITextGranularityWord                             inDirection:UITextLayoutDirectionRight];** The built-in UITextView tokenizer function rangeEnclosingPosition(_:with:inDirection:) seems to have broken in iOS 16.1 for the “word” granularity. Word: doesn't seem to ever return a range. We also tried this in a sample project. But, these issue is same on that project to. Please fix this issue on upcoming release. As, this being one of the crucial part of our health messaging app.  If possible, Please provide us a work around for this.

We have an App in App Store which is facing a different kind of scenario where users are missing out notifications after iOS updates.  We have already covered the scenario, Where we are registering app on every launch using .registerForRemoteNotifications() inside didFinishLaunchingWithOptions. And in case of a notification address change, we are forwarding the new notification address to our provider server. But, We come up with a scenario where the user updates his OS on his iPhone and doesn’t open his app. Also, The device token gets invalidated or expired after the update. So the User stops getting notifications. The only work he can do is to launch the app to register for remote notification and get a new device token after the iOS update.  So, We would like to know any best practices available or workaround available that can fix our problem until the user open ups the app to get the updated device token after the iOS Update.  Also, Is there any way from the server side by which our server can communicate with the APNS server and can identify that the APNs token has expired or any other issue is there with this Device token? So that we can let users know to open the app. As, This is a healthcare app and it is a very critical issue for us to miss out notifications. And due to this issue, a lot of users are getting impacted.