How can I handle this warning?(com.google.android.gms:play-services-safetynet:17.0.0)

3HJack commented 2 years ago

[READ] Step 1: Are you in the right place?

[REQUIRED] Step 2: Describe your environment

Android Studio version: 2021.2.1 Patch 1
Firebase Component:
implementation platform("com.google.firebase:firebase-bom:29.0.1")
implementation 'com.google.firebase:firebase-analytics'
implementation 'com.google.firebase:firebase-auth'
implementation 'com.google.firebase:firebase-auth-ktx'
implementation 'com.google.firebase:firebase-messaging'
implementation 'com.google.firebase:firebase-dynamic-links'
implementation 'com.google.firebase:firebase-perf'
implementation 'com.google.firebase:firebase-crashlytics-ndk'
Component version: _____

[REQUIRED] Step 3: Describe the problem

Steps to reproduce:

What happened? How can we make the problem occur? This could be a description, log/console output, etc.

Relevant Code:

google-oss-bot commented 2 years ago

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

chalermpong commented 2 years ago

I also got this warning. I'm using Firebase-Auth 21.0.6.

Here is the warning message from Google Play Console.

Warning

The developer of play-services-safetynet (com.google.android.gms:play-services-safetynet) has reported critical issues with version 17.0.0. Consider upgrading before publishing a new release.

Here's what the SDK developer told us: The SafetyNet Attestation API is being discontinued and replaced by the new Play Integrity API. Begin migration as soon as possible to avoid user disruption. The Play Integrity API includes all the integrity signals that SafetyNet Attestation offers and more, like Google Play licensing and better error messaging. Learn more and start migrating at Discontinuing the SafetyNet Attestation API | Android Developers

Learn More

argzdev commented 2 years ago

Hi @3HJack, thanks for reporting. I'll let our engineers know about this.

lisajian commented 2 years ago

Hi, thanks for filing this issue! We are unable to promise any timeline for this, but if others also have this issue, adding a +1 on this issue can help us prioritize adding this to the roadmap.

(Googler-only internal tracking bug: b/238777072)

bocops commented 2 years ago

Hi, thanks for filing this issue! We are unable to promise any timeline for this, but if others also have this issue, adding a +1 on this issue can help us prioritize adding this to the roadmap.

(Googler-only internal tracking bug: b/238777072)

+1

dpedrinha commented 2 years ago

Hi, thanks for filing this issue! We are unable to promise any timeline for this, but if others also have this issue, adding a +1 on this issue can help us prioritize adding this to the roadmap. (Googler-only internal tracking bug: b/238777072)

+1

Well, it's not like this is a feature request. SafetyNet IS being discontinued so the plugin is going to eventually break.

The due time is June 2023 though. There's time. But it definitely needs to go into the roadmap eventually.

yisusparkr commented 2 years ago

Hi, thanks for filing this issue! We are unable to promise any timeline for this, but if others also have this issue, adding a +1 on this issue can help us prioritize adding this to the roadmap.

(Googler-only internal tracking bug: b/238777072)

+1

jianyongyang commented 2 years ago

Hi, thanks for filing this issue! We are unable to promise any timeline for this, but if others also have this issue, adding a +1 on this issue can help us prioritize adding this to the roadmap.

(Googler-only internal tracking bug: b/238777072)

+1

foxcode7 commented 2 years ago

Hi, thanks for filing this issue! We are unable to promise any timeline for this, but if others also have this issue, adding a +1 on this issue can help us prioritize adding this to the roadmap.

(Googler-only internal tracking bug: b/238777072)

+1

zhangqiankun6 commented 2 years ago

Hi, thanks for filing this issue! We are unable to promise any timeline for this, but if others also have this issue, adding a +1 on this issue can help us prioritize adding this to the roadmap.

(Googler-only internal tracking bug: b/238777072)

+1

StigUK commented 2 years ago

Hi, thanks for filing this issue! We are unable to promise any timeline for this, but if others also have this issue, adding a +1 on this issue can help us prioritize adding this to the roadmap.

(Googler-only internal tracking bug: b/238777072)

+1

DennisKragekjaer commented 2 years ago

I also got this warning for my flutter app. But will the app be released with this warning?
Review is taking really long time.

simhi88 commented 2 years ago

b/238777072

+1

JoniGoos commented 2 years ago

Hi, thanks for filing this issue! We are unable to promise any timeline for this, but if others also have this issue, adding a +1 on this issue can help us prioritize adding this to the roadmap.

(Googler-only internal tracking bug: b/238777072)

+1

moyosolaa commented 2 years ago

+1

abdulkadir-ali commented 2 years ago

+1

Jeoxs commented 2 years ago

I also got this warning for my flutter app. But will the app be released with this warning? Review is taking really long time.

Hello! Yes, the app will be released regardless of the warning on the Play Console. I know the team is working on this ASAP and will give us any feedback soon. So, even if they cannot share any timeline, we have the Android's Developers page deadline for this:

June 2023: Migration deadline. The app will continue to work but there might be issues and deprecation warnings.
June 2024: Apps with SafetyNet will stop working.

Additionally, when the developers says to add a +1, I believe they're talking about adding the Emoji +1 as reaction to the main issue and not just commenting "+1".

Hope to get any news soon. Cheers! 👍

957211324 commented 2 years ago

+1

mcoskunnn commented 2 years ago

+1

rex26 commented 2 years ago

+1

hunghuuk commented 2 years ago

Still open, looking for closed this issue so we can upgrade the version to meet Google's policy

nsdhmonte commented 2 years ago

+1

TonyAnine commented 2 years ago

+1

alihassan143 commented 2 years ago

+1

ShawnLin013 commented 2 years ago

+1

carlplaylab commented 2 years ago

+1 Weird that firebase and Google android guys aren't communicating.

IsaiasCuvula commented 2 years ago

This is the most strange thing, Firebase team don’t talk with with Google Play team , and we suffer the consequences

On Tue, 16 Aug 2022 at 13:26, Carl Joven @.***> wrote:

+1 Weird that firebase and Google android guys aren't communicating.

— Reply to this email directly, view it on GitHub https://github.com/firebase/firebase-android-sdk/issues/3890#issuecomment-1216451803, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQJDWZEYXKA6SYVMUOOD3ZLVZNUEHANCNFSM53JRSJKA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

dpedrinha commented 2 years ago

This is the most strange thing, Firebase team don’t talk with with Google Play team , and we suffer the consequences … On Tue, 16 Aug 2022 at 13:26, Carl Joven @.> wrote: +1 Weird that firebase and Google android guys aren't communicating. — Reply to this email directly, view it on GitHub <#3890 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQJDWZEYXKA6SYVMUOOD3ZLVZNUEHANCNFSM53JRSJKA . You are receiving this because you are subscribed to this thread.Message ID: @.>

Flutter, Firebase, Google Play, Android OS, Google AdMob, Android Studio are all products from the same company and this kind of problem happens with all of them. It's like they don't have a test team.

WhitePhoenixv5870 commented 2 years ago

您好，感谢您提交此问题！我们无法为此承诺任何时间表，但如果其他人也有此问题，在此问题上添加 +1 可以帮助我们优先将此添加到路线图中。

（仅限 Google 员工的内部跟踪错误：b/238777072）

+1

sunday58 commented 2 years ago

👍+1

swdelvalle-na commented 2 years ago

+1

dzeniska commented 2 years ago

+1

tigrettin commented 2 years ago

+1

kevinguitar commented 2 years ago

+1

innomatica commented 2 years ago

+1

smartmerlin commented 2 years ago

+1

rojepp commented 2 years ago

I wish you would please stop commenting "+1". You do know that you are notify-spamming a bunch of people when you do this? Leave a thumbs-up in the original post or something.

Ghazanfarrajpoot commented 2 years ago

any fix?? and wrokaround???

Syn-McJ commented 2 years ago

+1

ahzmie commented 2 years ago

+1

rustam-baktybek commented 2 years ago

+1

rustam-baktybek commented 2 years ago

+1

lienict commented 2 years ago

+1

alihassan143 commented 2 years ago

why is firebase not serious about this issue @argzdev kindly tell us did firebase have any plans for resolving this issue??

argzdev commented 2 years ago

Hi @alihassan143 and all. Sorry for the delayed response, I apologize that we’re unable to migrate the library faster. Yes, this is under our radar and is being worked on by our engineers.

Just to give some insights, our engineers have other priorities right now. That being said, here’s what I can do. Since this issue gets a lot of attention, I’ll try to keep bringing this up to our engineers and nudge them to see if it’s possible to move this up from their timeline and add more priority on this issue.