HTTP user-agent of iOS SocialUIService? - ios

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

Related

Strange Tailing Number in the User-agent from iOS devices

Mozilla/5.0 (iPhone; CPU iPhone OS 15_6 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 (1234567890)
What does the the tailing number (1234567890) in the above user-agent mean? Is it something that can be used to track someone?
I have compared it with a user-agent from Safari which look like something as follows:
Mozilla/5.0 (iPhone; CPU iPhone OS 15_6_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.6.1 Mobile/15E148 Safari/604.1
The tailing number "(1234567890)" is replaced by "Safari/604.1". I suspect (1234567890) means the id of some iOS app but I have no evidence.

jitsi not supported in IOS xamarin webview

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)

What is the user agent string for iOS / MacOS iMessage?

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.

Why are some iOS devices sending OPTIONS requests with Origin: null?

On a website I'm working on, we're seeing quite a few OPTIONS requests from iOS devices that look like CORS preflight checks, but which have Origin: null. Does anyone know what might be causing such requests to be sent with Origin: null rather than the correct origin?
The user agents that I've seen exhibiting this behaviour are:
Mozilla/5.0 (iPhone; CPU iPhone OS 5_1_1 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Mobile/9B206
Mozilla/5.0 (iPhone; CPU iPhone OS 5_1_1 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9B206 Safari/7534.48.3
Mozilla/5.0 (iPod; CPU iPhone OS 5_1_1 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Mobile/9B206
Mozilla/5.0 (iPad; CPU OS 5_1_1 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9B206 Safari/7534.48.3
Mozilla/5.0 (iPod; CPU iPhone OS 5_1 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9B176 Safari/7534.48.3
Mozilla/5.0 (iPhone; CPU iPhone OS 5_0_1 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9A405 Safari/7534.48.3
Mozilla/5.0 (iPad; CPU OS 5_0_1 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9A405 Safari/7534.48.3
In practice, it's not a problem to deal with these requests (just refuse them), but I'm curious to know if there's some particular set of circumstances that is causing this. The only situation I've seen described where the Origin header might be set to null is when the origin is a file:/// URL, and that seems very unlikely - the referer in each of these cases looks like a normal page view of the site.
This question is related but this blog post explains the problem and solution.
If you’ve seen this behavior in your application, you should be able to fix it by using “Content-Disposition: inline” and not “Content-Disposition: attachment”.

Find iPhone Model Information via Browser

Is it possible to get the model information of an iPhone hitting a web page? I've looked at the User Agent, but it doesn't seem to have this information encoded within it. Essentially, I want to do this but from a browser.
They do have different user agent strings. iPhone 4 is
Mozilla/5.0 (iPhone; U; CPU iPhone OS 4_0 like Mac OS X; en-us) AppleWebKit/532.9 (KHTML, like Gecko) Version/4.0.5 Mobile/8A293 Safari/6531.22.7
You can find the complete list here: http://www.zytrax.com/tech/web/mobile_ids.html

Resources