TypeError with Uint8Array

[LuckeeDev]

Hello there! I'm trying to validate a JWT in a Next 12's middleware, as described by this example. However, both the repo example and my implementation throw errors.

This is my code in short.

import { jwtVerify } from 'jose';

const token = request.cookies.token;
const secret = new TextEncoder().encode(process.env.JWT_SECRET);
const verified = await jwtVerify(token, secret);

And it throws this error:

TypeError: Key must be one of type CryptoKey or Uint8Array. Received an instance of Uint8Array
    at symmetricTypeCheck (webpack-internal:///../../node_modules/jose/dist/browser/lib/check_key_type.js:10:15)
    at checkKeyType (webpack-internal:///../../node_modules/jose/dist/browser/lib/check_key_type.js:42:9)
    at flattenedVerify (webpack-internal:///../../node_modules/jose/dist/browser/jws/flattened/verify.js:89:71)
    at compactVerify (webpack-internal:///../../node_modules/jose/dist/browser/jws/compact/verify.js:22:97)
    at jwtVerify (webpack-internal:///../../node_modules/jose/dist/browser/jwt/verify.js:13:97)
    at verifyAuth (webpack-internal:///./pages/articles/_middleware.ts:14:75)
    at Object.middleware [as handler] (webpack-internal:///./pages/articles/_middleware.ts:21:9)
    at adapter (webpack-internal:///../../node_modules/next/dist/server/web/adapter.js:30:35)
    at Module.__WEBPACK_DEFAULT_EXPORT__ (webpack-internal:///../../node_modules/next/dist/build/webpack/loaders/next-mi
ddleware-loader.js?page=%2Farticles%2F_middleware&absolutePagePath=C%3A%5Csrc%5Cprojects%5Cweb%5Ccsl%5Capps%5Cweb%5Cpage
s%5Carticles%5C_middleware.ts!:17:87)
    at Object.run (C:\src\projects\web\csl\node_modules\next\dist\server\web\sandbox\sandbox.js:154:30)

Vercel's code, however, throws this error:

error - node_modules\jose\dist\browser\jws\flattened\sign.js (11:0) @ new FlattenedSign
TypeError: payload must be an instance of Uint8Array

For the sake of testing, the JWT_SECRET environment variable is a simple string like myjsonsecret.

Any idea on how to solve this?

[panva]

This was an upsteam bug in next.js and was fixed in https://github.com/vercel/next.js/releases/tag/v12.0.4

[LuckeeDev]

Thanks a lot for the fast reply!