[Solved] Android auth firebase error: Local module descriptor class for not found

  • I’m trying to build an app with login/register capabilities through Firebase. I’m working on it with a partner (he’s on Linux, I’m on Mac), and he’s able to get the authentication working but for some reason I am not. We have all the same code, SDK tools checked in the SDK manager, running the same version of everything.
  • Here’s the gradle file:

    compile ''
    compile ''
    compile ''
    compile ''
    testCompile 'junit:junit:4.12' 
  • And the code:

    public class RegisterActivity extends AppCompatActivity {
    private FirebaseAuth mAuth;
    private FirebaseAuth.AuthStateListener mAuthListener;

    private EditText mUsernameField;
    private EditText mPasswordField;
    private EditText mConfirmPasswordField;

    private Button mRegisterButton;

    protected void onCreate(Bundle savedInstanceState) {
        Toolbar toolbar = (Toolbar) findViewById(;

        mUsernameField = (EditText) findViewById(;
        mPasswordField = (EditText) findViewById(;
        mConfirmPasswordField = (EditText) findViewById(;
        mRegisterButton = (Button) findViewById(;

        mRegisterButton.setOnClickListener(new View.OnClickListener() {
            public void onClick(View v) {
                createAccount(mUsernameField.getText().toString(), mPasswordField.getText().toString());
        mAuth = FirebaseAuth.getInstance();

        mAuthListener = new FirebaseAuth.AuthStateListener() {
            public void onAuthStateChanged(@NonNull FirebaseAuth firebaseAuth) {
                FirebaseUser user = firebaseAuth.getCurrentUser();
                if (user != null) {
                    // User is signed in
                    Log.d("account", "onAuthStateChanged:signed_in:" + user.getUid());
                } else {
                    // User is signed out
                    Log.d("account", "onAuthStateChanged:signed_out");
                // ...

    public void onStart() {

    public void onStop() {
        if (mAuthListener != null) {

    private void createAccount(String email, String password) {
        Log.d("account", "createAccount:" + email);
        if (!validateForm()) {

        // [START create_user_with_email]
        mAuth.createUserWithEmailAndPassword(email, password)
                .addOnCompleteListener(this, new OnCompleteListener() {
                    public void onComplete(@NonNull Task task) {
                        Log.d("account", "createUserWithEmail:onComplete:" + task.isSuccessful());

                        // If sign in fails, display a message to the user. If sign in succeeds
                        // the auth state listener will be notified and logic to handle the
                        // signed in user can be handled in the listener.
                        if (!task.isSuccessful()) {
                            Toast.makeText(RegisterActivity.this, R.string.register_failed,

                        else {
                            Intent intent = new Intent(RegisterActivity.this, MainActivity.class);
        // [END create_user_with_email]

    private boolean validateForm() {
        boolean valid = true;

        String email = mUsernameField.getText().toString();
        if (TextUtils.isEmpty(email)) {
            valid = false;
        } else {

        String password = mPasswordField.getText().toString();
        if (TextUtils.isEmpty(password)) {
            valid = false;
        } else {

        String confirmPassword = mConfirmPasswordField.getText().toString();
        if (TextUtils.isEmpty(confirmPassword)) {
            valid = false;
        } else {

        if(!confirmPassword.equals(password)) {
            mConfirmPasswordField.setError("Passwords must be the same.");
            valid = false;

        return valid;


  • And finally the error:
W/DynamiteModule: Local module descriptor class for not found.
W/GooglePlayServicesUtil: Google Play Store is missing.
I/art: Background partial concurrent mark sweep GC freed 5866(313KB) AllocSpace objects, 1(14KB) LOS objects, 39% free, 2MB/4MB, paused 5.176ms total 27.761ms
D/account: createUserWithEmail:onComplete:false 

  • Pretty much everything was taken textbook from the Firebase website. Please help, we’ve been stuck on this for hours, and none of the other similar questions have helped.
Enquirer: John Doe


Solution #1:

Option 1: Go to Firebase Console < Authentication < SIGN-IN METHOD, and see if you are using it in the Anonymous state. If you are, disable that and enable Email/Password or whichever login method you are using.

Option 2: Check if the device you are testing with is running Google Play Services 9.0.0 or later.

Solution #2:

Add a log in onComplete() listener of createUserWithEmailAndPassword() to see what exactly is the reason behind the failure.

   if (!task.isSuccessful()) {
    Log.e(TAG, "onComplete: Failed=" + task.getException().getMessage()); 

This can be due to the password or email you entered to create an account.

  • if the email you entered is in proper format and does exist.
  • if password is strong enough to be accepted (usually not less than 6 letters).
  • if there is already an account with the same email.
Respondent: Niraj Niroula

Solution #3:

In my case, I was debugging the application and was missing the SHA1 Key in my firebase project configuration. If you are debugging make sure you have your SHA1 Key in place.

Respondent: Jawand Singh

Solution #4:

Can you check your Google Play Services version?

Prerequisites :

  • An Android device running Google Play services 9.0.0 or later
  • The Google Play services SDK from the Android SDK Manager
  • Android Studio 1.5 or higher
  • An Android Studio project and its package name.

One of the reason for this problem could be, your Sign In Method inside Firebase > Auth Dashboard might be disabled.


The 10.2.1 version wasn’t available for downloading from any (virtual)
device that you tested, required update.

The version of Google Play Services shown in the Extras section at the bottom of the Standalone SDK Manager has no effect on the version used by an emulator. The emulators run on system images configured to contain some particular version of Play Services, which is not always the same.

You should confirm that you have downloaded the latest emulator images having version compatibility like version 10.2.1(latest).

Respondent: Abhishek Aryan

Solution #5:

Same thing happened with me because I was using old auth version as you can see
the old one is mentioned and commented out and the new one is at the bottom inside dependencies.

enter image description here

So always try to follow dependencies that are mentioned here

The answers/resolutions are collected from stackoverflow, are licensed under cc by-sa 2.5 , cc by-sa 3.0 and cc by-sa 4.0 .

Most Popular

To Top
India and Pakistan’s steroid-soaked rhetoric over Kashmir will come back to haunt them both clenbuterol australia bossier man pleads guilty for leadership role in anabolic steriod distribution conspiracy