“Handling response” stuck on first app install when redirecting to Theme Editor

Extensions
1

Hi all,

I’m building a very simple embedded Shopify app with Remix + Polaris + App Bridge. The flow is:

  1. Merchant installs the app (first visit).
  2. They see an input field for a numeric, 4 digit key, specific to our platform.
  3. They click Save.
  4. We store that numeric key as a shop-level metafield, then immediately redirect them into the Theme Editor → App Embeds section.

The problem:
On the very first install, when they click Save, the interface changes to “Handling response” and never redirects. After a manual browser refresh, clicking Save works perfectly—no “Handling response” hang, redirect happens immediately.

I suspect Remix’s <Form> / loader-redirect dance inside an iframe is getting blocked the first time, but I haven’t been able to nail down exactly why. The merchant flow breaks until they reload, which is a terrible UX.

2

Hey @user121 :wave: thanks for breaking down the replication steps here, happy to take a look into this.

If you have a dev shop with the app installed, I can definitely take a look at this to try and replicate. If you’re able to share a shop ID/app ID - I can look into this locally and see if we can figure out what may be happening here.

Hope to hear from you soon!

3

Hey @Alan_G, thank you for your reply!

I believe this is the information you are asking about:

Dev store: george-testing-store-st.myshopify.com

Blockquote

4

I know it’s a dev store, but I’d suggest removing the API key and generating a new one so this one gets disabled.

I think Alan asked for the app ID, not api key :smiling_face:

1 Like
5

Thank you for the clarification! I was trying to figure out what the App ID is, I believe this might be it?

App ID: 240572530689

1 Like
6

Thanks @user121 (and @curzey !) - looking into this for you - I’ll loop back with you when I have some updates to share :slight_smile:

2 Likes
9

Hey @user121 :waving_hand: - I’m still looking into this with our team. Would you be able to share a screen recording of the issue if possible? I noticed that the app is not public yet, so it is a little difficult to replicate on our end. If you’re also able to create a HAR file as you replicate the issue that would be super helpful too (more info on how to create those here).

Hope to hear from you soon - we’ll get this looked into.

10

Hey @Alan_G, of course! I am going to give the HAR file documentation a quick read and send it all to you in a bit. Thank you!

1 Like
11

Hey @Alan_G , I am not allowed to send files here that are not authorized (authorized extensions: jpg, jpeg, png, gif, heic, heif, webp, avif) so I am sending a link for Google Drive. Thank you for your patience! It really means a lot!

12

Thanks @user121 - I was able to grab both files there - I’ll keep digging into this and get back to you once I have an update :slight_smile:

14

Hey @User121 :waving_hand: - still digging into this, but we couldn’t replicate things on our end. When we tried installing the app on a test shop on our end, we noticed that you might have deployed your local config (we saw a Cloudflare tunnel error when we tried installing the app) - just wanted to confirm if that’s the case?

If you’re able to create a version of the app that is hosted somewhere that we can access for a little while, that would be super helpful. If you’d like to share your code, I can also follow up with you over DM to see if we can take a look at that and try to replicate things on our end (you can share a private Github repo if that works)

Thanks!

15

Thanks @Alan_G, I am going to verify if I have deployed my config right now and get back to you in a bit. I honestly believe the bug is some requirement or verification I am missing. I am open to sharing the code, as the app is quite simplistic in nature.

1 Like
16

Hey @Alan_G , I am sorry for the delay! Would you remind me of your email address so I can share a git repo