-
Notifications
You must be signed in to change notification settings - Fork 0
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
restore login ability #321
Comments
for the time being, we can get around this error locally by updating the code as stated below. it means we get taken to a "middle man" site where we have to choose to be taken to scientist. however, since this is only a problem locally, I'm setting this aside for more pressing issues. # _app.js
# change this
signIn: () => signIn(process.env.NEXT_PUBLIC_PROVIDER_NAME)
# to this
signIn: () => signIn() |
unsure if it's related to the initial problem, but we are now unable to sign in locally, or on the production (vercel) site. once I clicked "sign in", I was redirected to the supplier's marketplace on scientist.com. I was able to log in, but the redirect erred. it took me to the nextauth default login page with a "Try signing in with a different account." message. clicking "Sign in with beachsidebiotech" didn't work. the reload button next to the url bar spun like it was trying to go somewhere, but once it finished we never left the page. going back to the homepage still showed that I wasn't signed in. the server logs show the error below: [next-auth][error][OAUTH_CALLBACK_HANDLER_ERROR]
https://next-auth.js.org/errors#oauth_callback_handler_error Request failed with status code 404 {
message: 'Request failed with status code 404',
stack: 'AxiosError: Request failed with status code 404\n' +
' at settle (file:///Users/alishaevn/Work/webstore/node_modules/axios/lib/core/settle.js:19:12)\n' +
' at Unzip.handleStreamEnd (file:///Users/alishaevn/Work/webstore/node_modules/axios/lib/adapters/http.js:512:11)\n' +
' at Unzip.emit (node:events:525:35)\n' +
' at Unzip.emit (node:domain:489:12)\n' +
' at endReadableNT (node:internal/streams/readable:1359:12)\n' +
' at process.processTicksAndRejections (node:internal/process/task_queues:82:21)',
name: 'AxiosError'
} |
the `signIn` function from "next-auth/react" uses `fetcher` and returns a 404 error response. throwing that error causes an `OAUTH_CALLBACK_HANDLER_ERROR`, which prevents users from signing in. `signIn` doesn't pass a url to `fetcher`. the check below ensures that other errors still get thrown - ref: #321
Story
we are unable to login locally or in production (vercel). the workaround mentioned in the comments below does not work for this error.
this is not affecting phenovista's digital storefront.
Acceptance Criteria
Screenshots / Video
browser error
INITIAL ISSUE
Story
locally, we are receiving a CORS error when pressing the "sign in" button. the same error is not seen at https://webstore-staging.vercel.app/.
Acceptance Criteria
Screenshots / Video
Testing Instructions and Sample Files
The text was updated successfully, but these errors were encountered: