POS UI Extension: Widespread network issues (primarily print API)

Extensions
1

Hi all,

We’re experiencing widespread network issues affecting our POS UI Extensions across virtually all of our merchants, effectively rendering the extension non-functional for them right now. The Print API in particular seems to be the most affected.

We’re consistently seeing the following errors:

  • You attempted to call a function that was already released.

  • load failed

This is having a significant impact on our merchants’ day-to-day operations, so any help or prioritization you can offer would be greatly appreciated. Please let us know if you need additional context, logs, or reproduction steps from our side, happy to provide whatever would be most useful.

Thanks so much for looking into this!

2

@Christof_Zirkler Hi! looking into this now

3

@Christof_Zirkler Can you give me a shop ID and your app ID so I can look up our logs?

4

Thanks Goupil.

app handle: open-fiskal
affects shops (incomplete):

5

@Christof_Zirkler May have found a fix for the printer issue. Can you give me more details into the “widespread network issues affecting our POS UI Extensions”?

6

Thats great news!

The other (non print related) network errors are a mix of:

  • “load failed”
  • 401s
  • “You attempted to call a function that was already released.”
  • “Network request failed”
  • Operation GenerateSessionToken timed out after 30000ms
7

@Christof_Zirkler We are just deploying a fix now, it should be live shortly. But merchants may have a cached version that expires hourly. We’d ask them to restart their POS in the morning if possible. Keep us in the loop please!

8

In the meantime, would you happen to have reproduction steps on your end? Is this something your dev team was noticing?

9

@Christof_Zirkler I took a look at the `You attempted to call a function that was already released.` errors in the context of your extension. It shouldn’t have any effect on the merchant, but it does look like there might be a double dismiss() call in your code due to a useEffect. when the first dismiss goes through, your extension tears down and likely some state is causing the effect to run again and call dismiss again. The desired outcome for the merchant is that the extension gets dismissed successfully I’m assuming, but the error is noisy. The print stuff looks like it might be related to a spike in 401s with the session tokens, which is what we just patched directly to the CDN. Hopefully the damage comes down.

10

We’d ask them to restart their POS in the morning if possible. Keep us in the loop please!

Hi @JS_Goupil, sorry I was sleeping my timezone.
Even after multiple restarts, the print API is still completely broken, every invocation of shopify.print.print() fails immediately.

11

Invocations of fetch() seem to be totally fine, thanks!.
But yeah, print() is still broken entirely.

12

@JS_Goupil we weren’t logging the errors, but throughout the business day yesterday we had 2 merchants who installed our Cart Transform function for POS, and no matter what we did it simply wouldn’t run. We uninstalled + reinstalled the function multiple times, did a Reset Account on Shopify POS w/ logout, etc.

Merchants who already had our Cart Transform function installed reported no issues.

Last night around 12 hours ago, one of them attempted the reinstall again and it finally started working after he said he uninstalled + reinstalled Shopify POS.

Is what we experienced yesterday related to the same issue in this thread (and hopefully resolved going forward)?

Shop ids:

fillgood-co
browns-top-shelf-meats

13

@derrick Hey Derrick, I’ll take a quick look at this for ya. But it’s probably unrelated. The issues that were being experienced with the print API were due to a beta flag that we rolled out. We rolled back the beta flags to mitigate and deployed a fix, but I don’t think it would be related to Cart Transform at all since the flags in question are purely UI Extension related.

14

@JS_Goupil thanks, we had another instance of this last night with a store in Singapore who installed our Function and it never activated on their device (they sent us a video): store id 39b357-78

What is the best way to ensure that a newly-installed cart transform function for a store gets applied to all POS devices?