Xcode 6 Error: "The entered binary package identifier does not have a prefix with the package identifier of the parent application."

Question

I am trying to create an extension project, and Xcode continues to throw an error into the topic.

In either case, the extension package identifier is prefixed with the application package identifier.

Product Name: ro.chitza.TodayPics.$(TARGET_NAME:rfc1034identifier

I tried to clear the build folder and rebuild, no luck. The funny thing is that the whole project was created several times, but after some changes to the code and user interface, it started to crash. Even if I create new projects, the same thing happens after about 5-6 builds.

Has anyone else encountered this error? Any tips for a solution or a workaround?

Answer 1

Try to clean before assembly. This fixed the problem for me (Xcode 6b2).

Answer 2

It appears that the behavior of the bundle identifier changed when WatchOS 2 appeared.

I used to have an expansion pack id:

 com.mycompany.myappname.watchkitextension 

Elsewhere in Stackoverflow, it was mentioned that the extension package identifier should be in this format, but no matter what I tried, Xcode kept throwing errors at me.

The only possible solution is to change the extension bundle identifier to:

 com.mycompany.myappname.watchkitapp.watchkitextension 

I am sure this is not the case with the WatchOS 1 application. The problem with this change is that you cannot generate the application identifier for the package identifier com.mycompany.myappname.watchkitextension . This is optional, just set all provisioning profiles in the build settings in automatic mode and don't forget to use the correct code signing certificate for the / ad -hoc / debug release schemes.

I really found out that this approach works because Xcode suggested fixing the problem, and that is what it did.

Answer 3

I had to manually change the BundleID in the info.plist extension to what I needed.

I filed a radar: rdar: // 17487465

Answer 4

it helped me:

The extension must have the identifier of the parent package as its prefix.

For example, if you are using the com.ronnathan.myapp application, your extension should be com.ronnathan.myapp.today. You renamed the application target, now go to the extension target and change the name to match.

taken here

Answer 5

I made changes like:

Main Application Id : com.myapp.testapp

and

Extension extension pack identifier: com.myapp.testapp.myextension

and his work !!!

Answer 6

Target-> General → Embedded Binaries remove the old ones and select the new one, this is how I solved this problem

Answer 7

I got the same error, maybe you added an extension such as the Today widget, since the extension is also binary, so it has its own plist, and make sure the package identifier in the plist extension has the application package identifier prefix. Hope this helps.

Answer 8

In my case, this error occurred when I changed the application package identifier. I also have a WatchKit app in my project.

To fix this, update the WatchKit Extension and WatchKit application package ID prefix with the new package ID of your application. Check info.plist for both.

Also update the following -

Update the following with the new monitoring application package identifier. Extension WatchKit> Info.plist - NSExtension-> NSExtensionAttributes-> WKAppBundleIdentifier

Update the following with a new application identifier. WatchKit App> Info.plist - WKCompanionAppBundleIdentifier

After changing all values, be sure to clean the product once.

Answer 9

It may have happened that you duplicated your goals to make a clone app. For example, you selected each of your goals and duplicated them. When you clone your goal to increase the number of hours, its target membership can be automatically assigned to the original watch application.

To fix this, you will need to go to your source file “WatchKit extension.appex” in Project Navigator and deselect the target membership in File Inspector for your new clone-clock app target. You must do the opposite for your duplicate Watchkit extension-copy.appex and make sure that only the duplicate target "watch copy application" is selected in it.

Answer 10

Make sure that:

Target App A → Built-in Settings → Code Signing → Release

matches with:

Target App A (Extension) → Built-in Settings → Code Signing → Release

Answer 11

The problem is that you added the folder using “Create Folder Links” when adding it to your project (like me). @Jacob fix does not work for me :(

I had to remove the link to the folder that I added to my project, then clean and build, and this fixed it for me.

Answer 12

Just remove the application provisioning profiles from the profiles ~ / Library / MobileDevice / Provisioning Profiles, restart Xcode and fix the problems when Xcode requests (or manually downloads them from the dev center in iOS).

This problem is fixed for me.

Answer 13

I had the same problems. Changing the CFBundleIdentifier for my WatchKit extension for something other than the original value used when I first added the WatchKit extension and re-configured access rights to the common application group has been fixed for me.

Answer 14

I just empty the derived folder and it helps me in these situations.

Answer 15

Go to each goal> Build Settings> Product Package Identifier> (Rename anything)