https://kotlinlang.org logo
Join Slack
Powered by
Anyone else having issues signing in? I did fresh...
# confetti
j
Anyone else having issues signing in? I did fresh install from play store and not working here for some reason....will take look at logs later.
hmm, it worked with debug version
b
Just updated the app signed out and back in again. It was not possible.
j
hmm, strange
My wife re-installed/signed in on her phone (she's on beta channel) and worked fine
b
Clean install from the store solved that error message. Bit still can't log in.
XRecorder_22042023_103505.mp4
j
yeah, that's what I see here
b
The birds got caught singing in the record 😁
j
none of the SHA values should have changed so don't think it would be that (that's generally the suggestion on SO to this issue!)
@mbonnin just in case you've come across this?
Might try and publish build of older versions of the code (since the beta release) to internal channel and see if it's related to any code change
just confirmed that the app signing 
SHA-1 certificate fingerprint
in play console is also one in firebase settings
m
Google has a validation process for the oauth screen, it's in the gcp console, I'll double check
j
Wonder why it would start having issues now
And seems to work with debug build
c
I find it a bit weird, but perhaps Google is making some sort of verification ofnAndroid Auto and the update is on hold until they give it green light?
I’ve just installed on my device and everything was smooth 😕
j
can you check what version you have
c
Oh, wait, it seems I can’t login
I don’t have any error message, but it doesn’t keep me logged (let me check the logs)
v1.0.161
j
I'll try publishing build of code before the auto changes (to internal channel) and see if that works
hmm, seems to be same issue
(republishing latest code now)
will be 1.0.165
c
I’m debugging the sign in, and the error seems to be returned directly from Google Sign In. 
onAuthError
gets triggered; I’m running on release to fix Android Auto, but I’ll jump to debug afterwards to see if I can see any log
I’m able to retrieve the sign in error in debug: 
com.google.android.gms.common.api.ApiException: 10:
https://stackoverflow.com/questions/47437678/why-do-i-get-com-google-android-gms-common-api-apiexception-10
j
@mbonnin could this be in any way related to setup for main AndroidMakers app.....think they're using some of same firebase setup?
am able to sign out/in of that app 🙂
m
AndroidMakers is theorically completely separated now
It does say "testing" here, I'll hit the publish button
j
strange
m
Gosh
j
what!
does every app with firebase login have to do all that!
m
🤷
We're requesting (but not using) user email
j
wonder why we're only seeing this now
maybe we went over some quota....
m
Not sure if firebase can work without the 
./auth/userinfo.profile
scope
Also at some point later this year we'll need to provide a way for users to delete their account
j
did main AndroidMakers app have to do all that?
m
nope, let me check how it's configured there
Screenshot 2023-04-22 at 12.31.47.png
Looks like it's pending review ? So the same thing may happen there...
j
that one at least says it's in production
m
Yea
I've submitted the app for verification
It didn't ask about a Youtube video
j
did you also get "OAuth Verification Request for Project Confetti-Firebase (id: confetti-164da)" email?
"Thanks for your patience while we reviewed your project. To continue with the verification process, you need to update your project Confetti-Firebase (id: confetti-164da) to comply with our requirements. Domain Verification Please verify the ownership of the following domain(s): • confetti-164da.firebaseapp.com, confetti-app.dev Go to the Search Console to complete the domain verification process. The account you use must be either a Project Owner or a Project Editor on Confetti-Firebase (id: confetti-164da). If the listed domain(s) are not required for the project, please remove them from the authorized domains section of your OAuth Consent Screen in Google Cloud Console. Please note: The project you are seeing is your own. When you've made these updates to your project, please reply to this email to confirm that you're now in compliance"
m
Yep, I have that email. Not sure about the firebaseapp.com domain though 🤔
So I have this now which should be good for confetti-app.dev
Going to remove the firebaseapp.com domain
Resubmitted
j
it's a "messy" process!
m
Yea, it's pretty opaque 😞
I understand why it's there though. We're good-intentioned but the web is usually not like that 😅
j
true 😃
m
Would be nice to have a no-verification signin though. Just give an uid
I might try to remove the public info scope on the Android Makers app, see what this makes
j
The other thing that's strange is that i was able to log out/log in using the beta version of app on my wife's phone....
"6 weeks"!!
m
😞
If your app doesn't need to display an icon, you can skip the verification process and no action is required
Can we disable the icon?
Copy code
The only exception to this behavior is if your app requests a subset of the following: name, email address, and user profile (through the userinfo.email, userinfo.profile, openid scopes or their OpenID Connect equivalents). For such requests, your users do not need to be in the trusted user list, they will not see a warning message, and their authorizations will not expire after 7 days. If your app uses Sign in with Google to authenticate users then this exception also applies. If your app requests any other OAuth scopes, then this exception does not apply.
Maybe just "just" need to stay in testing forever 🤔
j
"Can we disable the icon?" I guess so, if it gets us past all this....presumably AndroidMakers app will have same issue
"Maybe just "just" need to stay in testing forever" - can we do that?
Also, do you know why it still seems to work for my wife running beta version?
or is it somehow related to expiry/refresh of token?
m
Not sure
Alright so now it even doesn't work in testing...
j
it's very as you say opaque.....hard to know cause when something goes wrong
m
I have it working again unfortunately that will most likely require an update of the app 😕
I re-created another set of client ids...
I think we can stay in testing mode forever, there's a warning displayed but anyone can log in from my understanding
Next question is if it's going to stop working if we try to push to production
It'd be ok to wait 6 weeks in "testing" as long as users can still log in
j
the other strange thing is that it's working with debug build here
m
Can you check with a release build?
j
yeah, I can pull down your PR and publish that
m
The SHA1s are not private right?, I can put them in the PR for future reference?
j
hmm, thought they were
but could be wrong
m
Ok, I'll blur the production one
j
hmm, that's published but seem to be seeing same issue
v169
I don't see 
ApiException
in logs....were you seeing that there before?
m
Yes
Do you get it working in debug at least?
j
it had been working in debug here before
you mean with new code?
btw seeing following fwiw
Copy code
04-22 17:26:58.673  6804 11921 I PeopleChimeraService: onService. callbacks = audp@888676e, request = com.google.android.gms.common.internal.GetServiceRequest@eabbe0f
04-22 17:26:58.686  6804 29435 E BasePeopleOperation: Failed to load OwnerAvatar from MDI with cause: %s
04-22 17:26:58.686  6804 29435 E BasePeopleOperation: java.util.concurrent.ExecutionException: cnzl
I'll try debug now
working in debug
m
WT
Turns out we might have had 2 issues: 1. Oauth screen verification: (not 100% sure about this one). I ended up putting the Oauth screen in "testing" mode and regenerating the Android client ids (PR). It's not 100% clear if everything was required but it's working in debug with this. I'll try to publish the Oauth screen again after Android Makers 2. Issue with Firebase and R8 full mode: this one is 100% sure and reproducible (PR)
j
v171 in play store now has these changes
b
It fixed the problems for me. 👍
51 Views
Open in Slack
PreviousNext
Powered by