"Hi, please let me know if there's any update regarding the unique SHA-1 for Niotron apps. I need to implement Firebase Phone Auth, but it’s not working due to the default debug SHA-1. Do I need to purchase any pack or follow a different method?"

Bugs
1

Describe the bug in detail…

Attach Necessary Block Images and Files
Hello Niotron Team,

I am trying to integrate Firebase Authentication in my app built with Niotron. I noticed that the SHA-1 fingerprint shown in the Keystore section is the same for all projects, even after creating a new one.

Due to this, I am unable to get phone authentication and Google Sign-In working in Firebase, because the APK is signed with a shared debug keystore.

Kindly let me know:

  1. How can I get my app’s unique SHA-1 fingerprint?
  2. Do I need to purchase the Keystore Export Pack for this?
  3. Once purchased, will I be able to upload my own keystore and use a unique SHA-1 for Firebase?

I have already integrated Firebase Email/Password login successfully, but phone number authentication is not working due to SHA-1 mismatch.

Please help me resolve this or guide me with the right steps.

Thanks & regards,
Mohd Salman

2

“Hi, please let me know if there’s any update regarding the unique SHA-1 for Niotron apps. I need to implement Firebase Phone Auth, but it’s not working due to the default debug SHA-1. Do I need to purchase any pack or follow a different method?”

3

The SHA-1 is from your keystone. and Niotron provide just one keystone for all you app. But you can import and export keystone.