search

vercel / next.js

The React Framework
https://nextjs.org
MIT License
126.87k stars 26.97k forks source link

ios built in browser navigation problems #11746

Closed xopowuu closed 1 year ago

xopowuu commented 4 years ago

Bug report

Describe the bug

Browser's back and forward buttons disabled, when surfing next.js app through in app browser (like instagram)

To Reproduce

With instagram app add nextjs.org url to your profile, then open it and navigate pages with links

Expected behavior

Browser navigation buttons are active

System information

Additional context

bug is gone when back to previous page with swipe

timneutkens commented 4 years ago

Can you try upgrading to next@canary?

xopowuu commented 4 years ago

Can you try upgrading to next@canary?

upgrading to 9.3.5-canary.5 didn't help

developit commented 4 years ago

Did this ever work? The most obvious answer would be that Instagram's webview on iOS doesn't take client-side navigations into account, so it always sees a history of length 0.

Seems worth checking with another site that does client-side routing.

xopowuu commented 4 years ago

Did this ever work? The most obvious answer would be that Instagram's webview on iOS doesn't take client-side navigations into account, so it always sees a history of length 0.

Seems worth checking with another site that does client-side routing.

history works, you can "unlock" it with left swipe

xopowuu commented 4 years ago

temporary solution is to reload page after first route changing

daryl-z commented 4 years ago

Router.replace throw invalid href error in iOS9. next.js 9.3.1.

github-actions[bot] commented 1 year ago

Please verify that your issue can be recreated with next@canary.

Why was this issue marked with the please verify canary label?

We noticed the provided reproduction was using an older version of Next.js, instead of canary.

The canary version of Next.js ships daily and includes all features and fixes that have not been released to the stable version yet. You can think of canary as a public beta. Some issues may already be fixed in the canary version, so please verify that your issue reproduces by running npm install next@canary and test it in your project, using your reproduction steps.

If the issue does not reproduce with the canary version, then it has already been fixed and this issue can be closed.

How can I quickly verify if my issue has been fixed in canary?

The safest way is to install next@canary in your project and test it, but you can also search through closed Next.js issues for duplicates or check the Next.js releases.

My issue has been open for a long time, why do I need to verify canary now?

Next.js does not backport bug fixes to older versions of Next.js. Instead, we are trying to introduce only a minimal amount of breaking changes between major releases.

What happens if I don't verify against the canary version of Next.js?

An issue with the please verify canary that receives no meaningful activity (e.g. new comments that acknowledge verification against canary) will be automatically closed and locked after 30 days.

If your issue has not been resolved in that time and it has been closed/locked, please open a new issue, with the required reproduction, using next@canary.

I did not open this issue, but it is relevant to me, what can I do to help?

Anyone experiencing the same issue is welcome to provide a minimal reproduction following the above steps. Furthermore, you can upvote the issue using the :+1: reaction on the topmost comment (please do not comment "I have the same issue" without repro steps). Then, we can sort issues by votes to prioritize.

I think my reproduction is good enough, why aren't you looking into it quicker?

We look into every Next.js issue and constantly monitor open issues for new comments.

However, sometimes we might miss one or two due to the popularity/high traffic of the repository. We apologize, and kindly ask you to refrain from tagging core maintainers, as that will usually not result in increased priority.

Upvoting issues to show your interest will help us prioritize and address them as quickly as possible. That said, every issue is important to us, and if an issue gets closed by accident, we encourage you to open a new one linking to the old issue and we will look into it.

Useful Resources

balazsorban44 commented 1 year ago

This issue has been automatically closed because it wasn't verified against next@canary. If you think it was closed by accident, please leave a comment. If you are running into a similar issue, please open a new issue with a reproduction. Thank you.

github-actions[bot] commented 1 year ago

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.