Browser Widget and Twitter on iOS 13

panagiotis merakos merakosp at
Fri Aug 14 03:39:47 EDT 2020

Hello all,

Definitely this is related to the user-agent. It seems twitter recently has
become stricter on this:

I get the same warning ("this browser is no longer supported .." ) when I
try to visit from a browser widget on my Mac (10.14.6)
with LC 9.6.0.

I was able to get rid of the warning by visiting the page Mark posted ( with Safari
to see what an accepted user-agent is, and then set the "userAgent" of the
browser widget to this value.

Kind regards,

On Thu, 13 Aug 2020 at 20:36, Mark Waddingham via use-livecode <
use-livecode at> wrote:

> On 2020-08-13 18:30, Ralph DiMola via use-livecode wrote:
> > That tester has both iPhone and iPad and I know there both running the
> > same
> > version of iOS. iPhone doesn't get the message but the iPad does. I
> > will
> > find out if there both up to the latest 13.x.x. (it flew out of my head
> > after I heard they were running the same version)
> So I'm pretty sure this has to be the userAgent string which any HTTP
> client sends up as a header (User-Agent:?) as I don't think any other
> browser-specific/OS-specific/device-specific information is transmitted.
> If you can send the user an app with just a browser widget in it where
> they can visit:
> On both the iPad and iPhone they have then at least it will show if
> there *is* a difference between the two devices in terms of what
> WKWebView is sending (can also compare with Safari on the devices too
> which would either confirm or deny my suspicion about Safari not being a
> wrapped WKWebView).
> Warmest Regards,
> Mark.
> --
> Mark Waddingham ~ mark at ~
> LiveCode: Everyone can create apps
> _______________________________________________
> use-livecode mailing list
> use-livecode at
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:

More information about the use-livecode mailing list