R Randori Member Licensed User Longtime User Sep 5, 2016 #1 I attempting to configure from the tutorial and not getting it to work. I believe I have isolated the line of the error log that has some useful information: You have wrong OAuth2 related configurations, please check. Detailed error: INVALID_AUDIENCE.
I attempting to configure from the tutorial and not getting it to work. I believe I have isolated the line of the error log that has some useful information: You have wrong OAuth2 related configurations, please check. Detailed error: INVALID_AUDIENCE.
Erel B4X founder Staff member Licensed User Longtime User Sep 5, 2016 #2 Are you using Google sign-in? Start a new project with a new key and carefully go over the steps from the tutorial: https://www.b4x.com/android/forum/threads/firebaseauth-authenticate-your-users.67875/ Upvote 0
Are you using Google sign-in? Start a new project with a new key and carefully go over the steps from the tutorial: https://www.b4x.com/android/forum/threads/firebaseauth-authenticate-your-users.67875/
R Randori Member Licensed User Longtime User Sep 6, 2016 #3 OK...this was not wonderfully easy, but I figured it out. It all came down to the Certificate Fingerprints (SHA-1)...I needed to get a program called keystore explorer to open the keystore file from the basic4android install path and use that instead of the key that I got using the keytool as they were different. Once I did this the login button went on to prompt if I wished to allow the app to access after selecting the account. Upvote 0
OK...this was not wonderfully easy, but I figured it out. It all came down to the Certificate Fingerprints (SHA-1)...I needed to get a program called keystore explorer to open the keystore file from the basic4android install path and use that instead of the key that I got using the keytool as they were different. Once I did this the login button went on to prompt if I wished to allow the app to access after selecting the account.
freedom2000 Well-Known Member Licensed User Longtime User Sep 6, 2016 #4 Randori said: OK...this was not wonderfully easy, but I figured it out. It all came down to the Certificate Fingerprints (SHA-1)...I needed to get a program called keystore explorer to open the keystore file from the basic4android install path . Click to expand... Please could you tell me where is this file in B4A ? thanks Upvote 0
Randori said: OK...this was not wonderfully easy, but I figured it out. It all came down to the Certificate Fingerprints (SHA-1)...I needed to get a program called keystore explorer to open the keystore file from the basic4android install path . Click to expand... Please could you tell me where is this file in B4A ? thanks
R Randori Member Licensed User Longtime User Sep 6, 2016 #5 Sure...(but please note that I am far from an authority on this topic)... I located the debug.keystore file in the folder "C:\Program Files (x86)\Anywhere Software\Basic4android". The Certificate Fingerprints (SHA-1) from here must be what B4A uses as it compiles as it worked instantly. Upvote 0
Sure...(but please note that I am far from an authority on this topic)... I located the debug.keystore file in the folder "C:\Program Files (x86)\Anywhere Software\Basic4android". The Certificate Fingerprints (SHA-1) from here must be what B4A uses as it compiles as it worked instantly.
freedom2000 Well-Known Member Licensed User Longtime User Sep 6, 2016 #6 Randori said: Sure...(but please note that I am far from an authority on this topic)... I located the debug.keystore file in the folder "C:\Program Files (x86)\Anywhere Software\Basic4android". The Certificate Fingerprints (SHA-1) from here must be what B4A uses as it compiles as it worked instantly. Click to expand... Ok I see ! You can access the same information using B4A. GO to the tools menu then "private Sign key" then into the text at the bottom of the page you will see the SHA1 Upvote 0
Randori said: Sure...(but please note that I am far from an authority on this topic)... I located the debug.keystore file in the folder "C:\Program Files (x86)\Anywhere Software\Basic4android". The Certificate Fingerprints (SHA-1) from here must be what B4A uses as it compiles as it worked instantly. Click to expand... Ok I see ! You can access the same information using B4A. GO to the tools menu then "private Sign key" then into the text at the bottom of the page you will see the SHA1
R Randori Member Licensed User Longtime User Sep 6, 2016 #7 I do not see this in my version. I am using v6.0. Upvote 0
R Randori Member Licensed User Longtime User Sep 6, 2016 #9 OK...I see...if you go ahead and select the key using browse... Upvote 0
