I’m growing a Progressive Internet App utilizing Subsequent.js and testing on iOS Safari model 26.2.
After I add the app to the house display screen from the touchdown web page /, the app runs appropriately in standalone mode and no Safari browser controls are seen throughout navigation.
Nonetheless, if I navigate to /dashboard, faucet Add to Dwelling Display, after which navigate to /messenger, the Safari UI controls briefly seem on the prime and backside of the display screen.
This conduct solely happens when the app is put in from /dashboard. Putting in it from the basis route doesn’t set off the difficulty.
What I’ve verified
• The app is put in by way of Add to Dwelling Display
• show: standalone is about within the net app manifest
• Navigation makes use of Subsequent.js client-side routing
• The problem solely happens on iOS Safari 26.2
Query
Why does Safari present browser controls after navigation when the PWA is put in from a non-root route, and the way can I make sure the app persistently stays in standalone mode whatever the set up route?
