Geek Answers Handbook

Xcode - failed to check archive due to strange problems with resolving variables / placeholders in info.plist and permissions

Something is really broken with my project or Xcode, and I'm afraid from two days to find out what is happening.

My application works fine, it is an OS X application and contains the Today Widget extension. I completed the project recently and now I cannot publish the application due to validation errors.

It began with a validator complaining about my application group, which I use to share content between the main application and the widget extension. The group has been identified as $(TeamIdentifierPrefix)com.acme.GreatApp.

The validator complained that my group name was incorrect, and it is better to start with my TEAMID. After 3 hours of working in circles, I replaced the placeholder with the $(TeamIdentifierPrefix)identifier of my team (for example S3F45A5S35.) - and it worked.

Then the validator complained about every kind of other placeholder in my info.plistand rights files, such as $(PRODUCT_NAME), com.acme.GreatApp.$(PRODUCT_NAME:rfc1034identifier)and $(EXECUTABLE_NAME). I replaced all of these placeholders with the corresponding values, which were then accepted.

Then, for a while, the validator complained about structural problems that don't make too much sense to me:

Failed to complete iTunes Store operation. Bad CFBundle Executable. Cannot find an executable file that matches the CFBundleExecutable value in the GreatAppWidget properties file attached package [com.acme.GreatApp.pkg / Payload / GreatApp.app / Contents]

iTunes Store. . "com.acme.GreatApp.GreatAppWidget" GreatApp.app/Contents/Plugins/GreatAppWidget.appex (com.acme.GreatApp.GreatAppWidget)

, ?

iTunes Store. . Bundle GreatApp.app/Contents/Plugins/GreatAppWidget.appex /.

, , , , . , Contents/Plugins. , ?

iTunes Store. CFBundleExecutable . : GreatApp.app/Contents.

, . - , , - , -, , , ?

, , . . Cocoa, Widget Today - . , , ..

, , , . , , . , , , Keychain - Xcode.

:

iTunes Store. CFBundle . , CFBundleExecutable ${bundleName} [ ${bundlePath}]

iTunes Store. . ${bundleIdentifier} ' ${bundlePath} (${ parentBundleIdentifier})

iTunes Store. . ${bundlePath} ${pluginsSubPath}.

iTunes Store. CFBundleExecutable . : ${sharedBundlePath}.

, , Apple , . - Today-Scripts. ($(TeamIdentifierPrefix)com.acme.Today-Scripts, ) , , : !

, .. , , , , , Today-Scripts XPC, , . .

, . , ~/Library/Developer/Xcode/DerivedData, ~/Library/Caches/com.apple.dt.Xcode, , .

, , . , - , heck Xcode .

  • Xcode info.plist ?
  • bundle ,
    • XCode, Cocoa ?
    • / Today-Scripts?
+4
3

- ! , - , info.plist (Target Membership) . , , info.plist GreatApp.app/Contents/Resources. . info.plist .

3 .

+3

" iTunes Store. Bad CFBundleExecutable. , CFBundleExecutable ${bundleName} [$ {bundlePath}] "

adobe air Mac.

"/Contents/Frameworks/Adobe AIR.framework//1.0//AdobeCP15.plugin//MacOS/AdobeCP"

info.plist, "///Adobe AIR.framework//1.0//AdobeCP15.plugin//info.plist"

CFBundleExecutable adobecp

, .

CFBundleExecutable AdobeCP

.

+2

I ended up on this post because I had a similar error, but another reason. My problem was caused by the WatchKit application and the “Embed Watch Content” build phase after my “Run Script” phase. After I moved the “Integrated Content View” build phase between “Copy Bundle Resources” and “Embed Frameworks”, WatchKit validation succeeded.

0
source

More articles:


All Articles