Last modified: 2014-02-12 23:55:39 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T38382, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 36382 - iPhone 4S users woes including reported screen locking
iPhone 4S users woes including reported screen locking
Status: RESOLVED WORKSFORME
Product: MobileFrontend
Classification: Unclassified
stable (Other open bugs)
unspecified
All All
: Normal normal
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-05-01 14:32 UTC by Jon
Modified: 2014-02-12 23:55 UTC (History)
10 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Jon 2012-05-01 14:32:58 UTC
A couple of users have fed back an issue with iPhone 5.0
I'm not too sure what is so special about these devices to cause these problems
#####

From http://en.wikipedia.org/wiki/Wikipedia:Mobile_Extension_Feedback:

Screen locks please update this app asap. 80.216.224.2 (talk) 12:20, 1 May 2012 (UTC)
User agent: Mozilla/5.0 (iPhone; CPU iPhone OS 5_1 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9B176 Safari/7534.48.3

The mobile site before an April 30,2012 update for the main start page was much better and more usable than the current page.
Please take a look at the mess it is on an iphone. I am looking at en.m.wikipedia.com 99.16.78.65 (talk) 01:24, 1 May 2012 (UTC)
User agent: Mozilla/5.0 (iPhone; CPU iPhone OS 5_1 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9B179 Safari/7534.48.3
Comment 1 Thehelpfulone 2012-05-01 14:36:24 UTC
Changing to iPhone 4S - we've got enough rumours!
Comment 2 Tomasz Finc 2012-05-01 17:45:27 UTC
I think these are two separate issues. I bet the first one is related to an app that screen scrapes our site and is now broken. This is what happens when you screen scrape. We now have a fancy new API that they can use instead.

The second issue was likely due to caching issues during our deployment.
Comment 3 Jon 2012-05-02 22:40:27 UTC
Closing as timestamp suggests it was during deployment.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links