Intermittent "App failed to load" errors on post-purchase extension

Extensions
1

Hi,

We have a POS post-purchase extension that semi regularly shows an “App failed to load” error on the menu item preventing the user from clicking on it. There doesn’t seem to be a pattern as to why this occurs and it is happening across multiple clients and devices. We have also had reports of the extension being stuck in a loading state. I’ve added a few pictures to show the issues.

What can cause this error message to show and what can we do to mitigate it?

Below is some device information from a client that is experiencing the issue.

Environment

  • App version - 10.19.2
  • Build number - 230691
  • iPadOS version - 17.7.10

Any other questions please let me know.

Many thanks.

app-failed-to-load-issue
app-failed-to-load-issue1920×2560 638 KB

loading-issue
loading-issue1920×2560 494 KB

1 Like
2

Hi @Jake_Maguire

It’s hard to tell what could be causing this without having visibility into your extension code, but one thing to check would be any network-related issues that might be causing the app to fail to load. This includes verifying that all necessary resources are being loaded without delay.

Are there logs you can share for this?

3

Hey Liam,

Appreciate you getting back to me. The code in our menu item is really basic, it just renders a modal once clicked, there shouldn’t be anything that prevents the menu item from showing. Would any of the action code prevent the menu item from appearing? I would assume that none of this code is executed until the modal is clicked?

import { render } from "preact";

export default async () => {
  render(
    <s-button onClick={() => shopify.action.presentModal()} />,
    document.body,
  );
};

Unfortunately we don’t really have any logs on the extension side for me to share.

Thanks again.

4

I have seen issues with preact configurations in the past - you could update update your tsconfig.json to use react instead, eg: "jsxImportSource": "react",

5

Thanks Liam,

If I switch to using that tsconfig.jsonoption would that not result in me having to use the react package instead and run into issues with the 64kb size now I’m not using preact?

Is there anyway I could log the issue that is potentially causing this issue somehow?

Appreciate the help.

6

This is currently still an issue for us.

We’ve added the ability to log in our extensions, is there anything we could be logging to help diagnose this problem? When this issue is reported we see no logs on our side so assume that the extension is not being loaded at all?

Can I provide anything else to aid troubleshooting?