Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't get Google OAuth to work #10

Open
diogox opened this issue Sep 8, 2020 · 2 comments
Open

Can't get Google OAuth to work #10

diogox opened this issue Sep 8, 2020 · 2 comments

Comments

@diogox
Copy link

diogox commented Sep 8, 2020

Hi 馃憢

First of all, I'm not sure if this a problem with the library itself. I might be missing something here.

If that is the case, I would really appreciate it if you could still take the time to help me out and perhaps this issue might serve as documentation to others in the future.

So, the problem I'm getting is the following:

  • I've set up the code like the README file exemplifies.
  • When I click the button, it opens the Google page for the user's consent.
  • After consenting, the page closes.
  • Nothing happens on my page. It doesn't redirect, it doesn't log anything.

Here's what the code looks like:

<script lang="ts">
    import Tailwindcss from '../Tailwindcss.svelte';
    import { GoogleAuth } from '@beyonk/svelte-social-auth';
</script>

<style>

</style>

<Tailwindcss/>

<main>
    <div class="bg-white">
        <h1>Login</h1>
        <br/>
        <GoogleAuth clientId={process.env.OAUTH_GOOGLE_CLIENT_ID}
                    on:auth-success={e => console.log(e.detail.user)}
                    on:auth-failure={e => console.log(e)}
        />
    </div>
</main>

I can't figure out why it's not working... Do you see what might be causing this issue?

Thanks in advance :)

@antony
Copy link
Member

antony commented Nov 1, 2021

Apologies, I managed to not spot any issues at all on this repository!

I'm assuming that after a year you have found a solution to this or another library?

@diogox
Copy link
Author

diogox commented Nov 2, 2021

No problem ^^

I think I dropped whatever I was working on at some point, but I recall figuring out that this worked fine when in incognito mode. Meaning it was most likely one of my extensions causing the issue.

I've also seen this behavior on some pretty high-level websites, so it's probably safe to close this issue :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants