java.lang.NoClassDefFoundError: Failed resolution of: Lcom/google/firebase/auth/internal/InternalAuthProvider; #2122
Comments
|
I have same issue on android. |
|
I have same issue on android. Please check this link. |
|
with com.google.firebase:firebase-auth:17.0.0 runs without crashes |
|
@igor-slotin |
|
current react-native-firbase version is 4.3.7 |
|
Looks like this is the latest Android SDK release causing this - I'm not sure why the latest release is causing issues when the versions are locked in your dependencies to versions that were working prior to yesterdays release =/ If @igor-slotin solution works then that's the way to go, update to latest Auth SDK: Alternatively, it may just be that only core is required to be updated here instead of auth, could someone try that and confirm here please, update core from 16.0.8 to 16.0.9: |
|
I've also update @Salakar you suggestion make sense, i can try update just only it in 10 minutes |
|
I got this same crash on Monday night UK time, 6th May 2019. Was doing debug builds (just superficial tweaks to our codebase), running them on Android emulator, all was fine, then suddenly this error and no builds working since. Another coder on our team just got it this morning. Might be relevant: To overcome a previous gradle bomb we have this in our app gradle... |
|
Nope, updating just core doesn't work for me, the same crash |
|
UPDATE: I got it working by updating What i would love to know is: How did this bug happen without me doing anything apart from running |
|
I also am facing same issue. Has anyone resolved yet? I have not installed any new packages but still my app crashes with same error |
An Android Firebase SDK release must have caused this, very weird though given that all of us, myself included have specified the exact versions - but according to the Firebase Android SDK release notes for yesterday there was a breaking Auth change:
Must have been backported or something, really don't know 🤷♂ |
|
@ericm999 It seems that an android SDK update has broken the existing packages. However, updating |
Thank you all, upgrading firebase-auth to 17.0.0 fixed the issue. |
Thanks man you saved my day !!! |
|
A heads up as well if you're using storage: if you're getting unknown http failure errors, check the logs, if you see the following then you'll need to update to the latest Android SDK version for that as well 😫
It may be the case on other modules, the safest option is to update all of them. There are no breaking changes as far as I can see that will affect RNFB v5 (have tested on RNFB v6 - which had same versions as RNFB v5)
|
Salakar
added
impact: build-error
[android] update to latest firebase sdks - previous release broken (#2122) [skip ci]
|
I am using current everything on the android side (current gradle, current gradle plugin, current sdk, build tools, firebase deps etc etc) with react-native-firebase 5.3.1 and it's fine for all the modules I'm using - I am not using storage, remote config, or dynamic links yet though |
|
@mikehardy not sure why it works for you :D Happened to me today on v6 without upgrading anything, just did a fresh android build and it went spoopy 💩 |
|
Well, I have something to look forward to on my next build then I suppose - the joy of dynamic dependency resolution. |
|
Anyone who gets module specific errors like Auth,Database, etc. Try updating those to 17.0.0. As firebase updated to these SDK version. Somehow the older SDKs version broke and couldn't simply work anymore !! |
|
+1 for workaround, glad I found this solution! |
|
So reassuring to know that even behemoths like Google fuck things up on a regular basis. |
|
I don't understand why Google is shattering jobs in his updates. FirebaseInstanceId was removed and I included it in my project but still couldn't remove my head from problems. Very painful |
It's Working |
* v5.x.x: 5.4.0 [tests] disable admob (has a new runtime check that causes a crash as we don't have a valid admob identifier) [android] update firebase sdk versions - forced to upgrade due to invertase#2122 [android][internals] rework internals utils to better support JSONObject/Array values [GENERAL][BUGFIX][build] - patch v5 build toolchains for XCode10.2 & RN0.59 compatibility (invertase#2166) [tests] update podfile lock [tests] sync v5.x.x local changes [tests] sync v5.x.x local changes [docs] update link [STORAGE][BUGFIX][ANDROID] - Preserve `file://` prefix [JS][BUGFIX] [package.json] - Fix build on Windows (BABEL_ENV error) [Messaging] Add null check to acquire WakeLock on Android (invertase#2092) [TYPES][BUGFIX][AUTHENTICATION] - Change type PhoneAuthSnapshot.Error to NativeError
|
Closing this, we've got versions in our compatibility table, we did a fair bit of work recently on v5 build + CI and even did a v5 release, and I'm using it all in a real app - there was definitely a hiccup, but with current versions things are working |
|
Downgrading |
|
@neri4488 - yes that is one way, just replying for future viewers, because you may be able to use the versions over 16 (that is, the AndroidX ones) if you also convert your app to AndroidX and use https://github.com/mikehardy/jetifier - but all these things (the AndroidX transition steps) have to happen together - all one way or all the other |
|
https://dev.to/rosariopfernandes/exploring-firebase-bill-of-materials-bom-1hij I fixed this issue with adding https://firebase.google.com/support/release-notes/android#2019-04-02 |
|
Having tested the "bom" style myself, it what I recommend going forward, we just haven't updated the docs or anything. It is a very nice way to manage all the dependencies. That said, @richardradics why not bom 22.1.0? I don't understand why people don't stay current... 🤷♂️ |
|
@mikehardy I've just tried to be as close with the versions as in the library's integration documentation. In the |
|
I updated the docs recently so they indicate ranges, including the current ones - the whole point of the v5.5.x release line where I made breaking changes was to support keeping the underlying firebase SDKs current. You can assume that until the SDKs themselves make another breaking changes you can just stay updated https://rnfirebase.io/docs/v5.x.x/getting-started#Supported-versions---React-Native-/-Firebase ...and when they do, I'll release v5.6.x with the necessary changes to make those compatible |
|
Which I guess answers my implied question anyway: I think our documents might be a bit unclear there. if you can think of a more clear wording for that link that makes it clear we track the current underlying SDKs so you can stay current, I'm open to anything as a PR there |
|
I had the same issue on android. |
|
Same issue. |
|
@amixel this issue is closed, which implies if you have the same issue it should be solved with the above information If you have an open issue on current stable versions, please open a new issue including the necessary information in the template. Prior to doing so I encourage you to examine what a clean example looks like to make sure you've done all necessary steps: https://github.com/mikehardy/rnfbdemo/blob/master/make-demo.sh |
but I don't see the solution that good. the Firebase community is also experiencing the same problem. |
|
Worked for me thanks |
Recently added a few google packages such as Crashlytics and updated google-services for Google-Signin on firebase. Since then, Android build is successful through both Android Studio build and
react-native run-android. Before these changes app launched without any issue,App is uploaded to emulator successfully however, app won't launch
The only error log I get is from logcat which seems to be related to firebase auth
Project Files
Android
android/build.gradle:buildscript { ext { buildToolsVersion = "28.0.3" minSdkVersion = 16 compileSdkVersion = 28 targetSdkVersion = 28 supportLibVersion = "28.0.0" googlePlayServicesAuthVersion = "16.0.1" // for social signin with firebase } repositories { google() jcenter() maven { url 'https://maven.fabric.io/public' } } dependencies { classpath 'com.android.tools.build:gradle:3.3.1' // 3.2.1 3.1.4 classpath 'com.google.gms:google-services:4.2.0' classpath 'io.fabric.tools:gradle:1.+' } } allprojects { repositories { maven { url "https://jitpack.io" } mavenLocal() google() jcenter() maven { // All of React Native (JS, Obj-C sources, Android binaries) is installed from npm url "$rootDir/../node_modules/react-native/android" } maven { url "https://maven.google.com" } } } task wrapper(type: Wrapper) { gradleVersion = '4.4' distributionUrl = distributionUrl.replace("bin", "all") } subprojects { project.configurations.all { resolutionStrategy.eachDependency { details -> if (details.requested.group == 'com.android.support' && !details.requested.name.contains('multidex') ) { details.useVersion "26.1.0" } } } }android/app/build.gradle:android/settings.gradle:MainApplication.java:AndroidManifest.xml:Environment
react-native infooutput:Platform that you're experiencing the issue on:
Are you using
TypeScript?NThe text was updated successfully, but these errors were encountered: