RE: Browser Widget and Twitter on iOS 13

2020-08-17 Thread Ralph DiMola via use-livecode
I was thinking of doing it just for Twitter but if other sites become stricter 
I did not want to have to release a new app. I could have done an OTA update of 
sites that needed this userAgent but I opted for the simple solution.

Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net

-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of 
Linda Miller via use-livecode
Sent: Saturday, August 15, 2020 2:53 PM
To: use-livecode@lists.runrev.com
Cc: Linda Miller
Subject: RE: Browser Widget and Twitter on iOS 13

Why not check if it is going to a URL that contains “twitter.com” and feed the 
correct user agent prior to going to the website since it is only a twitter 
issue?

Linda

> On Aug 15, 2020, at 10:00 AM, use-livecode-requ...@lists.runrev.com wrote:
> 
> RE: Browser Widget and Twitter on iOS 13

___
use-livecode mailing list
use-livecode@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@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


RE: Browser Widget and Twitter on iOS 13

2020-08-15 Thread Linda Miller via use-livecode
Why not check if it is going to a URL that contains “twitter.com” and feed the 
correct user agent prior to going to the website since it is only a twitter 
issue?

Linda

> On Aug 15, 2020, at 10:00 AM, use-livecode-requ...@lists.runrev.com wrote:
> 
> RE: Browser Widget and Twitter on iOS 13

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Browser Widget and Twitter on iOS 13

2020-08-15 Thread Jim Lambert via use-livecode
Ralph,

Thanks for that switch statement.

Jim Lambert

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


RE: Browser Widget and Twitter on iOS 13

2020-08-14 Thread Ralph DiMola via use-livecode
There is a song to be written for
https://webaim.org/blog/user-agent-string-history/. It may have multiple
time signatures... but I digress. Here's the code that's working for me:


if the environment = "mobile" and the platform = "iphone" and the machine
contains "iPad" then -- one can never be too careful

  switch

 case the systemversion begins with "12" -- iOS 12

set the userAgent of widget "BrowserW" to "Mozilla/5.0 (iPad;
CPU OS 12_4_8 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko)
Version/12.1.2 Mobile/15E148 Safari/604.1"

break

 case the systemversion begins with "13" -- iOS 13

set the userAgent of widget "BrowserW" to "Mozilla/5.0
(Macintosh; Intel Mac OS X 10_15_4) AppleWebKit/605.1.15 (KHTML, like Gecko)
Version/13.1.1 Safari/605.1.15"

break

 default -- everybody else. This could get me into trouble later.
Maybe default should be deleted?  REVISIT

set the userAgent of widget "BrowserW" to "Mozilla/5.0 (iPad;
CPU OS 12_4_8 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko)
Version/12.1.2 Mobile/15E148 Safari/604.1"

  end switch

   end if


Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net


-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf
Of Mark Wieder via use-livecode
Sent: Friday, August 14, 2020 7:17 PM
To: Ralph DiMola via use-livecode
Cc: Mark Wieder
Subject: Re: Browser Widget and Twitter on iOS 13

On 8/14/20 2:54 PM, Ralph DiMola via use-livecode wrote:
> Mark/Panos,
> 
> Thanks for all your help, this worked like a charm! I got the 
> userAgent from a v12 iPad and v13 iPad. For any other iPad OS version 
> I use the v13 version.

Just curious... what userAgent string worked for you?

--
  Mark Wieder
  ahsoftw...@gmail.com

___
use-livecode mailing list
use-livecode@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@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Browser Widget and Twitter on iOS 13

2020-08-14 Thread Mark Wieder via use-livecode

On 8/14/20 2:54 PM, Ralph DiMola via use-livecode wrote:

Mark/Panos,

Thanks for all your help, this worked like a charm! I got the userAgent from
a v12 iPad and v13 iPad. For any other iPad OS version I use the v13
version.


Just curious... what userAgent string worked for you?

--
 Mark Wieder
 ahsoftw...@gmail.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


RE: Browser Widget and Twitter on iOS 13

2020-08-14 Thread Ralph DiMola via use-livecode
Mark/Panos,

Thanks for all your help, this worked like a charm! I got the userAgent from
a v12 iPad and v13 iPad. For any other iPad OS version I use the v13
version.

Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net


-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf
Of Mark Waddingham via use-livecode
Sent: Friday, August 14, 2020 9:12 AM
To: How to use LiveCode
Cc: Mark Waddingham
Subject: Re: Browser Widget and Twitter on iOS 13

On 2020-08-14 14:01, Mark Waddingham via use-livecode wrote:
> On 2020-08-14 13:31, Ralph DiMola via use-livecode wrote:
>> Should I use the userAgent globally for all browser widget http(s) 
>> requests on platform = iphone?
> 
> Isn't the issue on iPad?

Hah - ignore this - I forgot to edit it when I realized 'the platform' 
returns iPhone (its the machine which distinguishes between iPad and
iPhone).

Whether to do it for all web-requests then I'm not sure - this is
twitter.com related thing as far as I can see.

It shouldn't do any harm to use the same useragent for all requests though
(although you might want to check if iPad latest iOS from Safari is
different from iPhone latest from Safari and switch on the machine if so).

I'd recommend removing this mitigation if/when twitter.com starts behaving
normally again though as you don't want to have to keep that up to date lest
it cause problems for other websites.

Warmest Regards,

Mark.

--
Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/
LiveCode: Everyone can create apps

___
use-livecode mailing list
use-livecode@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@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Browser Widget and Twitter on iOS 13

2020-08-14 Thread Mark Waddingham via use-livecode

On 2020-08-14 14:01, Mark Waddingham via use-livecode wrote:

On 2020-08-14 13:31, Ralph DiMola via use-livecode wrote:
Should I use the userAgent globally for all browser widget http(s) 
requests

on platform = iphone?


Isn't the issue on iPad?


Hah - ignore this - I forgot to edit it when I realized 'the platform' 
returns iPhone (its the machine which distinguishes between iPad and 
iPhone).


Whether to do it for all web-requests then I'm not sure - this is 
twitter.com related thing as far as I can see.


It shouldn't do any harm to use the same useragent for all requests 
though (although you might want to check if iPad latest iOS from Safari 
is different from iPhone latest from Safari and switch on the machine if 
so).


I'd recommend removing this mitigation if/when twitter.com starts 
behaving normally again though as you don't want to have to keep that up 
to date lest it cause problems for other websites.


Warmest Regards,

Mark.

--
Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/
LiveCode: Everyone can create apps

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Browser Widget and Twitter on iOS 13

2020-08-14 Thread Mark Waddingham via use-livecode

On 2020-08-14 13:31, Ralph DiMola via use-livecode wrote:

Thanks Panos and Mark!

So... to recap..
1) get the userAgent in Safari on my 10.14.6 Mac
2) in App (If the platform="iphone" then set userAgent to this value).


Pretty much - although I recommend not using the userAgent string from a 
mac. Instead, get the userAgent string from an iPad which allows you to 
access twitter.com through the browser widget. Just in case anything 
mac-ish in the user agent string causes twitter.com to do something 
different (e.g. specialize for desktop rather than mobile).


Should I use the userAgent globally for all browser widget http(s) 
requests

on platform = iphone?


Isn't the issue on iPad?


Will this affect any other tsNet functions?


The browser widget uses WKWebView which uses system HTTP functionality 
so tsNet isn't involved.



Should it be reset back to empty for any reason?


I can't think of one.


Should I file a bug report?


No - this isn't anything we can do anything about. I strongly suspect 
the iPad issue your client is having is one of;
  - it isn't running the very latest iOS version, and Twitter is 
blocking the default userAgent string for that version and older ones 
which come from WKWebView
  - Twitter's (new?) block-list isn't actually correct and not taking 
into account enough variations (e.g. those coming from WKWebView).


Warmest Regards,

Mark.

--
Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/
LiveCode: Everyone can create apps

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


RE: Browser Widget and Twitter on iOS 13

2020-08-14 Thread Ralph DiMola via use-livecode
Thanks Panos and Mark!

So... to recap..
1) get the userAgent in Safari on my 10.14.6 Mac
2) in App (If the platform="iphone" then set userAgent to this value).

Should I use the userAgent globally for all browser widget http(s) requests
on platform = iphone?
Will this affect any other tsNet functions?
Should it be reset back to empty for any reason?

Should I file a bug report?

Have a good weekend.
Thanks again.

Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net

-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf
Of panagiotis merakos via use-livecode
Sent: Friday, August 14, 2020 3:40 AM
To: How to use LiveCode
Cc: panagiotis merakos
Subject: Re: Browser Widget and Twitter on iOS 13

Hello all,

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

https://help.twitter.com/en/using-twitter/twitter-supported-browsers

https://stackoverflow.com/questions/63081729/when-using-r-curl-to-download-a
-twitter-page-the-page-downloaded-is-this-brows

https://stackoverflow.com/questions/62967532/ipad-wkwebview-in-case-of-ipad-
i-am-getting-this-browser-is-no-longer-supporte

I get the same warning ("this browser is no longer supported .." ) when I
try to visit https://twitter.com 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 (
https://www.whatismybrowser.com/detect/what-is-my-user-agent) with Safari to
see what an accepted user-agent is, and then set the "userAgent" of the
browser widget to this value.

Kind regards,
Panos
--



On Thu, 13 Aug 2020 at 20:36, Mark Waddingham via use-livecode <
use-livecode@lists.runrev.com> 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:
>
> https://www.whatismybrowser.com/detect/what-is-my-user-agent
>
> 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 ~ m...@livecode.com ~ http://www.livecode.com/
> LiveCode: Everyone can create apps
>
> ___
> use-livecode mailing list
> use-livecode@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@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@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Browser Widget and Twitter on iOS 13

2020-08-14 Thread panagiotis merakos via use-livecode
Hello all,

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

https://help.twitter.com/en/using-twitter/twitter-supported-browsers

https://stackoverflow.com/questions/63081729/when-using-r-curl-to-download-a-twitter-page-the-page-downloaded-is-this-brows

https://stackoverflow.com/questions/62967532/ipad-wkwebview-in-case-of-ipad-i-am-getting-this-browser-is-no-longer-supporte

I get the same warning ("this browser is no longer supported .." ) when I
try to visit https://twitter.com 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 (
https://www.whatismybrowser.com/detect/what-is-my-user-agent) with Safari
to see what an accepted user-agent is, and then set the "userAgent" of the
browser widget to this value.

Kind regards,
Panos
--



On Thu, 13 Aug 2020 at 20:36, Mark Waddingham via use-livecode <
use-livecode@lists.runrev.com> 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:
>
> https://www.whatismybrowser.com/detect/what-is-my-user-agent
>
> 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 ~ m...@livecode.com ~ http://www.livecode.com/
> LiveCode: Everyone can create apps
>
> ___
> use-livecode mailing list
> use-livecode@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@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Browser Widget and Twitter on iOS 13

2020-08-13 Thread Mark Waddingham via use-livecode

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:


   https://www.whatismybrowser.com/detect/what-is-my-user-agent

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 ~ m...@livecode.com ~ http://www.livecode.com/
LiveCode: Everyone can create apps

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


RE: Browser Widget and Twitter on iOS 13

2020-08-13 Thread Ralph DiMola via use-livecode
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)

Odd indeed but I(well Panos) just found a iPad oddity that a couple of iPad
Mini models running 12.x would only load local web pages if they were in the
temp folder. So this unified iOS SW/HW thing is not 100% yet.

Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net


-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf
Of Mark Waddingham via use-livecode
Sent: Thursday, August 13, 2020 1:09 PM
To: How to use LiveCode
Cc: Mark Waddingham
Subject: Re: Browser Widget and Twitter on iOS 13

On 2020-08-13 17:06, Ralph DiMola via use-livecode 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.

So that is just odd - it might be worth checking that said iPad has the
latest version of iOS13...

There's a small chance that Apple has fixed something in WKWebView on
iOS13 in some .x increment, and Twitter has blocked the versions before (via
userAgent).

Safari and WKWebView are not the same thing (I think Safari might use its
own private version of WebKit under the hood - although I'm not 100% sure
about that) so the Safari comparison might not be relevant in this case.

Warmest Regards,

Mark.

--
Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/
LiveCode: Everyone can create apps

___
use-livecode mailing list
use-livecode@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@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Browser Widget and Twitter on iOS 13

2020-08-13 Thread Mark Waddingham via use-livecode

On 2020-08-13 17:06, Ralph DiMola via use-livecode 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.


So that is just odd - it might be worth checking that said iPad has the 
latest version of iOS13...


There's a small chance that Apple has fixed something in WKWebView on 
iOS13 in some .x increment, and Twitter has blocked the versions before 
(via userAgent).


Safari and WKWebView are not the same thing (I think Safari might use 
its own private version of WebKit under the hood - although I'm not 100% 
sure about that) so the Safari comparison might not be relevant in this 
case.


Warmest Regards,

Mark.

--
Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/
LiveCode: Everyone can create apps

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Browser Widget and Twitter on iOS 13

2020-08-13 Thread Prothero@earthlearning via use-livecode
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 
>  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
> rdim...@evergreeninfo.net
> 
> 
> -Original Message-
> From: use-livecode [mailto:use-livecode-boun...@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 ~ m...@livecode.com ~ http://www.livecode.com/
> LiveCode: Everyone can create apps
> 
> ___
> use-livecode mailing list
> use-livecode@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@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@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


RE: Browser Widget and Twitter on iOS 13

2020-08-13 Thread Ralph DiMola via use-livecode
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
rdim...@evergreeninfo.net


-Original Message-
From: use-livecode [mailto:use-livecode-boun...@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 ~ m...@livecode.com ~ http://www.livecode.com/
LiveCode: Everyone can create apps

___
use-livecode mailing list
use-livecode@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@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Browser Widget and Twitter on iOS 13

2020-08-13 Thread Mark Waddingham via use-livecode

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 ~ m...@livecode.com ~ http://www.livecode.com/
LiveCode: Everyone can create apps

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Browser Widget and Twitter on iOS 13

2020-08-13 Thread Ralph DiMola via use-livecode
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?

Thanks.

Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode