Peter Perlepes

Hey @MedicusIO :) Can you please gives us some information on your setup and the packages used ? _(an example repo would be even better)_

Thanks peeps, it would be really helpful for us to start checking the issue based on the setup and give you a resolution.

Me and @nikosdouvlis are probably going to be checking today if we can change this logic to plain string from `backend-core`, removing the need to fetch.

Hello @karam94 Thanks for the report, can you please send the 401 request information ? _(headers, any response etc.)_ Also does this happen only by setting this option to false...

Hey @estephinson Thanks for the comment. For API routes _(which we currently support on Next.js 12.2+)_, when using the `experimental-edge` runtime, returning a `NextResponse` is valid. If you face any...

@paulboocock Fixed the dots 😆 In this PR I will keep the change as it is for now since it was causing a cryptic error for users. Moving forwards let's...

@adatzer Checked a bit an example implementation and it seems there is the same issue with other error codes as well. I am wondering if this ever worked 🤔 What...

It is external and comes from the [reference](https://developers.google.com/youtube/iframe_api_reference#onError). The double mapping would come from the fact that we do not just send the errors as they arrive from the API...

Yeap that is Option 1 in a nutshell! _(I might have messed up what changes are needed in each option)_ All in all, we just change the mapping to fit...

Yes on `release/3.6.1` or `release/3.7.0` which is yet to be seen based on the types of changes.