Issue with creating user, cannot read properties of null about kpop-stack HOT 7 CLOSED

Glad it is all working. Thank you so much for opening the report and working with me on this! Keep us posted on what's next for ya! 😄

from kpop-stack.

I notice here you've got a 500 error there which seems not so good! What was the UI feedback from Remix you received with the failed creation of the user?

from kpop-stack.

Hi Maxcell. This is what I get when try to signup.
The user is created in supabase. But it doesn't look like it's completing the operation.
When trying to login I get a invalid user/pass.

When trying from deployed netlify site, I can't make it work too, but error is different:

looks like I have wrong configuration, but all I did was set variables copying from supabase settings.

Thanks

from kpop-stack.

@leofmoura No worries at all! Happy to help out. Just one last check, did you perform the necessary SQL queries in the README under the Database section? https://github.com/netlify-templates/kpop-stack#database

from kpop-stack.

Ok, that fixed my local env. I missed that, thanks.

About the netlify site:

I'm getting this error when creating an account:

{
  "errorType": "Runtime.UnhandledPromiseRejection",
  "errorMessage": "FetchError: invalid json response body at https://rktuocznllhvbarshwit.supabase.co/auth/v1/signup reason: Unexpected token M in JSON at position 0",
  "trace": [
    "Runtime.UnhandledPromiseRejection: FetchError: invalid json response body at https://rktuocznllhvbarshwit.supabase.co/auth/v1/signup reason: Unexpected token M in JSON at position 0",
    "    at process.<anonymous> (/var/runtime/index.js:35:15)",
    "    at process.emit (events.js:400:28)",
    "    at process.emit (/var/task/node_modules/source-map-support/source-map-support.js:516:21)",
    "    at processPromiseRejections (internal/process/promises.js:245:33)",
    "    at processTicksAndRejections (internal/process/task_queues.js:96:32)"
  ]
}

from kpop-stack.

Let me know if that also fixed on the Netlify deploy as well, it should resolve well! Or is the error above still after making the migrations?

from kpop-stack.

Yes, it fixed. I had a caching issue, but as soon I've re-deployed everything, it worked fine.
Nice to have you here!

from kpop-stack.