A client’s app link worked perfectly in Safari. Same exact link, same exact code — completely blocked inside Twitter’s in-app browser. It looked like a simple bug. It wasn’t, once we broke down what was actually happening.

Two steps that look like one

There are two completely different actions happening back to back, even though they look like a single click to the user:

1. Twitter’s in-app browser loads the web page fine — HTML, layout, the button, all of it displays correctly.
2. That button then asks the phone’s operating system to switch over to a different app entirely.

Step 1 works. Step 2 gets blocked — not by the website’s code, but by Twitter’s browser specifically.

Why the restriction exists

Loading a web page is a harmless, well-understood action — it just displays content. Jumping to another app is a fundamentally different category of action, one that’s commonly abused for forced installs and scam redirects. So platforms like Twitter let any page load freely inside their in-app browser, but specifically lock down app-switching, regardless of which app is asking.

Think of it like a room with windows but no door. You can see everything happening inside clearly — that part’s open. But the moment you try to actually walk through to another room, that door’s locked, even with the windows wide open.

“Debugging isn’t always about fixing broken code. Sometimes it’s about realizing the code isn’t broken at all — it’s working exactly as intended, just running into a wall someone else built on purpose.”

How we actually fixed it

Once we understood it wasn’t a code defect but a platform-level restriction, the fix stopped being about the link itself and started being about detecting the environment: identifying when the page is running inside a restricted in-app browser, and giving the user a clear, explicit path out — an “open in browser” prompt — rather than a silently failing button. We handled this specifically for Facebook’s and Twitter/X’s in-app browsers, since each has slightly different restrictions and needs its own detection logic.

The takeaway

If a link works everywhere except inside one specific app’s browser, the first question isn’t “what’s wrong with our code” — it’s “what is this specific browser deliberately restricting.” Most of the time, in-app browser problems aren’t bugs to fix. They’re platform boundaries to design around.