Posts

Post not yet marked as solved
18 Replies
Bumping this thread. It would be appreciated if Apple could provide a rough deadline. Is this days, weeks, months, a year? This would help us to prioritize the work of removing the UIWebView dependency, which is part of a 3rd party library that we use.
Post not yet marked as solved
8 Replies
At the minimum, it would be appreciated if Apple could give a rough timeline. Is this days, weeks, months, a year? We're actively working on removing any UIWebView usage but understanding the urgency would help us better plan this work.
Post marked as solved
35 Replies
We are in a similar situation. Like the post above, the user may answer the call before the app is ready to receive the call.In addition, there may be cases where a VOIP notification is received and we do not want to trigger the incoming call UI. For example:A local settings (i.e., call block or app-level do-not-disturb) indicates that the user does not want to receive the call.Other situations where a VOIP notification might be sent to trigger a critical sync between devices.Our concern is that these use cases could result in the notificaton not getting reported to CallKit and potentially trigger a violation on iOS 13. What is the recommendation for these use cases?
Post marked as solved
2 Replies
This likely has been added because of the newly introduced UIKit for Mac 13.0+. My guess is that CXProvider.isSupported will be false on Mac but always true on iOS.