Failed resolution of : lcom/google/android/gms/safetynet/safetynet;

Discuss
, , ,
#42

Have you removed Firebase Auth component?

#43

Could you please post the correct model steps blocks for the aulth firebase, from FSA?

#44

The only different thing is initialisation.
For that you will find all the required credentials in google-services.json file.

#45

After adding the FSA extension, my app started to close by itself simply because I went to another screen, and I spent days analyzing why it was returning a class error of some incompatibility with GoogleMaps that was on another screen, but only if I was with "Call Google Maps .Enable My Location Enable, in Map is Ready, which I need to leave activated, then I have to choose, either I use the FSA Login or the My Location Method. Both together in the App are not possible!
blocks google

#46

It is possible.
Pm me apk with Google maps.

#47

I Used FSA extension but app automatically closed on open

#48

Ok, that’s amazing to know.
I am sure I can’t help without knowing what other components you are using.
FSA isn’t made for Kodular so there might be several components which don’t work well with it.
Google Maps is one of them.

#49

I am having this error while login How can I fix it :face_holding_back_tears: :face_holding_back_tears:, plz help me

Screenshot_٢٠٢٣١١١٨-١٤٢٧٣٩
Screenshot_٢٠٢٣١١١٨-١٤٢٧٣٩720×1600 54.7 KB

Try to let the user sign in with a Phone Number
kodular
Firebase Authentication

1 Like
#50

Hello, I searched a lot in the community and did not find a solution. I previously had a problem with logging in and confirming the OTP. It had been working for a while. It became a very big problem, which is that the OTP code does not reach the user, and this image appears. I want a solution from Community Kodular.

IMG_20231224_174258_480
IMG_20231224_174258_4801080×514 25.6 KB

#51

I moved your question into the correct thread
Just read the already given answers here, for example Failed resolution of : lcom/google/android/gms/safetynet/safetynet; - #25 by vknow360

Taifun

#52

This happened after the Kodular API 33 update, and there is no solution, I really had a lot of problems because of that too, I had to change everything, think about the problem, Kodular is very complicated, you fix it there and they ruin it there,

#53

There is no solution here, I hope you can solve this problem now

#54

Is there any solution that you have done?

1 Like
#55

I removed it from Firebase and left it with the Google account, you have to use other login methods

1 Like
#56

Until when will we remove the OTP feature, it is definitely important in any application

2 Likes
#57

Is there any solution that
:rage: :rage: :rage:

#58

Same Error in app please help me, hoe to solve it without using any extension provided above

#59

Does anybody have any solution to it? I am not able to publish this app because of this reason only please help me to resolve this safety issue

#60

On immediate purpose… if otp is essential then don’t use firebase for play store it will provide lamda error and app will reject… use another database and for otp use fast2Sms it provides… 4000 OTP in 1000 INR

#61

There is no solution

:rage: :rage: :rage:

1 Like