Showing Handling response on App

[muhammad-hunnain786]

I create app using npm init @shopify/app@latest and i run it on my store after installing on my store it just show "Handling response" and stuck at there

on cmd console i see this

16:44:21 │ remix │ [shopify-app/INFO] Authenticating admin request

on browser console i see this warning

Warning: Extra attributes from the server: processed_6f9b7d42-15a2-4061-bc60-5dd3e7e76dc9

Iam on windows 11 64bit

and

browser is chrome

[lizkenyon]

Hi there 👋

I was not able to reproduce this issue.

I would encourage you to turn on debugger level logging to see if it gives you any more information about what my be going wrong.

const shopify = shopifyApp({
  apiKey: process.env.SHOPIFY_API_KEY,
  apiSecretKey: process.env.SHOPIFY_API_SECRET || "",
  apiVersion: ApiVersion.October24,
  scopes: process.env.SCOPES?.split(","),
  appUrl: process.env.SHOPIFY_APP_URL || "",
  authPathPrefix: "/auth",
  sessionStorage: new PrismaSessionStorage(prisma),
  distribution: AppDistribution.AppStore,
  restResources,
  future: {
    unstable_newEmbeddedAuthStrategy: true,
  },
+ logger: {
+ level: LogLevel.Debug,
+ },

Closing for now if you believe this is a bug with the app template, please provide us with code that can reproduce the issue, and reopen this issue.

[lukeclifton]

Hey. I was seeing the same "handling response" page when trying to run the app locally.

@lizkenyon Your suggestion of turning on the debugger logs helped show me the real cause of the issue.

Is there a way we can improve the error handling so that errors such as this bubble up to the UI and we don't just see the "handling response" state?

[lizkenyon]

Hi @lukeclifton

I agree this could be an area of improvement. Until then I would recommend having debug level logs turned on while you develop locally.

[Lium-7768]

Hi @lizkenyon

I also have the same problem

[lizkenyon]

Hey @Lium-7768 Thanks for the flag!

We have noted that finding a better way to surface errors is an area for improvement.

If you look at your logging it looks like there is a different error message in this case, than what was reported earlier (Failed to validate session token: Failed to parse session token.) If you believe that our error is caused by a bug in the template, and you would like us to investigate further, please provide us with code for reproduction, and create a new issue.