I’m trying to use Firebase email and password authentication in Java using their REST API, as their Admin SDK doesn’t provide the needed methods to log in etc., only user management methods. With help from this answer, I’ve managed to put together the following code, which works for correct credentials but when trying to handle errors e.g. USER_NOT_FOUND or INVALID_PASSWORD,
Tag: firebase-authentication
The register button is giving me authentication failed, how can i fix it?
The register button is not functioning correctly, It gives me authentication failed toast. it seems like my strings for a create a user with email and password are correct but it still wont work. What can I do? please help if you can. Java File: XML File: the strings I filled in: [enter image description here][1] [1]: https://i.stack.imgur.com/2d29O.png Answer When
FirebaseAuth does not print realtime data in the membership creation step
I have created a membership system in my application. I create record with Firebase Auth and store some information in firebase realtime . However, I saw that 1% of the users did not print their data to firebase realtime during record creation. If users’ data is not written to firebase realtime, my application will crash. I haven’t been able to
Setting DisplayName on Register for Firebase
UserProfileChangeRequest(java.lang.String, java.lang.String, boolean, boolean)’ is not public in ‘com.google.firebase.auth.UserProfileChangeRequest’. Cannot be accessed from outside package and Register.java:85: error: constructor UserProfileChangeRequest in class UserProfileChangeRequest cannot be applied to given types; UserProfileChangeRequest profileUpdates = new UserProfileChangeRequest().Builder().setDisplayName(username).build(); ^ required: String,String,boolean,boolean found: no arguments reason: actual and formal argument lists differ in length I’m getting the above error from trying to set the display
Using Firebase open a different activity if user logged in second time
I am using Firebase in my project. What I want?? When a new user logged in, he goes through all activities (like Information activity, etc) after login and then to the dashboard. when that user logout from the app and logged in again then directly go to dashboard not need to fill that all information again. I am using this
How can I solve this new Firebase Auth error?
As normal I was working on my actual project and I wanted to add something new to an old activity. When I opened the .java file a new error has shown with a reason that I can not think about. It says that the FirebaseAuth symbol cannot be resolved. I checked my Gradle ( which is updated to the latest
Why do we have to call getCurrentUser() several times Firebase?
I am creating a Journal app. I am currently working on the functionality for if the user is already logged in—bypass the “get started/log in activities” In the video I am watching to create a journal app, the instructor calls mUser = firebaseAuth.getCurrentUser(); several times. He calls it in onStart(), in onCreate() and in onAuthStateChanged(). I can understand why we
Firebase Authentication email
Currently, I am working on an Android project. I started the project with sign up and login pages using Firebase. It goes like this: A new user enters the required details with email and password as login credentials. Meanwhile, a verification mail is sent to the provided email address, the user needs to verify the authentication by following the link
How to make firebase Realtime database writable according to authentic users
I am making an android app where anyone can read the data but only an authentic user (whom we added in Realtime database as ‘User’ with email id) can modify or add. I want that no one other than authentic user can write in his /her database. Others can only read. Here is my database structure:- Answer Your rule might
Firebase authentication works only on debug version
I have an app on google play: https://play.google.com/store/apps/details?id=com.conta.ftof and I have a big problem. I can’t get firebase authentication with phone number to work on the signed version. in fact, it works only with the debug version (when in the release version I insert the number and click the send button, the toast is returned: unknown error) … Precisely for