First tab missing in embedded app navigation (Shopify Admin)

Shopify App Store
,
1

Hi everyone,

We’ve noticed an issue with embedded app navigation in the Shopify Admin: the first tab in the navigation never shows up.

  • If you add your expected first tab → it doesn’t render.

  • If you try to duplicate or even insert a fake placeholder as the first item → the fake one doesn’t show either, but the second item in the list does.

So effectively, the first tab is always hidden, regardless of what it is.

Is this a known bug with the embedded app navigation? Has anyone found a proper workaround?

Thanks,
Guilherme

2

Confirmed. Our app also suddenly lost 1st nav menu. Seem there is an issue with App Bridge CDN?

3

I have implemented workaround while waiting Shopify to response about this.
Add / as Homepage/Dashboard will restore the 1st nav menu. Before adding this, our Point Programs nav menu disappeared!

Screenshot 2025-08-26 at 00.51.42
Screenshot 2025-08-26 at 00.51.42554×326 17.5 KB

4

We’re having the same issue with our app. It seems there is a paragraph in the AppBridge docs that explains this behavior. I don’t remember seeing this before though: ui-nav-menu

The first element is required and used to configure the home route of the app. It is not rendered as a link. It needs to have rel="home" set along with the href set to the root path.

5

This definitely seems new and broke my app navigation. Adding an another link home link works. I wish we could back to app-bridge being versioned. Breaking changes like these are becoming way too common recently.

6

Also seeing this issue. We’re working on handling it by adding the defined home link, but it would be great to know if this was an unintentional change that will be changed again or if this is the correct handling moving forward. Either way, unannounced breaking changed like this in App Bridge are getting pretty tiresome.

7

Hi folks - thanks for flagging this, we’re investigating this behaviour now.

8

Hey folks,

We are shipping a fix for this bug right now. Please hold tight. It should be resolved shortly!