Browser Widget and Twitter on iOS 13

[Prothero@earthlearning]

FYI,
I have bitdefender on my Apple Laptop and when I post an entry to my mysql database on my server, I get a security alert from bitdefender (Catalina latest update and latest LC distro, LC 9.6.1). So, I wonder if the person with the problem might have some kind of anti-virus software installed.

Bill

William Prothero
http://es.earthednet.org

> On Aug 13, 2020, at 9:05 AM, Ralph DiMola via use-livecode <use-livecode at lists.runrev.com> wrote:
> 
> Thanks Mark.
> 
> I searched all stacks for "userAgent" and it did not exist. After I got some
> more feedback it is working on iOS 13 iPhones but not on an iOS 13 iPad. So
> far this iPad is the only one with this issue. The user tried in Safari on
> the iPad and did not get the message.
> 
> LC 9.6.0 
> OSX 10.14.6 
> Xcode 11.3.1
> 
> Ralph DiMola
> IT Director
> Evergreen Information Services
> rdimola at evergreeninfo.net
> 
> 
> -----Original Message-----
> From: use-livecode [mailto:use-livecode-bounces at lists.runrev.com] On Behalf
> Of Mark Waddingham via use-livecode
> Sent: Thursday, August 13, 2020 11:16 AM
> To: How to use LiveCode
> Cc: Mark Waddingham
> Subject: Re: Browser Widget and Twitter on iOS 13
> 
>>> On 2020-08-13 13:46, Ralph DiMola via use-livecode wrote:
>> When accessing Twitter via the Browser Widget on iOS 13 I get this
>> error message==> "This browser is no longer supported. Please switch
>> to a supported browser or disable the extension which masks you
>> browser to continue using twitter.com". Is there a widget setting I
>> can change to eliminate this? It works on Android and iOS 12. This is
>> from the first tester. Could there be a iOS devices setting that this
>> user inadvertently changed that caused this? I'm waiting for other
>> testers but wanted to get on top of this. Any ideas?
> 
> Hmmm - the wording "This browser is no longer supported. Please switch to a
> supported browser or disable the extension which masks you browser to
> continue using twitter.com" suggests that twitter.com is using the userAgent
> string to determine access.
> 
> I'm pretty sure the old UIWebView (which we replaced with WKWebView in
> 9.6) didn't support a custom user agent string - but the new WKWebView one
> does.
> 
> Are you setting `the userAgent` property of the browser widget anywhere?
> 
> Of course, this wouldn't explain why it works in iOS12 / Android if this is
> the problem...
> 
> Warmest Regards,
> 
> Mark.
> 
> --
> Mark Waddingham ~ mark at livecode.com ~ http://www.livecode.com/
> LiveCode: Everyone can create apps
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
> 
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode