Xcode Organizer device status "TakingInstallLock" and hangs, only cure is full iOS restore

Question

I'm building apps that use UILocalNotifications for alerts. To test scheduling logic, I frequently have to change the system time by minute or hour increments, or change the time zone, etc.

The problem is that after a few sessions of doing this, the Organizer device tab shows a status called "TakingInstallLock" with an indefinite hang in the progress indicator.

1) Is this caused by changing the system time? 2) If not, then what? 3) Or if it is, how else can I test UILocalNotifications that are spaced anywhere from minutes to weeks apart?

Answer 1

A hanging on "TakingInstallLock" can be caused by a long installation process running on the iPhone. For example while you download and install a large game on the device, XCode will show this message if you try to run a project at the same time.

Answer 2

It has to do with modifying the date. If you install your app at say 10:20PM and then set your date back or in the future and try to run the app again, you will get this issue.

Answer 3

I had this problem a moments ago, (TakingInstallLock message for undefined time)

What I did was restart xCode and the Device, but I still had the message. What made the difference was to force quit xCode with the Activiy Monitor, and delete the application from the phone. Then I opened Xcode and could re-run my project with no problems.

Hope this help someone.

-

As a note to the OP , I also had this problem when I was modifying my phone date to test future events. It may have something to do.

Answer 4

This happened to me when I took over a colleague's iPad on which he had previously installed the same app. Terminating Xcode and uninstalling the app from the device before trying again fixed this problem.

After this I got a "application signed with wrong entitlements" problem which I fixed by installing the appropriate provisioning profile.

I later discovered that the iPad clock was set to January 1 1970, so that may be a contributing factor, but I was nonetheless able to debug my app before adjusting the clock.