Git Product home page Git Product logo

Comments (8)

devfd avatar devfd commented on July 28, 2024 1

the project name can be whatever you want.

what happens if you configure the sdk with only GoogleSignin.configure() ?

if you still get this internal error, please make sure the json file is correctly placed inside your directory. also check within the file that the package name matches yours.

last idea, also make sure the sha1 from the console is correct

from google-signin.

devfd avatar devfd commented on July 28, 2024

assuming your project is correctly configured, have you tried setting the email and project name in the Oauth consent screen (Developers Console -> API Manager -> Credentials) ?

from google-signin.

meaculpa123 avatar meaculpa123 commented on July 28, 2024

Yep, there's an email and project name already there on the consent screen. Although, does the project name have to equal the package name? (Seems weird if it has to as the user would see that.)

from google-signin.

meaculpa123 avatar meaculpa123 commented on July 28, 2024

Yeah, tried the blank configure() call and that had same result.
JSON file I put under /android/app and the SHA1 matched too...kind of ran out of ideas, and switched to a WebView OAuth implementation instead. (Kind of a non-resolution, but, for better or worse it gets the job done.)

from google-signin.

devfd avatar devfd commented on July 28, 2024

well this is weird. if you can put up a public repo I can have a look.

also oauth webview support is something I had in mind for some times. would you care to share your code or do a PR ?

from google-signin.

BigPun86 avatar BigPun86 commented on July 28, 2024

Got it working by re-generating google-services.json. In my case i had to manually edit package name in this file at two places :P But it works now. Not sure if it is important, but i have removed the android/app/build folder and restarted the packager with --reset-cache and builded new....

from google-signin.

xavierarpa avatar xavierarpa commented on July 28, 2024

Assuming that you added a new SHA1 because you tried to do a build on another computer, you just need to regenerate the google-service.json because now you're setting a kind of auth on this build from that computer (that's the reason as I know), it works to me 👍

In addition you could try to do a rebuild, clear cache etc.

from google-signin.

zaraganja avatar zaraganja commented on July 28, 2024

Restart your mobile device or your simulator, then run the project again. this worked for me!

from google-signin.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.