Error on Missing REquired client_id Despite being set

[lewismunene020]

I keep getting this error in development and i have already set the parameter whats might be the problem its probably a bug

Uncaught (in promise) 
Object { message: "Missing required parameter client_id.", stack: "Bp@https://accounts.google.com/gsi/client:229:367\nCp@https://accounts.google.com/gsi/client:222:467\nMq@https://accounts.google.com/gsi/client:280:395\nUq@https://accounts.google.com/gsi/client:284:450\n@https://accounts.google.com/gsi/client:288:754\nuseTokenClient/<@http://192.168.1.103:3000/_nuxt/node_modules/.cache/vite/client/deps/vue3-google-signin.js?v=9ea727e1:347:73\ncallWithErrorHandling@http://192.168.1.103:3000/_nuxt/node_modules/.cache/vite/client/deps/chunk-RAKT47ZN.js?v=f15bec11:1565:18

[kasvith]

hi, this is related to #11

[kasvith]

btw can you reproduce this in prod? or this only affects in dev mode?

[lewismunene020]

it only happens in development mode

…

On Mon, Oct 30, 2023 at 9:23 PM Kasun Vithanage ***@***.***> wrote: btw can you reproduce this in prod? or this only affects in dev mode? — Reply to this email directly, view it on GitHub <#14 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXNGT4BQ2RJLLW4BZTJN5EDYB7WB5AVCNFSM6AAAAAA6SHQMN6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBVHAYDIMZWGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[ibrahimrehman1]

Hi @kasvith Any luck on this? I am having the same issue

[kasvith]

Hi @ibrahimrehman1 not yet. we couldn't identify the issue yet.

[kasvith]

at this point im wondering whether this is an upstream issue in nuxt itself

@ibrahimrehman1 is this only happening in dev mode?

[ibrahimrehman1]

Yeah I am in dev mode and it's not working. It's strange it was working fine a while ago but then I merge my changes with some other developer and it stopped working however nothing crucial was changed during that merge. Though I might be wrong

[kasvith]

hmm these reports came very recently...i still cant figure out why its happening

[lewismunene020]

think it might be something to do with cache since when i restart server its reflecting

…

On Thu, Nov 2, 2023 at 7:33 PM Kasun Vithanage ***@***.***> wrote: hmm these reports came very recently...i still cant figure out why its happening — Reply to this email directly, view it on GitHub <#14 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXNGT4DKR247OIRFNU35YMTYCPDONAVCNFSM6AAAAAA6SHQMN6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJRGA3TQMJRGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[kasvith]

Hmm probably this might be an upstream nuxt issue

On Sat, 4 Nov 2023 at 9:03 AM Lewis Munene ***@***.***> wrote: think it might be something to do with cache since when i restart server its reflecting On Thu, Nov 2, 2023 at 7:33 PM Kasun Vithanage ***@***.***> wrote: > hmm these reports came very recently...i still cant figure out why its > happening > > — > Reply to this email directly, view it on GitHub > < #14 (comment)>, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AXNGT4DKR247OIRFNU35YMTYCPDONAVCNFSM6AAAAAA6SHQMN6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJRGA3TQMJRGE> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> > — Reply to this email directly, view it on GitHub <#14 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADGCQC6J6ABBKG4VFA77T3TYCWZP5AVCNFSM6AAAAAA6SHQMN6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJTGMZDIMRSGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Kasun Vithanage

[kasvith]

Hi @ibrahimrehman1 @lewismunene020 can you check with nuxt3.8.1 ? as per #11 (comment)

[lewismunene020]

Yes, I will check.

…

On Mon, Nov 6, 2023, 19:33 Kasun Vithanage ***@***.***> wrote: Hi @ibrahimrehman1 <https://github.com/ibrahimrehman1> @lewismunene020 <https://github.com/lewismunene020> can you check with nuxt3.8.1 ? as per #11 (comment) <#11 (comment)> — Reply to this email directly, view it on GitHub <#14 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXNGT4AJAHJRAPUQ2ZUINT3YDEGNLAVCNFSM6AAAAAA6SHQMN6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJVGM3TKMBVGA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[kasvith]

Hi @ibrahimrehman1 @lewismunene020 can you test v0.0.10 and verify it works?

[ibrahimrehman1]

Hi @kasvith I forgot to update here but the issue was somehow resolved automatically without me changing the nuxt version or this package version few days ago. I am currently in dev mode and things are working fine now, strange 🤷‍♂️

[kasvith]

idk...i double checked...i was in the dev mode in my local env and it worked fine. but after I publish to npm it doesn't work properly

this error reported recently...before that it was just fine

[kasvith]

i made a weird observation

import { defineNuxtPlugin, useRuntimeConfig } from "#app";
export default defineNuxtPlugin(async (nuxtApp) => {
  console.log("nuxt-vue3-google-signin plugin"); // this console log make it works
  const { googleSignIn } = useRuntimeConfig().public;
  if (googleSignIn) {
    const plugin = await import("vue3-google-signin");
    nuxtApp.vueApp.use(plugin.default, { clientId: googleSignIn.clientId });
  }
});

removing it causes the problem in dev mode again

[kasvith]

Lets close this and track it #11

[lewismunene020]

thanks for that it worked

…

On Mon, Nov 6, 2023 at 10:05 PM Kasun Vithanage ***@***.***> wrote: Closed #14 <#14> as completed. — Reply to this email directly, view it on GitHub <#14 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXNGT4GDHZI4JKVN6CTTAWTYDEYHFAVCNFSM6AAAAAA6SHQMN6VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJQHA3TOMZWGIZDENI> . You are receiving this because you were mentioned.Message ID: ***@***.*** com>

[kasvith]

@lewismunene020 i think issue is still there, check the other thread

[lewismunene020]

But it the funny thing is that it disappears once you restart the server

[kasvith]

This is definitely an issue with upstresm nuxt

On Tue, Nov 7, 2023 at 2:59 PM Lewis Munene ***@***.***> wrote: But it the funny thing is that it disappears once you restart the server — Reply to this email directly, view it on GitHub <#14 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADGCQC6AH7426BLGQ5NSSL3YDH5Q7AVCNFSM6AAAAAA6SHQMN6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJYGEZDIMBSHE> . You are receiving this because you modified the open/close state.Message ID: ***@***.***>

-- Kasun Vithanage