jt274

@darshankawar As linked to in the original post, I organized v1/v2 functions into separate folders according to this: https://firebase.google.com/docs/functions/organize-functions#managing_multiple_source_packages_monorepo I did this because I could not manage to deploy an...

@darshankawar I'd already come across that post, and specifying the region does not make a difference. The function is already in the `us-central1` region. The only error provided is the...

> Does `cloud_functions` plugin support v2 functions? It appears it currently does not support v2 functions. You must call the function with the full URL using a regular HTTP request...

@darshankawar I do believe the original bug report is still valid though, for the `cloud_functions` package. When a function is not found, it should provide an error message that says...

Hmm, interesting thought, I will look into that. Yes, I have confirmed storeCallback and loadCallback are functioning properly. (My auth was working previously, but I had some package update break...

@kato-takaomi-ams I've tried putting the context initialization inside the server.use(). I recently converted the server to Typescript, and it gives the error `Argument of type 'void' is not assignable to...

Since my error seems to be occurring inside `router.get("/")`, I checked to see if the Shopify.Context had been initialized in that route before calling `handleRequest()` (which causes the session to...

Also, to clarify: - Shop goes through auth successfully, redirects to `/?shop=shop_name` - Current session loads successfully by the `Shopify.Utils.loadCurrentSession` calling the `loadCallback` function, and `await handleRequest(ctx)` runs - Server...

@ilugobayo I don't believe you can just check the session yourself. It actually has to be loaded by the library. If it's not loaded (and able to be retrieved with...

There is also this issue which seems related, but I'm not clear on the conclusion that was made: https://github.com/Shopify/shopify-node-api/issues/150