# PWA launched via webapp:// always loads homepage, not intended path

**URL:** https://meta.discourse.org/t/pwa-launched-via-webapp-always-loads-homepage-not-intended-path/375036
**Category:** Feature
**Tags:** mobile, pwa, ios
**Created:** [July 21, 2025, 8:33am UTC](https://meta.discourse.org/t/pwa-launched-via-webapp-always-loads-homepage-not-intended-path/375036 "2025-07-21T08:33:38Z")
**Posts on this page:** 1
**Showing post:** 1

<div class="post-metadata">

### Author: ![Ethsim2](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ethsim2/32/522255_2.png) [@Ethsim2](https://meta.discourse.org/u/Ethsim2)
#### Post date: [July 21, 2025, 8:33am UTC](https://meta.discourse.org/t/pwa-launched-via-webapp-always-loads-homepage-not-intended-path/375036/1 "2025-07-21T08:33:38Z")

</div>

On iOS (16.4+), Safari PWA already on homepage, it’s now possible to open installed PWAs using the webapp:// URL scheme from Shortcuts or other apps.

Example:

```plaintext
webapp://myforum.example.com/t/topic-title/123

```

This correctly opens the Discourse PWA shell — however, the path is ignored, and it always loads the homepage instead.

### Expected behavior:

The Discourse PWA should respect the incoming window.location.pathname on cold start, and load that route directly.

### Actual behavior:

Only / is rendered, even though the requested URL included a path.

This makes deep linking into the PWA impossible (unless it was already running), which limits usefulness with iOS Shortcuts, widgets, NFC automations, etc.

Can this be fixed by adjusting Service Worker scope or initial routing behavior in the PWA shell?

Would love to see full support for deep linking via PWA!

---

_[View the full topic](https://meta.discourse.org/t/pwa-launched-via-webapp-always-loads-homepage-not-intended-path/375036)._