I noticed this appeared to be working yesterday for the oAuth pages (the main site still redirects to mobile though).
I just wanted to check whether a change was made or whether I'm just seeing some random behaviour. I'm ready to submit my app to the marketplace but want to be sure this will work consistently before I do.
I'm not seeing this on Android; I presume because the UA detection isn't picking up the fact it's a mobile device, or someone's decided to set the desktop experience for android users.
Same issue here, big big problem. Can't really require users to take their web-enabled mobile to the desktop to enter some keycodes. Setting the URL to include mobile_mode=off works to a point - you can click the authorise button, but then it bounces you back to the mobile home page rather than completing the authentication. Unbelievably frustrating.
As an FYI to Android developers, you can set the user-agent string for the WebView using setUserAgentString().
I finally got chance to deploy my app to my phone but the oAuth/link account stuff doesn't work where it did on the emulator.
Whenever I load the login/approve screens I get redirected to the generic mobile home page so can't progress.
My UA string is below, could you add this so it can use the full site?
Mozilla/4.0 (compatible; MSIE 7.0; Windows Phone OS 7.0; Trident/3.1; IEMobile/7.0; )
Thanks.
Message edited by willj 2 years ago
willj – 2 years ago
Just to update I am no longer able to reach https://www.lovefilm.com/activate on the device or in the emulator.
I just get redirected to the mobile home page.
Was a change made?
Thanks
kevmcdonk – 2 years ago
I'm seeing the same thing at the moment using a Windows Phone 7 app. Any workarounds that we can pass it to go directly to the main site?
willj – 2 years ago
I noticed this appeared to be working yesterday for the oAuth pages (the main site still redirects to mobile though).
I just wanted to check whether a change was made or whether I'm just seeing some random behaviour. I'm ready to submit my app to the marketplace but want to be sure this will work consistently before I do.
Thanks
Will
jonkong – 2 years ago
Hi,
Did anyone get this working?
Thanks
Jon
Gregory Block – 2 years ago
I'm not seeing this on Android; I presume because the UA detection isn't picking up the fact it's a mobile device, or someone's decided to set the desktop experience for android users.
Dan – 2 years ago
Same issue here, big big problem. Can't really require users to take their web-enabled mobile to the desktop to enter some keycodes. Setting the URL to include mobile_mode=off works to a point - you can click the authorise button, but then it bounces you back to the mobile home page rather than completing the authentication. Unbelievably frustrating.
As an FYI to Android developers, you can set the user-agent string for the WebView using setUserAgentString().