Feature #33358
open
- Status changed from Assigned to In Progress
Google Sign-In integration is still in progress. While trying to connect the Firebase project to the application using the Firebase CLI command, it showed “command not found” on Linux. For Linux, it requires Node.js and npm to install Firebase CLI. However, when I tried downloading Node.js and npm, it returned a 403 Forbidden error due to network restrictions. I need to contact the system administrator for access, but they had already left for the day.
- Status changed from In Progress to Fixed not Tested
- % Done changed from 0 to 100
Today I integrated Google Sign-In with Firebase.
While trying to connect the app with Firebase, I faced some issues, so I contacted the support team. When they checked, they told me I needed to update and install the latest Node.js and npm. It took a lot of time to set everything up.
After that, I continued the implementation by connecting the app with Firebase and setting up Google Sign-In on the main screen after the splash screen. I also added the same setup in the Pax screen, so if the user is not logged in, they can sign in using Google.
Everything is now set up properly.
If the user is new to the app, the Google account email will be used as the username. The system checks whether the user already exists. If the user already exists with the same Google account, the app logs them in and retrieves their token from the backend.
Also available in: Atom
PDF