Xcode Organizer device status “TakingInstallLock” and freezes, only cure - full iOS recovery

Question

I am creating applications that use UILocalNotifications alerts. To test the scheduling logic, I often have to change the system time to minute or time increments, or change the time zone, etc.

The problem is that after several sessions of this action, the "Organizer Device" tab displays the status of "TakingInstallLock" with an undefined progress indicator hanging.

1) Is it due to a change in system time? 2) If not, then what? 3) Or, if so, how else can I check for UILocalNotifications that are located a few minutes to a few weeks apart?

Answer 1

The suspension on "TakingInstallLock" can be caused by the lengthy installation process on the iPhone. For example, when you download and install a large game on your device, Xcode will display this message if you try to start a project at the same time.

Answer 2

I had this problem a few minutes ago (takingInstallLock post for undefined)

I restarted xCode and Device, but I still had a message. What mattered was the forced shutdown of xCode using the Activiy monitor and the removal of the application from the phone. Then I opened Xcode and could restart the project without any problems.

Hope this helps someone.

-

As a note to the OP, I also had this problem when I changed the date of my phone to check for future events. It can do something.

Answer 3

This is due to a change in date. If you install the application, say 10:20 pm, and then set a date or in the future and try to run the application again, you will get this problem.

Answer 4

This happened to me when I took a colleague iPad on which he had previously installed the same application. Terminate Xcode and uninstall the application from the device before trying to fix this problem again.

After that, I had a problem with the application signed with the wrong rights, which I fixed by setting the appropriate provisioning profile.

Later, I discovered that the iPad clock was installed on January 1, 1970, so this may be a factor, but I was nevertheless able to debug my application before setting up the clock.