Skip to content
This repository has been archived by the owner on May 9, 2018. It is now read-only.

iTunes connect deploy problem (solved, but still...) #638

Open
awedeebawe opened this issue May 27, 2015 · 4 comments
Open

iTunes connect deploy problem (solved, but still...) #638

awedeebawe opened this issue May 27, 2015 · 4 comments

Comments

@awedeebawe
Copy link

I tried countless times to submit my application to iTunes connect, but every time the archive was created, the "Validate..." and "Submit to AppStore" buttons were disabled.
I found that the Mapbox SDK headers are in "Private", "Public" and some are in "Project" sections. I moved all headers to "Project" section and I was able to submit my app. Is this the correct approach?

@awedeebawe awedeebawe changed the title Suggestion: iTunes connect deploy problem (solved, but still...) May 27, 2015
@incanus
Copy link
Contributor

incanus commented May 27, 2015

This hasn't been a problem in past. Is this a Swift app?

@awedeebawe
Copy link
Author

Objective-C

@username0x0a
Copy link

Same issue in our project, moved everything to Project section in our branch.

This may be an interesting note on this:

Technically, the problem isn't that the headers are Public under Copy Headers, it's that Build Settings > Public Headers Folder Path is set to the default of /usr/local/include. If you're building a static library the headers must be Public, so it's more correct if # 3 is to change Public Headers Folder Path to something more sensible like include/$(TARGET_NAME). CopperCash notes this in an answer below.

From a question on StackOverflow – discussion about the difference for static library and subproject linking.

@JohnRbk
Copy link

JohnRbk commented Jun 16, 2015

Same issue for me, but easy fix to move all headers to Project section. (My app is in Swift)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants