When I load google page with WKWebView I have noticed that google label is not sharp. But in Safari it is good.
WKWebView
Safari
So, how can I make it sharp like in Safari ?
I have found the solution. Just set customUserAgent :
webView.customUserAgent = "Mozilla/5.0 (iPhone; CPU iPhone OS 11_2_5 like Mac OS X) AppleWebKit/604.5.6 (KHTML, like Gecko) Version/11.0 Mobile/15D60 Safari/604.1"
Related
I am trying to open jitsi website on a webview,
if I open it in the Safari builtin browser, it works fine.
if I open it in a Webview inside Xamarin application, it said "It looks like you're using a browser we don't fully support"
is not it supposed the Webview uses Safari by default?
then, why Safari works, while the Webview is not supported?
Is there any work around to open the Jitsi inside the application Webview?
Opening an external browser is not an option,
------------ UPDATE (1) -----------------
According to Jason advice, I set the UserAgent:
1- I used my xamarin webview and navigate to:
whatsmyua.info
My UserAgent was "Mozilla/5.0 (iPhone; CPU iPhone OS 15_4 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148"
2- I used iPhone Safari and navigate to:
whatsmyua.info
My UserAgent was "Mozilla/5.0 (iPhone; CPU iPhone OS 15_5 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.5 Mobile/15E148 Safari/604.1"
3- So I set the xamarin webview UserAgent in code behind
wkWebView.CustomUserAgent = "Mozilla/5.0 (iPhone; CPU iPhone OS 15_5 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.5 Mobile/15E148 Safari/604.1";
4- I check again using "whatsmyua.info", and everythign is ok, UserAgent successfully changed.
5- I tried to open "jitsi website", but nothing changed,
still gives me "It looks like you're using a browser we don't fully support"
Any Ideas, please?
===================== Update (2) ========================
I used UserAgent "Mozilla/5.0 (X11; Linux i586; rv:31.0) Gecko/20100101 Firefox/31.0",
Now it is working,
But I do not why it did not work when I used the same UserAgent like Safari!
Anyway, I am happy
Thanks (Jason)
According to Jason advice, I set the UserAgent:
1- I used my xamarin webview and navigate to:
whatsmyua.info
My UserAgent was "Mozilla/5.0 (iPhone; CPU iPhone OS 15_4 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148"
2- I used iPhone Safari and navigate to:
whatsmyua.info
My UserAgent was "Mozilla/5.0 (iPhone; CPU iPhone OS 15_5 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.5 Mobile/15E148 Safari/604.1"
3- So I set the xamarin webview UserAgent in code behind wkWebView.CustomUserAgent = "Mozilla/5.0 (iPhone; CPU iPhone OS 15_5 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.5 Mobile/15E148 Safari/604.1";
4- I check again using "whatsmyua.info", and everythign is ok, UserAgent successfully changed.
5- I tried to open "jitsi website", but nothing changed, still gives me "It looks like you're using a browser we don't fully support"
===================== Final Working Solution ========================
I used this UserAgent:
wkWebView.CustomUserAgent = "Mozilla/5.0 (X11; Linux i586; rv:31.0) Gecko/20100101 Firefox/31.0";
Now it is working!
Anyway, I am happy
Thanks (Jason)
I'm working on a live video session app. I have used the BigBlueButton API to develop the web version, which is working properly on the web. I'm trying to use that web app URL in my react native app using react-native-webview. In iOS app, I'm able to join the session but while enabling video I'm getting error message as follows
**Audio/Video not supported**
At this time audio and video not supported on chrome for ios. We recommend using Safari iOS.
When I'm setting userAgent as "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_0) AppleWebKit/604.3.5 (KHTML, like Gecko) Chrome/83.0.4103.97 Version/12.0.1 Mobile Safari/604.3.5".
And when I'm setting userAgent as "Mozilla/5.0 (iPhone; CPU iPhone OS 13_5 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) CriOS/83.0.4103.88 Mobile/15E148 Safari/604.1" I'm getting following error.
On iOS please use Safari for full support.
When I'm removing the userAgent it showing the error like
It looks like you're using a browser that is not supported. Please use either Chrome or Firefox for full support.
Thanks in advance.
I'm parsing s3 logs to identify requests made from iMessage previews (on Mac OS Sierra & iOS 10).
There are few common types of UA strings, but I can't tell which are from the browser vs. imessage. I'm hoping it's a unique UA from Safari:
`AppleCoreMedia/1.0.0.14B100 (iPhone; U; CPU OS 10_1_1 like Mac OS X; en_us)
^ Gotta be iOS Safari, right?
2.MobileSMS/1.0 CFNetwork/808.1.4 Darwin/16.1.0`
^ I think MobileSMS means imessage (hopefully)
Mozilla/5.0 (iPhone; CPU iPhone OS 10_1_1 like Mac OS X) AppleWebKit/602.1.32 (KHTML, like Gecko) Mobile/14B100 Twitter for iPhone
^ Twitter via webkit webview?
Mozilla/5.0 (iPhone; CPU iPhone OS 10_1_1 like Mac OS X) AppleWebKit/602.1.50 (KHTML, like Gecko) CriOS/54.0.2840.91 Mobile/14B100 Safari/602.1
^ more iOS Chrome (i see you CriOS)
Mozilla/5.0 (iPhone; CPU iPhone OS 10_1_1 like Mac OS X) AppleWebKit/602.2.14 (KHTML, like Gecko) Version/10.0 Mobile/14B100 Safari/602.1
^ more iOS Chrome?
Twitter/5002568 CFNetwork/760.6.3 Darwin/15.6.0 (x86_64)
^ Twitter
I've just faced the same issue while trying to re-route the iMessage crawler to a non-angular page which will generate the correct meta tags for it and found this question in the process. Figured I'd write an answer since I've now found it. Apple's documentation says nothing but mention the ...(Applebot/x.x) User-Agent which is not the correct one. I've found nothing on the internet so I logged traffic to just one file on a public server and shared the link via iMessage. In the log file I received:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1) AppleWebKit/601.2.4 (KHTML, like Gecko) Version/9.0.1 Safari/601.2.4 facebookexternalhit/1.1 Facebot Twitterbot/1.0
When I've modified my RegEx to fit this User-Agent, the iMessage crawler was finally re-routed to the correct location.
So there it is, it's probably subject to change without notice since it does not exist in any official Apple documentation as far as I can tell but I hope this still helps someone :)
Use this regex to identify requests from IMsg crawlers.
(Twitterbot(.*)facebookexternalhit)|(facebookexternalhit(.*)Twitterbot)
I have tested it and it works perfectly.
When using the native iOS share dialog UIActivityViewController inside you own App and starting to share a link via the Facebook icon a SocialUIService is in the background crawling the link/website for additional information.
What HTTP user-agent has this SocialUIService service?
From what I can tell, when the SocialUIService fetches the link in the background, the user agent is:
Mozilla/5.0 (iPhone; CPU iPhone OS 8_1_2 like Mac OS X) AppleWebKit/600.1.4 (KHTML, like Gecko) Mobile/12B440
Where if you were to click on the link in Safari, it would look like this:
Mozilla/5.0 (iPhone; CPU iPhone OS 8_1_2 like Mac OS X) AppleWebKit/600.1.4 (KHTML, like Gecko) Version/8.0 Mobile/12B440 Safari/600.1.4
Notice the two missing pieces are Version/8.0 and Safari/600.1.4
I'm trying to view a users tweets from my app but twitter responses with a webpage saying:
Sorry that page is not supported on mobile at this time
However if i load the same URL with mobile safari i get a nice webpage with all the tweets.
I'm using this URL: http://mobile.twitter.com/SOME_USERNAME/tweets
You can reproduce the error message by visiting the url in safari. If you use safari as developer and you set the user agent to iPhone you'll get the right page.
It seems the webview is sending different headers as User Agent:
Mozilla/5.0 (iPhone Simulator; CPU iPhone OS 5_1 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Mobile/9B176
vs
Mozilla/5.0 (iPhone Simulator; CPU iPhone OS 5_1 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9B176 Safari/7534.48.3
Is there anything i could do about this problem?
Apperently it does work when i remove the /tweets part of the URL.
This is not really the answer to my question but it is the best option as long as nobody comes up with a better answer i'll accept this answer.