Link not opening in Facebook

Of every in-app browser we route taps out of, Facebook's is the most stubborn. It is also the one that changed most recently, in a way that quietly breaks older detection code.

6 August 2026 by PAD team

The failure

Tap a store link inside Facebook on an iPhone and the App Store usually does not open. Apple redirects apps.apple.com to the itms-appss:// scheme, and Facebook's WebView will not pass that scheme to another application. Navigation stops, the page stays blank, and the visitor leaves.

The same link pasted into Safari works every time, which is why this can survive months of campaigns without anyone identifying it.

Facebook is stricter than Instagram

Both apps belong to Meta and both open links in a WebView, but they behave differently. Instagram ships instagram://extbrowser, an undocumented scheme that hands a URL to the system browser. Facebook has no working equivalent, so there is one fewer route out.

Measured on 6,200 taps routed between 3 and 6 August 2026, Facebook needed the manual fallback button several times more often than Instagram did. In practice you should plan for the button rather than treat it as an edge case.

What changed in iOS 26

Facebook used to mark its WebView in the user agent with FBAV or FBAN. Since iOS 26, some builds have stopped doing that, and the string looks like ordinary Safari.

Detection written before that change now classifies those visits as a real browser, sends them the plain store link, and they die on the blank page. If your routing has an if FBAN branch and nothing else, it is currently misrouting a share of Facebook traffic.

There is no replacement marker. What is left is circumstantial evidence, combined rather than trusted individually, and covered in the detection write-up.

What still works

Request the store scheme directly rather than waiting for Apple to redirect you into it. Some builds refuse the https URL and pass the custom scheme through:

itms-appss://apps.apple.com/app/id123456789

Then show a manual button quickly. On the strict platforms we render it after roughly a second and a half, and about half the people who see it use it. A spinner that runs for four seconds converts worse than a button that appears in one.

Ads make it expensive

App install campaigns are unaffected, because Meta opens the store natively from the Install button with no browser in between. Traffic, engagement and conversion campaigns all route through the WebView, and those are exactly the objectives you are pushed into when there is a landing page or a quiz before the download. Details in the write-up on paid traffic.