Unhandled error when connecting LinkedIn

[parthkoshti]

📜 Description

Error occurred when going through the oauth flow for LinkedIn profile. Only bringing this up because the app exited and had to be restarted

Here's the log:

2024-12-28T06:07:48.882390351Z [Nest] 171  - 12/28/2024, 6:07:48 AM     LOG 🚀 Backend is running on: http://localhost:3000
2024-12-28T06:07:54.888674192Z 2024-12-28 06:07:54,888 INFO success: backend entered RUNNING state, process has stayed up for > than 10 seconds (startsecs)
2024-12-28T06:09:29.716979882Z {"error":"invalid_redirect_uri","error_description":"Unable to retrieve access token: appid/redirect uri/code verifier does not match authorization code. Or authorization code expired. Or external member binding exists"}
2024-12-28T06:09:29.719880474Z node:internal/process/promises:389
2024-12-28T06:09:29.719892612Z       new UnhandledPromiseRejection(reason);
2024-12-28T06:09:29.719896839Z       ^
2024-12-28T06:09:29.719900304Z 
2024-12-28T06:09:29.719903749Z UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "#<BadBody>".
2024-12-28T06:09:29.719907845Z     at throwUnhandledRejectionsMode (node:internal/process/promises:389:7)
2024-12-28T06:09:29.719911130Z     at processPromiseRejections (node:internal/process/promises:470:17)
2024-12-28T06:09:29.719914335Z     at process.processTicksAndRejections (node:internal/process/task_queues:96:32) {
2024-12-28T06:09:29.719917630Z   code: 'ERR_UNHANDLED_REJECTION'
2024-12-28T06:09:29.719920845Z }
2024-12-28T06:09:29.719923949Z 
2024-12-28T06:09:29.719927134Z Node.js v20.17.0
2024-12-28T06:09:29.837418071Z TypeError: fetch failed
2024-12-28T06:09:29.837446515Z     at node:internal/deps/undici/undici:13178:13
2024-12-28T06:09:29.837450672Z     at async /app/dist/apps/frontend/.next/server/app/(site)/integrations/social/[provider]/continue/page.js:3:27731
2024-12-28T06:09:29.837454457Z     at async it (/app/dist/apps/frontend/.next/server/app/(site)/integrations/social/[provider]/continue/page.js:3:26753) {
2024-12-28T06:09:29.837458062Z   digest: '353303767',
2024-12-28T06:09:29.837461247Z   [cause]: SocketError: other side closed
2024-12-28T06:09:29.837464442Z       at Socket.<anonymous> (node:internal/deps/undici/undici:6020:28)
2024-12-28T06:09:29.837468408Z       at Socket.emit (node:events:531:35)
2024-12-28T06:09:29.837494648Z       at endReadableNT (node:internal/streams/readable:1696:12)
2024-12-28T06:09:29.837498704Z       at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
2024-12-28T06:09:29.837501979Z     code: 'UND_ERR_SOCKET',
2024-12-28T06:09:29.837505063Z     socket: {
2024-12-28T06:09:29.837508158Z       localAddress: '::1',
2024-12-28T06:09:29.837511212Z       localPort: 54912,
2024-12-28T06:09:29.837514247Z       remoteAddress: '::1',
2024-12-28T06:09:29.837517452Z       remotePort: 3000,
2024-12-28T06:09:29.837520506Z       remoteFamily: 'IPv6',
2024-12-28T06:09:29.837523551Z       timeout: undefined,
2024-12-28T06:09:29.837526595Z       bytesWritten: 1615,
2024-12-28T06:09:29.837530000Z       bytesRead: 0
2024-12-28T06:09:29.837533125Z     }
2024-12-28T06:09:29.837536210Z   }
2024-12-28T06:09:29.837539374Z }
2024-12-28T06:09:29.846236474Z 2024-12-28 06:09:29,845 WARN exited: backend (exit status 1; not expected)

Happy to provide more info if needed :)

👟 Reproduction steps

When going through the OAuth flow for LinkedIn

👍 Expected behavior

Error should be handled

👎 Actual Behavior with Screenshots

App shouldn't crash if OAuth fails for whatever reason

💻 Operating system

Linux

🤖 Node Version

20.xx

📃 Provide any additional context for the Bug.

No response

👀 Have you spent some time to check if this bug has been raised before?

• I checked and didn't find similar issue

Are you willing to submit PR?

Yes I am willing to submit a PR!

[nevo-david]

Please ask it on our discord at: https://discord.postiz.com