Skip to content

iTunes Store submission issue #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
andreyz opened this issue Dec 7, 2017 · 4 comments
Closed

iTunes Store submission issue #3

andreyz opened this issue Dec 7, 2017 · 4 comments

Comments

@andreyz
Copy link

andreyz commented Dec 7, 2017

Getting this back from Apple:
Invalid Bundle Structure - The binary file '<Appname>.app/Frameworks/CFNotify.framework/CFResources.bundle/CFResources' is not permitted. Your app can’t contain standalone executables or libraries, other than the CFBundleExecutable of supported bundles. Refer to the Bundle Programming Guide for information on the iOS app bundle structure.

@andreyz
Copy link
Author

andreyz commented Dec 7, 2017

I am including this project manually. To solve the issue I needed to remove CFResources.bundle from CFNotify's Copy Bundle Resources step in CFNotify.xcodeproj for CFNotify target.

Probably a good thing to do as well for anyone else using the project.

@andreyz
Copy link
Author

andreyz commented Dec 8, 2017

Update: the workaround described above, allowed me to submit the app, but resources from CFResources.bundle aren't visible in notifications from CFNotify.

@JT501
Copy link
Owner

JT501 commented Dec 11, 2017

Sorry for late reply, I'm just back from a trip. I will have a look on it in this few days.

JT501 added a commit that referenced this issue Dec 17, 2017
Delete CFBundleExecutable key in CFResources.bundle's info.plist
Delete CFResources executable using Run Script when building
@JT501
Copy link
Owner

JT501 commented Dec 17, 2017

I found out that an unnecessary executable was generated in CFResources.bundle. After plenty of trials, the generation of the executable seems cannot be avoided. Thus, I do it in violent way, I added a Run Script in Build phase to remove the executable everytime the framework is built.

I have tested uploading to App Store, the error is gone and all good. Please try the latest version of the framework. If the problem still exist, please re-open this issue. Thank you.

@JT501 JT501 closed this as completed Dec 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants