Replitmobile

Mobile Safari Back Button Breaking SPA on Replit

The back button on iOS Safari breaks your single-page app hosted on Replit. Pages show stale content or blank screens. Learn how to fix SPA navigation.

3 min read Updated Applies to Replit

What is going on

Users on iOS Safari report that pressing the back button in your single-page application shows a blank page, stale content from cache, or navigates completely out of your app. The browser's back/forward navigation does not work correctly with your client-side routing.

This is a notorious issue with SPAs on Mobile Safari specifically. Safari aggressively uses its back-forward cache (bfcache), which restores a frozen snapshot of the previous page instead of re-executing JavaScript. This means your React, Vue, or Angular app gets restored in a stale state where event listeners are dead and data is outdated.

The issue is exacerbated on Replit because AI-generated SPAs rarely handle Safari's bfcache behavior, and the Replit preview does not use Safari's rendering engine so the problem is invisible during development.

Error messages you might see

No error messages — page appears blank or shows stale content
JavaScript event listeners stop responding after back navigation
Page shows old data that does not update
App appears frozen after pressing back button

Common causes

  • Safari's bfcache — Safari restores a frozen page snapshot instead of re-rendering, leaving the app in a broken state
  • Missing popstate handler — the SPA does not listen for browser navigation events
  • History API misuse — pushState and replaceState are called incorrectly, confusing the browser's history stack
  • No scroll position restoration — the page scrolls to the wrong position after back navigation
  • Hash vs history mode conflict — the router mode does not match what Safari expects

How to fix it

  1. Handle the pageshow event — listen for window's pageshow event and check event.persisted to detect bfcache restoration, then force a re-render
  2. Add a popstate event listener — ensure your router handles browser back/forward navigation by listening for popstate events
  3. Disable bfcache if needed — add an unload event listener (even an empty one) to prevent Safari from caching the page, though this hurts performance
  4. Use router's scroll behavior — configure your SPA router to handle scroll position restoration on navigation
  5. Test on actual iOS Safari — use a real iPhone or BrowserStack to test back button behavior, since Chrome DevTools cannot simulate this

Getting help takes about a minute

No hiring, no back and forth. A real person looks at your app.

  1. 1

    Describe it

    Tell us what you need in plain words. You don't have to be technical or have an account to start.

  2. 2

    Free 15-minute call

    A verified developer calls you. Many tasks are sorted right there, and it costs nothing.

  3. 3

    Pay after you approve

    If there is more to do, you get one fixed price up front. You pay only once you are happy.

Get help

Real people, reviewed by hand

Developers who do this every day

Every developer is approved by our team before they can take a task. Describe yours and the first one who is free picks it up.

Get help

Questions

Why does back button work in Chrome but not Safari?

Safari has a more aggressive back-forward cache (bfcache) that freezes and restores entire page states. Chrome is more conservative and typically re-executes JavaScript. Your SPA needs to handle Safari's bfcache specifically.

Can I disable Safari's back-forward cache?

Adding an unload event listener prevents bfcache, but this is considered a last resort because it degrades performance. Better to handle the pageshow event and refresh your app state when persisted is true.

How do I test this without an iPhone?

Use BrowserStack or Sauce Labs for cloud-based real device testing. If you have a Mac, use the iOS Simulator included with Xcode. Chrome DevTools device mode does not replicate Safari's bfcache behavior.

Keep reading

Can't fix it yourself?
Real developers can help.

Get help