Passkeys & verification Model, expiresAt always in past
With 1.2.7 I do not get passkeys login working anymore. In the database verification table I see expiresAt always have the same timestamp for each passkey createVerificationValue request (2025-04-16 10:07:45.958). This is in the past and I think this is the cause the browser do not start the webauthn process. Looks like at starting next.js server it's resulting into static timestamp of that moment. It does not recalculate the expirationTime for each
createVerificationValue request.
In code I found:
This should provide a timestamp in the future.
Why does expirationTime not recalculated at every createVerificationValue request?
i'm using prisma 6.6.0 (not using output path) and postgresql database.0 Replies