Search Issue Tracker

Fixed in 2020.1.X

Fixed in 2017.4.X, 2018.4.X, 2019.2.X, 2019.3.X

Votes

108

Found in

2017.4.0f1

2018.4.0f1

2018.4.2f1

2019.2.0a1

2019.3.0a1

2020.1.0a1

Issue ID

1180664

Regression

No

[iOS] Apple throws Deprecated API Usage warning for using UIWebView when submitting Builds to the App Store Connect

iOS

-

After submitting Unity-iOS builds to the App Store Connect Apple is showing Warning for using UIWebView:

==
Dear Developer,
We identified one or more issues with a recent delivery for your app, "XXXXX". Your delivery was successful, but you may wish to correct the following issues in your next delivery:
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.
After you’ve corrected the issues, you can use Xcode or Application Loader to upload a new binary to App Store Connect.
==

This case doesn't need a reproduction project, the problem is that we're creating an instance of UIWebView at PlatformDependent/iPhonePlayer/URLUtility.mm to handle in-game links, but the UIWebView will be no longer supported by Apple and will be a cause for apps rejection in the App Store Connect

Reproduced on Unity 2017.4.32f1, 2018.4.8f1, 2019.2.4f1, 2019.3.0b2 and 2020.1.0a2

  1. Resolution Note (fix version 2020.1):

    Please note that you will get the error if you are using a Unity Ads package older or equal to 3.2. This was fixed with Ads 3.3.0.

Log in to vote on this issue

Comments (91)

  1. unity_2iM-Z6ouvzLZoQ

    Oct 06, 2019 10:35

    Unity 2018.4.10f1, this problem is still remain.

    What I did,
    Deleted obj, Temp,Library directories.
    Deleted Xcode project.
    Used ads plugin, not from asset store but built-in.

    Assets in my project,
    TextMesh Pro
    Easy Save 3
    DOTween Pro
    In App Purchasing

    Services used,
    Ads
    Analytics
    In-App Purchasing

  2. slUnity

    Oct 04, 2019 09:23

    Still exist in 2019.3.0b1

  3. Nenet

    Oct 04, 2019 01:21

    Please give the fix version of 2017.4. I have to take responsibility for not being able to publish products.

  4. Molioo

    Oct 01, 2019 08:24

    +1 for 2019.1 fix. It would be great.

  5. GameBearTech

    Sep 29, 2019 01:51

    2017.4 please, our game will be released soon!

  6. xpol

    Sep 28, 2019 00:16

    Why no fix for 2019.1 ?!

  7. Masaori-Hirono

    Sep 27, 2019 08:00

    So, which version should I use? (I use currently 2019.2.x)

    I think any tickets should be resolved after the fix was released.

  8. Dalton-Lima

    Sep 27, 2019 07:05

    I mean it "...it should be delivered in 2018.4.10f1"

  9. Dalton-Lima

    Sep 27, 2019 07:03

    This was being tested during 2018.4.9f1 (LTS), so normally it should be delivered in 2019.4.10f1 (which is not launched yet, according to Unity Hub).

  10. dhanrajsinh24

    Sep 26, 2019 15:37

    yes it's still present in 2019.2.6f1. do something plz.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues