Databases
StackOverflow2013
Postsdbo
POApp won't respond until rotation/2x occurs on iPad3
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POApp won't respond until rotation/2x occurs on iPad3
    primarykey
    data
    text
    <p>I am wondering if anyone else has had this happen to them. I have a iPhone App that I have been updating for over a year and it has been working just fine on my iPad2, iPhone 3GS, as well as the 4G, 4GS, and 5. However, just recently I obtained an iPad3 to test the App on. Something very strange happens: When the App is loaded through Xcode in development it comes up and looks perfect - however, <strong>it won't respond to any touches at all</strong>. I have an alert that pops up on load and you can close that, but the actual main view controller will not react to any drag or touch gestures - it is essentially frozen. However! <strong>When I rotate the device and the App rotates correctly, it suddenly starts working just fine,</strong> even if I rotate it back! The simulator for the iPad running iOS6 in normal and retina does the same thing even though it works just fine on my iPad2. However, the simulator for the iPhone works just fine.</p> <p>Like I said, this doesn't happen on any other device. Even loaded the same way all devices allow tapping like normal. Here is what I have been able to confirm:</p> <ul> <li>iPad3 device: <strong>frozen</strong> </li> <li>iPad-retina sim: <strong>frozen</strong> </li> <li>iPad-normal sim: <strong>frozen</strong></li> <li>iPad2 device: normal</li> <li>iPhone-retina sim: normal</li> <li>iPhone-normal sim: normal</li> <li>iPhone 4S device: normal</li> <li>iPhone 4 device: normal</li> </ul> <p>If all the iPhones worked and the iPads didn't, it would make some sense. But my ipad2 works just fine. Also, if I use the iPad3 open it, it is frozen. BUT! <strong>If I hit the 2X button, it starts working</strong> again even without rotation.</p> <p>I also decided to test and see if it would work as a Universal App. On the iPad3 <strong>when I switch it over to Universal, it works just fine to begin with</strong>. So something weird must be going on with the simulator. Any ideas?</p> <p>Thanks!!</p> <p>-Mark</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USKivak Wolf
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POApp won't respond until rotation/2x occurs on iPad3
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POApp won't respond until rotation/2x occurs on iPad3
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POApp won't respond until rotation/2x occurs on iPad3
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI found the solution given for http://stackoverflow.com/questions/13445452/xcode-iphone-app-doesnt-respond-after-starting-in-landscape-orientation-on-ipad works for me as well.
      singulars
      1. POApp won't respond until rotation/2x occurs on iPad3
      1. USmss
    2. COThis also happens with the Stackwise app.
      singulars
      1. POApp won't respond until rotation/2x occurs on iPad3
      1. USUndo
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload