I have embedded apps enabled in the app extensions area, and it works fine in my development app with the exact same settings, but when I deploy to staging I am getting this message. I have removed any references to the Embedded app SDK and am only loading the App Bridge, I also double checked that the shopOrigin and api key are correct. Has anyone had a similar issue? Maybe it’s something simple I am missing.
What’s your app ID? I can check what might be going on from here. You can get your numeric app ID from the end of the URL in your partner dashboard when viewing the app specifically.
You have a feature enabled on your app which would enable the use of the Analytics API for example, which at this time cannot be used in tandem with App Bridge.
Hey @Alex , I did double check and we removed all references to ShopifyApp, and we are not even loading the app.js embedded app sdk. Is it an issue that we used those methods in the past and now we aren’t able to upgrade to the App Bridge, or should it be working once those are removed?
Heya. I’ve pulled some levers on my end and you should now be good to use app bridge. Let me know if you notice anything unexpected, but you should be fine.
I can flip the switch on 1644751 but if you’re using any of the above mentioned methods you’ll end up getting flipped back. There’s not too much I can do about that one on my end until the app is clear from making these calls.
The two bars along the top which represent the TitleBar action is a part of App Bridge’s implementation. I don’t believe you can make use of storing the navigation and title in a single bar while being “migrated” to App Bridge at the same time (that is, not using any deprecated Embedded App SDK methods).
Feedback is most welcome on this front though, it’s my job to pass that along, so let me know what kinds of issues this causes for you either here or in a DM. If you need any help migrating, let me know as well. (I could probably roll you back to your prior state as well)
@DiscountNinja if you’re referring to the Refresh + Settings buttons, it looks like those are considered secondary buttons, not navigation items. Are you calling ShopifyApp.Bar.initialize() with buttons in the options object? I’m not seeing us pulling any navigation items or buttons from your app’s settings.
I’ve now put the new version of the app live and unfortunately the App Bridge part of the app doesn’t work.
So now we have two problems, indicated in bold in the summary.
Note that our production app routes users to different versions of our backend:
V1 is our legacy version, V2 is the current version, V3 is the new release (not GA).
The test app routes all users to V3.
Here’s a summary:
On the test app (2911355)
All traffic is routed to V3 of the app
Navigation items are not displayed
Menu buttons are displayed correctly using App Bridge
On the production app (1644751)
When routing to V1 of the app
Deleted navigation items are displayed (since they contain links to V2 this causes the app to break)
Menu buttons are displayed correctly using the old Shopify Embedded Apps javascript
When routing to V2 of the app
Deleted navigation items are displayed (they work since they are V2 related, but we don’t want to display them)
Menu buttons are displayed correctly using the old Shopify Embedded Apps javascript
When routing to V3 of the app
Deleted navigation items are displayed (since they contain links to V2 this causes the app to break)
Menu buttons are not displayed. The newer App Bridge is used here.
Regarding the first problem:
These navigation items were created as a work around last year when problems with the App Bridge were breaking our app
It seems there is a bug (or a cache?) when deleting them
Regarding the second problem:
There are no error messages in the console
The only differences between the production and test app I can see are:
They use a different entry point (App Url), configured in the App Setup
Potentially they are configured differently in your backend because the test app was created much later than the production app
I’d appreciate some help on this because at it stands the navigation is breaking the user experience for a large percentage of our users in production.