Closed vborbely closed 1 year ago
:wave: @vborbely, sorry you're having an issue. As the issue template explains, we require that you provide a runnable example that reproduces your issue (please read the issue template). The reason is that maintainers do not have time to try reproduce bugs themselves. Please try to minimize the superfluous code and focus only on reproducing the bug. Please create a new issue with this and we'll be happy to review it! If you're hitting a hard wall, you may consider paid assistance.
Hello and thanks for reporting, It's hard to tell what is going on without code that can be executed. Given that it all works in dev, I believe there's something wrong with your app's configuration. Thank you 🙂
Steps to Reproduce
When I run my code in the DevClient, I can login with the provided Google Sign-In configuration. But when the same code runs after a Production build, there is no user consent visible.
const googleResponse = await GoogleSignin.signIn();
After this call, seems there is no
serverAuthCode
value provided in the response value.Expected Behavior
The user consent screen pops up to able the authorize the user profile data.
Actual Behavior
No user consent pops up in the Android Production build.
Environment