existing user modification time and new user signup timestamps are same

[j2emanue]

It seems the check to verify if the user is a new SignUp or existing user is not working.

I signed up a user brand new and then logged out of email provider.

I then logged in again (and got the welcome back screen) and signed in again.

I did this immediately with about 10 seconds delay between:

but the following code always returns true:

  public boolean isNewSignUp() {
       FirebaseUserMetadata metadata = mAuth.getCurrentUser().getMetadata();
       if (metadata.getCreationTimestamp() == metadata.getLastSignInTimestamp()) {
           Toast.makeText(getActivity(), "new user ACCOUNT CREATED", Toast.LENGTH_LONG).show();
       } else {
           // This is an existing user, show them a welcome back screen.

           Toast.makeText(getActivity(), "existing user account retrieved", Toast.LENGTH_LONG).show();
       }

       return metadata.getCreationTimestamp() == metadata.getLastSignInTimestamp();
   }

i am using fireBaseUI-Auth and this check happens in onActivityResult. What am i missing ?

[SUPERCILEX]

What version of FUI and play services are you using?

[j2emanue]

firebase_version = '12.0.1' classpath 'com.google.gms:google-services:3.2.0' com.google.android.gms:play-services-auth:12.0.1 firebaseUI = 3.2.2 do you have another way i can get if its a new user sign up ?

…

________________________________ From: Alex Saveau <notifications@github.com> Sent: Sunday, March 25, 2018 12:36 PM To: firebase/FirebaseUI-Android Cc: j2emanue; Author Subject: Re: [firebase/FirebaseUI-Android] existing user modification time and new user signup timestamps are same (#1209) What version of FUI and play services are you using? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#1209 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AEuvOgKiy1G-9udo_5gwBLTNPyJLsUOcks5th8eqgaJpZM4S6GX1>.

[huberrom]

Got the same problem

[j2emanue]

im on the latest android and google play services now. tried it again and same issue. its kind of important issue as when we know its a new user account we'd like to show a screen such as select your country or select your preference for the application before proceeding. @huberrom have you thought of any temporary solution

[samtstern]

I just tried this with the demo app in this repository and I cannot reproduce. I signed in with an existing email user and got:

created:1518803610000
   last:1522860101000

[j2emanue]

samtstern, do it this way instead. create a new account and immediately sign out and log in again with the same account. on api 26 emulator is what i was using with google play services 12.0.1 but even previous version it occurs.

[samtstern]

@j2emanue thanks! That reproduced it for me:

created:1522861280000
   last:1522861280000

This is almost definitely a bug in the Firebase Auth SDK, I will file it with them. Could you see if calling reload() helps you?:
https://firebase.google.com/docs/reference/android/com/google/firebase/auth/FirebaseUser.html#reload()

[samtstern]

@j2emanue ok I just talked to the team and they said:

The granularity accuracy that Firebear server guarantees for the last_login timestamp is 1 minute. The reason is to avoid too frequent write operation to [the backend].

The real source of true here is the isNewUser() method on the AdditionalUserInfo returned in the AuthResult, but off the top of my head I don't think we provide any way for you to get to that from FirebaseUI.

[samtstern]

Going to close this and file a new feature request to expose that information,

[j2emanue]

@samtstern it happens in other scenarios. i had an account that has existed for a few days and when i log in it says its a new account. i then go on firebase console and check the creation time and its from a few days ago. so its happening in other scenarios. @SUPERCILEX is there anyway you can put a boolean in the intent when onActivityResult is called so that we can know if its a new user, as a temporary fix ?