Receive message “A signed resource has been added, modified, or deleted” when trying to debug an App on iPhone

Question

While attempting to debug a build created using the 3.2 SDK on an iPhone device I receive the message \"A signed resource has been added, modified, or deleted.\".

I

Answer 1

This can have several causes. The fastest way to figure out what is causing it is to go into Xcode, Window menu, Devices, then click the reveal button at the bottom of the pane to show the Console. Now attempt to run. You should see log output that names the specific files it is complaining about.

Most of the solutions previously posted are just artificial ways of getting Xcode to regenerate the contents of the build folder and/or re-sign the files.

In my case, my WatchKit extension was somehow acquiring references to Cocoapods frameworks that were only targeted toward the main app so they got signed during the build, then pruned later (as they were not used). Then on device, iOS complained that they were missing from the .appex folder for the extension. I ended up not needing any pods in the extension so I just removed them all and removed the extension as a target, then did some minor cleanup to remove the pod-related debris left in the build steps. Now everything works perfectly.

Answer 2

it seems this is a bug in xcode 3.2.2: iphonedevsdk

Answer 3

I had the same problem in Xcode 3.2.1 when I put a + in my app name. Specifically the "product name" in the build settings. It is fine to have a + in the bundle name in your Info.plist. The same probably applies to other punctuation characters.

Answer 4

I got this error intermittently while installing app using iPhone config utility on Windows7. Following solution works - Go to C:\Users\{lanusername}\AppData\Local\Temp and delete app specific folders (e.g. abc.app) and try installing app again.

Answer 5

This is pretty clearly a bug in the 3.2 SDK, but I don't want to downgrade. I've found that doing a Clean by pushing Command+Shift+K, then Return is pretty fast before pushing Command+R to build.

Answer 6

I reported this bug on ICU (Windows versions) to Apple in June 2011. With the following workarounds:

The workaround is this ....

Win XP

1) Close ICU

2) Delete the temp folder: c:\Documents and Settings\[username]\Local Settings\Temp\[AppName].app

3) Delete the deploy folder: c:\Documents and Settings\[username]\Application Data\AppleComputer\MobileDevice

4) Restart ICU. Drag in the App and install normally.

============================

Win 7

1) Close ICU

2) Delete the temp folder: c:\Users\[username]\AppData\Local\Temp\[AppName].app

3) Delete the deploy folder: c:\Users\[username]\AppData\Local\Apple Computer\MobileDevice\Applications\[AppName].app

4) Restart ICU. Drag in the App and install normally.

=========================================================