shopify-api-js icon indicating copy to clipboard operation
shopify-api-js copied to clipboard
verified publisher icon Shopify

Embedded navigation - Enable cookies / auth loop

Open stevepsharpe opened this issue 4 years ago • 3 comments

Issue summary

I have a fresh embedded app created via the CLI and when I use embedded navigation it doesn't load a page, it instead redirects to an enable cookies url, then redirects to auth and loads the initial default view again once complete.

Expected behavior

What do you think should happen?

I would expect that when clicking a navigation item it would load a page from the Next.js app.

Actual behavior

What actually happens?

I created a brand new Shopify app using the CLI. I duplicated pages/index.js to pages/sample.js. I then went to App Setup > Embedded app > Configure (Navigation) inbox the partner dashboard. I added two items, Dashboard > / and Sample > /sample.

The navigation appears as expected, when I click on the "Sample" link I would expect it to load the sample page from Next.js. However it seems to redirect to an enable cookies url, then redirects to auth and loads the initial default view again once complete.

Steps to reproduce the problem

  1. Create a new app via the CLI
  2. Add a new page to Next.js
  3. Add navigation in the partner dashboard and then try and open link to new page

Checklist

  • [ ] I have described this issue in a way that is actionable (if possible)

stevepsharpe avatar Apr 28 '21 18:04 stevepsharpe

Same here. Any helps?

liqueflies avatar May 18 '21 15:05 liqueflies

Same here, any solution to this?

stazap-capsule avatar Jun 07 '21 12:06 stazap-capsule

On my side if I use Firefox, I don't get this annoying "Enable cookies" message, but it still redirects to initial default view.

FrEaKmAn avatar Jun 14 '21 07:06 FrEaKmAn

This issue is stale because it has been open for 90 days with no activity. It will be closed if no further action occurs in 14 days.

github-actions[bot] avatar Oct 06 '22 02:10 github-actions[bot]

We are closing this issue because it has been inactive for a few months. This probably means that it is not reproducible or it has been fixed in a newer version. If it’s an enhancement and hasn’t been taken on since it was submitted, then it seems other issues have taken priority.

If you still encounter this issue with the latest stable version, please reopen using the issue template. You can also contribute directly by submitting a pull request– see the CONTRIBUTING.md file for guidelines

Thank you!

github-actions[bot] avatar Oct 20 '22 02:10 github-actions[bot]