title: Firebase sendPasswordResetEmail doesn't seem to work correctly with firebase-auth:9.0.2
body: <p>I am moving an Android app to the new Firebase platform from the old one. I can't seem to get sendPasswordResetEmail to work as documented for email/password authentication if given an unknown email string.</p>
  
  <p>The documentation says:</p>
  
  <blockquote>
    <p>public Task sendPasswordResetEmail (String email)</p>
    
    <p>Triggers the Firebase Authentication backend to send a password-reset
    email to the given email address, which must correspond to an existing
    user of your app.</p>
    
    <p>Exceptions:</p>
    
    <p>FirebaseAuthInvalidUserException thrown if there is no user
    corresponding to the given email address Returns Task to track
    completion of the sending operation</p>
  </blockquote>
  
  <p>Here is my pw reset method:</p>
  
  <pre><code> // firebase password reset
  private void requestPwReset() {
      String email = mEmailView.getText().toString();
      Log.d(TAG, "sending pw reset request for: " + email);
      try {
          Task&lt;Void&gt; task = mAuth.sendPasswordResetEmail(email);
          Log.d("TAG", "result: " + (task.isSuccessful() == true) ); // NEVER SUCCEEDS, EVEN WITH VALID EMAIL ADDRESS
      } catch(FirebaseAuthInvalidUserException e) {  //COMPILE ERROR HERE!
          Log.d(TAG, "exception: " + e.toString());
      }
  }
  </code></pre>
  
  <p>Calling this method causes this compile time error (which the IDE also flags):</p>
  
  <blockquote>
    <p>LoginActivity.java:117: error: exception
    FirebaseAuthInvalidUserException is never thrown in body of
    corresponding try statement
            } catch(FirebaseAuthInvalidUserException e) {</p>
  </blockquote>
  
  <p>If I omit the try-catch code then the method compiles, but  the returned task never succeeds, even with known good email addresses.</p>
  
  <p>The good news is that Firebase does eventually send a reset to good addresses, but I'm wondering why the sendPasswordResetEmail doesn't throw the documented exception if given an unknown user email or a successful Task when given a valid email.</p>
  
  <p>I did see in the May 18 release notes that there is an iOS issue with this function.</p>