[ 
https://issues.apache.org/jira/browse/CB-10078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Hemker updated CB-10078:
----------------------------------
    Environment: 
iPad Pro
iOS 9.1

  was:iPad Pro


> With iPad Pro the wrong userAgent (iPhone) will be saved
> --------------------------------------------------------
>
>                 Key: CB-10078
>                 URL: https://issues.apache.org/jira/browse/CB-10078
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: iOS
>    Affects Versions: Master, 3.6.3
>         Environment: iPad Pro
> iOS 9.1
>            Reporter: Christian Hemker
>
> Using UIWebView on an iPad Pro (iOS 9.1) gives you a wrong userAgent, because 
> is says its an iPhone. 
> The iPad Pro Simulator 9.1 gives you this iPhone userAgent:
> {noformat}
> mozilla/5.0 (iphone; cpu iphone os 9_1 like mac os x) applewebkit/601.1.46 
> (khtml, like gecko) mobile/13b137
> {noformat}
> Same happens for the userAgent on iPad Pro device.
> This seems is a known bug with iOS 9.1 on the Pro, while this is fixed with 
> iOS 9.2 beta 4. Then you get the correct iPad UserAgent.
> If you install an iOS app that is build with iOS (8.4) on an iPad Pro (iOS 
> 9.1/9.2 beta 4) the iPhone userAgent will be used inside the cordova app.
> In this case inside the method originalUserAgent from CDVUserAgentUtil the 
> userAgent „…iPhone…“ is cached inside the app.
> The problem is, that if you install an cordova app update for iOS 9.1, the 
> CDVUserAgentUtil uses the cached „…iPhone…“ userAgent
> instead of the corrected userAgent „…iPad..“ that is fixed with iOS 9.2 beta 
> 4.
> How is it possible not to use the cached value originalUserAgent because in 
> this cases thats wrong?
> If you install the same cordova app build with iOS 9.2 on the iPad Pro (iOS 
> 9.2 beta 4) the userAgent iPad is used.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to