-
Notifications
You must be signed in to change notification settings - Fork 262
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Apple started rejecting OneSignal SDK because of UIWebView API #522
Comments
Same here ITMS-90809: Deprecated API Usage - Apple will stop accepting submissions of apps that use UIWebView APIs . See https://developer.apple.com/documentation/uikit/uiwebview for more information |
@arthurdapaz @inkly Thanks for reporting, a fix has been merge in and will be included in the next release |
@jkasten2 do you have any infos when the next release will be available ? |
- Removes deprecated UIWebView usage from original SDK (OneSignal/OneSignal-iOS-SDK#522) - Fixes a problem while building it with Xcode 11 (williamrijksen#85) - Removes deprecated API call to IdsAvailable - Adds CoreGraphics and WebKit must haves frameworks - Updates to Titanium 8.x SDK - Uses TitaniumKit framework and sets CLANG_ENABLE_MODULES to true on project configuration
Hi, I'm facing the same problem. How can I fix it? |
This fix was included in OneSignal-iOS-SDK 2.10.2 released Sep. 3 2019. |
Description:
Apple will start rejecting apps that directly or indirectly calls for UIWebView API. (OneSignal framework, GoogleSignIn SDK, for example are both being warned by Apple automatic review process)
UIWebView is deprecated since iOS 12*. So, for best practice we should replace it for WKWebView
Environment
Swift 5 (target: iOS 10.0), latest OneSignal framework
Steps to Reproduce Issue:
Anything else:
Didn't find any branch dealing with this issue. Suggestion is to use WKWebView which is modern and encouraged by Apple
The text was updated successfully, but these errors were encountered: