Skip to content
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

[ISSUE] Deprecated API Usage - Apple may deny builds #3780

Closed
filipealva opened this issue Sep 5, 2019 · 5 comments

Comments

@filipealva
Copy link

commented Sep 5, 2019

#3011 # [REQUIRED] Step 2: Describe your environment

  • Xcode version: 10.2.1
  • Firebase SDK version: 6.6.0
  • Firebase Component: Core
  • Component version: 6.6.0

[REQUIRED] Step 3: Describe the problem

Steps to reproduce:

What happened?

When I upload a build for TestFlight Apple advises me that I'm making use of a deprecated API and they still start rejecting builds like that. I investigated and it's Firebase iOS SDK making some calls to UIWebView.

What's the suggested solution? How can I be safe that my build will not be denied because of Firebase's SDK?

This could be a description, log/console output, etc.

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.
@ryanwilson

This comment has been minimized.

Copy link
Member

commented Sep 5, 2019

Thank you for the report - this is a duplicate of #3722 and is fixed by #3723. The release should be out today if all goes well.

@ryanwilson ryanwilson closed this Sep 5, 2019

@ryanwilson ryanwilson added this to the M55 milestone Sep 5, 2019

@paulb777

This comment has been minimized.

Copy link
Member

commented Sep 5, 2019

I'll reopen, since while the issue in this repo with DynamicLinks is being fixed in Firebase 6.8.0, the issue still remains in Crashlytics(b/140424496) and FirebaseML(b/140396933).

This was previously reported at firebase/quickstart-ios#788. I'll close that one and keep it open here.

@paulb777

This comment has been minimized.

Copy link
Member

commented Sep 6, 2019

b/140559063 is another related internal tracking bug

@samedson

This comment has been minimized.

Copy link

commented Sep 10, 2019

Just released Crashlytics 3.14.0 which should fix this issue

@morganchen12

This comment has been minimized.

Copy link
Collaborator

commented Sep 10, 2019

If anyone sees this issue after Crashlytics 3.14.0, please comment here and we'll re-open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
6 participants
You can’t perform that action at this time.