Jesse Winton

> Next 12.2.0 next-auth 4.10.2 working in local but not in Vercel. token returns null Same here; everything works fine locally but not in Vercel.

> Hmm. @ThangHuuVu might be right. I am able to reproduce this starting with `12.2.3-canary.17`, so something might have happened in [vercel/[email protected]](https://github.com/vercel/next.js/compare/v12.2.3-canary.16...v12.2.3-canary.17). I have a lead, so I'll talk with...

+1. Would love to see this integrated.

Bumping this

@jasonlong I wonder if an easy solution for this could be a demo instance that uses a simple credentialed login and a Vercel cron on an API route to delete...

Could easily be done using Vercel's recommended method! https://vercel.com/docs/cron-jobs#how-to-secure-cron-jobs

How viable would it be to create a simple cli app, like `create-t3-app` that would allow for users to choose the use case? It might be overkill, but could potentially...

@leerob awesome; I suppose I'd wonder if it would be good for the docs to recommend that starter? Right now it's recommending [this starter](https://planetscale.com/docs/tutorials/connect-nextjs-app#set-up-the-starter-nextjs-app). That being said, I was more...