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

Viewed 49259

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 can clean, rebuild, then install with no error, but if I try to install without cleaning the error shows.

Anyone have an idea as to what might be causing this?

26 Answers

I found a workaround for the bug.

If you delete the .app file in build/Debug-iphoneos/ before building for the device, the app gets installed without errors. And there is a simple way to do that before every build.

Make sure you have selected "Device" in the dropdown overview menu. In XCode go to Project > New target... Then find "Shell Script target" under MacOSX/Other Name it and add it to the current project

Now, in the left navigation panel, under targets, expand your newly created target and double-click on Run Script. In the window that opens replace "# shell script goes here" with "rm -fr build/Debug-iphoneos/*.app" (without the quotes). Now open your main target preferences and under Direct Dependencies add your newly created target. Build and Go! :)

This error occurs when there is a special character in the Product Name. In my case it was a "?"

If you change the Product Name it automatically updates the "Bundle Name" and "Bundle Display Name" so it is often the best choice to rename an app.

If you want to include special characters in the app name you have to manually rename the "Bundle Name" and "Bundle Display Name"

Bundle Name: This is the actual app bundle name in the file system such as "Awesome App.app". It is generally not visible to the user.

Bundle Display Name: This is a short name displayed under the app icon on the device. Since the bundle name would be truncated to "Awes…tion" you have the option to have a shorter name which fits better such as "Awesome App". It should be similar to the App Store name (set in iTunes Connect)

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.

Same for me, thought it has something to do with multiple targets etc. because I changed a lot there. But it's highly possible that it's a Bug in the 3.2.2 release since I did not test extensively in this sdk version before the massive target changes in my project.

solved my issue!!!

I found out by accident that somehow a space " " found it's way into the Product Name of my app so it was called "First Second.app" instead of "FirstSecond.app". After deleting the space the issue was gone!

I changed it here: right click on target Get Info Build Tab Packaging Section Product Name <- The name here will be used for the bundle (.app) name

Hope this helps, let me know!

Cheers, nils

For me the issue was related to the provisioning profile settings. The clue to this was that debug builds were installing ok, but release builds were not. I wanted to test a release build, so I ran the scheme with that build configuration.

I fixed it by duplicating the Release Configuration, then modifying those fields in the Build Settings to have the same provisioning stuff as if I am debugging it.

(Adding another build configuration will give you headaches if you are using Cocoapods however, then you'll have to modify your Podfile)

I'm getting the same thing, when installing on a iPod Touch. I can't link for the simulator (for other reasons), so can't say whether the problem occurs there.

Yes, rebuilding clean or deleting the app from the device allows me to install again. Neither are desirable, iterative solutions!

The minimal "cleaning" I've come across as a work around is manually deleting the Foo.app in the build/Debug-iphoneos directory.

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.

Related