S-page Breadcrumbs Not Working on Mobile and Tablet Devices

Hey,

I’m using the s-page web component with breadcrumbs, and it works perfectly on desktop.
However, on mobile and tablet devices, the breadcrumbs do not work when clicking on them does nothing.

This issue makes navigation inconsistent across devices.

Issue Details:

  • Component: s-page (Polaris Web Component)

  • Feature: Breadcrumbs

  • Desktop: Working as expected

  • Mobile/Tablet: Breadcrumb clicks do not respond

Expected Behavior:

Breadcrumbs should be fully functional and clickable across all device types, including mobile and tablets.

Actual Behavior:

Breadcrumbs display on mobile and tablet devices but the click action does not trigger any navigation.

Steps to Reproduce:

  1. Render the s-page component with breadcrumbs.

  2. Open the page on desktop → breadcrumbs work correctly.

  3. Open the same page on a mobile or tablet device.

  4. Tap a breadcrumb link.

  5. Observe that nothing happens.

Additional Notes:

  • Tested on multiple mobile and tablet devices.

  • No console errors appear.

  • Breadcrumb implementation follows the standard Polaris Web Component usage.

Could someone help determine whether this is a known issue or if there is a workaround for enabling breadcrumb interaction on mobile and tablet devices?

Thank you!

@Fio @Paige-Shopify I am still experiencing the issue mentioned above. I would appreciate your help in resolving it.

Please do not tag Shopify staff members, they will review and reply when they get chance,

Hi @jaymit_b,

Thanks for reporting this issue to us.
I was able to reproduce the issue in an app following your instructions.

I’ll look into getting a fix shipped for this, and will provide an update here once we’ve got it working for mobile and tablet devices.

@Luke in my experience, tagging staff members is a good way to get posts noticed, and many of these bugs are quite serious, impacting apps with users in production. When I don’t tag anyone “when they get a chance” is often “basically never” without any feedback as to whether the post has been seen by anyone relevant.

Shopify are the ones insisting on using a forum for bug reporting. They are welcome to implement a proper solution and/or to respond in a timely way, even just to say a post has been read by staff, or logged internally, without being prodded. (Not to mention to allow versioning of the library so they don’t break things that are working, or to properly test their libraries in a production-relevant context to avoid many of these bugs in the first place.)

@Luke This post sat for 17 days without any reply. jaymit tagged staff and finally they noticed it and confirmed it’s a real bug.

It’s against the community guidelines.

Please familiarize yourself with them.

I dunno man, these are all people who has engaged with these topics.

Anyway, this is what it takes to get our apps unbroken by Shopify. When there’s a better way I’m all in. The whole idea that these forums are where bugs are reported and communicated seems to be against the community guidelines. But here we are.

It’s against the community guidelines.

Is there any plans to have a proper system for this?

We’re working towards a systematic approach to ensure we address all posts where issues are flagged.

Hey folks,

RE: tagging staff, please continue to respect the community rules and resist tagging individuals. I understand sometimes there are critical issues where something requires urgent attention, and in those cases you can tag me.

2 Likes

Hi, is there any update on this issue? We’re still facing the same behavior and wanted to check if there’s a fix or recommended workaround.

I believe I’m encountering the same issue, and it’s one of the reasons our Built for Shopify submission was rejected. What is the best way to communicate to reviewers that this issue isn’t in our app itself?

In this case, I’m using the <TitleBar /> component from @shopify/app-bridge-react, and <button variant=”breadcrumb” /> doesn’t trigger onClick when the screen is “mobile-sized.” (though it does on desktop).

Hi @tobebuilds, sorry to hear that! I’ve sent you a DM to request the name of the app affected so I can inform the reviewers.

1 Like

Hi all,

We have shipped a fix to resolve this issue. Let us know if you encounter any further issues :slight_smile:

1 Like