"[mf:err] GET /: InvalidCharacterError: Invalid character" - npx superflare@latest new

[tsteckenborn]

Running npx superflare@latest new -> Database Models, Scheduled Tasks-> npm install --legacy-peer-deps-> npx superflare migrate -> npm run dev or npx superflare dev yields the following error on opening the index URL right now:

[mf:err] GET /: InvalidCharacterError: Invalid character
    at atob (.../node_modules/@miniflare/core/src/standards/encoding.ts:33:13)
    at unsign (.../node_modules/@remix-run/cloudflare/dist/crypto.js:29:42)
    at decodeCookieValue (.../node_modules/@remix-run/server-runtime/dist/cookies.js:82:27)
    at Object.parse (.../node_modules/@remix-run/server-runtime/dist/cookies.js:54:60)
    at Object.getSession (.../node_modules/@remix-run/server-runtime/dist/sessions/cookieStorage.js:36:54)
    at handleFetch2 (.../node_modules/@superflare/remix/dist/index.mjs:23:5)
    at ServiceWorkerGlobalScope.[kDispatchFetch] (.../node_modules/@miniflare/core/src/standards/event.ts:385:13)
    at Server.<anonymous> (.../node_modules/@miniflare/http-server/src/index.ts:291:20)

[subhendukundu]

I am facing the same issue, not able to get it to load.

[jplhomer]

🤔 I've seen this sometimes too, and it's usually when the APP_KEY is not set properly in .dev.vars.

Can you confirm you have that value set? It's definitely not a super valuable error message coming from Remix/Miniflare.

[tsteckenborn]

The APP_KEY is defined in the .dev.vars, yet that must have happened through npx superflare@latest new. Yet without the worker itself being pushed by that, I don't exactly know how I could check against the eventual corresponding secret it should be according to https://superflare.dev/deploying#checklist. npx wrangler secret list -jdoesn't work for me, as it seems to be still looking for the toml (Required Worker name missing. Please specify the Worker name in wrangler.toml, or pass it as an argument with --name <worker-name>), npx wrangler secret list --name my-app-name errors with workers.api.error.script_not_found [code: 10007].

Right now I'd assume that the secret therefor isn't set. Yet I'm confused as the only reference to APP_KEY is in the deployment docs.

It might make sense to add the additional steps necessary to:

superflare/packages/superflare/docs/getting-started.md

Lines 6 to 22 in 919e4dc

	## Installation
	The easiest way to start with Superflare is to spin up a brand-new project with the following command:
	```bash
	npx superflare@latest new
	```
	Superflare will ask you which bindings you'd like to use for D1, R2 and KV. It will also offer to create the bindings if you haven't already!
	Once you get your project created, you can start a local development server with:
	```bash
	npx superflare dev
	```
	## Remix + Superflare

and

superflare/packages/superflare/cli/new.ts

Lines 295 to 298 in 919e4dc

	outro(
	`You're all set! \`cd ${path}\`, run \`npm install --legacy-peer-deps\`, and then \`npx superflare migrate\` to get started.`
	);
	}