# Glide Pages + Facebook Android: stuck in FB in-app browser

**URL:** <https://community.glideapps.com/t/glide-pages-facebook-android-stuck-in-fb-in-app-browser/85770>\
**Category:** Ask for Help\
**Created:** [December 22, 2025, 9:55am UTC](https://community.glideapps.com/t/glide-pages-facebook-android-stuck-in-fb-in-app-browser/85770 "2025-12-22T09:55:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Miroslav\_Madaric](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/miroslav_madaric/32/20852_2.png) [@Miroslav\_Madaric](https://community.glideapps.com/u/Miroslav_Madaric)\
**Post date:** [December 22, 2025, 9:55am UTC](https://community.glideapps.com/t/glide-pages-facebook-android-stuck-in-fb-in-app-browser/85770/1 "2025-12-22T09:55:10Z")

</div>

Hello Glide team & community,

I’m facing a serious UX issue with **Glide Pages** when users come from **Facebook on Android**.

**Problem:**  
When a user clicks a direct link like  
`https://nasilje.glide.page/`  
inside the Facebook Android app, Facebook wraps it into  
`https://l.facebook.com/l.php?...`  
and opens it **only inside Facebook’s in-app WebView**.

As a result:

- The Glide Page does **not** open in Chrome

- The user never reaches the “real” app context

- No deep-linking / PWA handoff happens

- Many users (especially non-technical) abandon immediately

Even though the URL is correct, from the user’s perspective _“the app never opens”_.

**Questions:**

1. Is there any **official or recommended Glide workaround** for Facebook/Instagram WebView on Android?

2. Is there a **reliable way to force or strongly encourage opening in an external browser** (Chrome) from a Glide Page?

3. Does Glide have a **documented method to detect Meta WebView** (Facebook / Instagram user agents) to show a dedicated “open in browser” gate screen?

4. Is there any **difference in behavior** between Glide App vs Glide Page in this scenario?

5. Are there known limitations acknowledged by Glide regarding Meta platforms?

I understand Facebook controls their WebView — I’m not looking for miracles — but I’d like to know **what Glide officially recommends as best practice** , and what is simply impossible by design.

Thanks in advance for any concrete guidance or references.

---

<div class="post-metadata">

**Author:** ![MegannLock](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/megannlock/32/19680_2.png) [@MegannLock](https://community.glideapps.com/u/MegannLock)\
**Post date:** [December 22, 2025, 12:35pm UTC](https://community.glideapps.com/t/glide-pages-facebook-android-stuck-in-fb-in-app-browser/85770/2 "2025-12-22T12:35:29Z")

</div>

No difference between Glide App/Glide Pages. That distinction is not related to the issue you’re having. Back in 2021 or so, I was experiencing same issue on one of the first iterations of Glide Apps (before pages existed).

I’m not sure what Glide’s official recommendation is, but here’s what I do for quick fix (I think you can use specific link sharing tools to bypass FB in-app browser):

Instead of sharing a Glide link on FB, I just share an image with my custom domain & catchy instructions to open your browser & Go to “customdomain.app” to get started!