-
Notifications
You must be signed in to change notification settings - Fork 25
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
App Store publication issues when using Carthage #698
Comments
@makoni Thanks for reporting this. |
I use latest Xcode 9.2 with iOS 11 SDK |
@makoni That's also good to know. I was asking about the version of the Ably SDK :) |
github "ably/ably-ios" == 1.0.11 I had the same issues with github "ably/ably-ios" ~> 1.0 |
Thanks. What version of Carthage are you using? ( |
0.28.0 |
Is your app including an App Extension by chance? |
No, just iOS app without extensions |
There's a duplication on the file system but likely there's also one in the Xcode project. In the |
Like in README screenshot: |
Can you please get rid of the Carthage build folder and anything related to Carthage in the project, and then run |
I made an empty Xcode project which you can use to reproduce all issues. Just change bundle id and team to yours and try to archive and validate: |
Will try now. Thanks. |
@makoni The solution (workaround?) I found is to delete this folder. Not ideal, but at least you can submit your app :) Thanks for your help so far! |
As for the SocketRocket error I sent a PR here: facebookincubator/SocketRocket#559 |
I created a separate issue for the "SocketRocket missing CFBundleVersion" problem here |
@makoni This is now fixed in version |
@funkyboy |
@makoni can you reopen this? |
Unfortunately there's no reopen button. Try to open a new issue |
There're few issues with publishing to App Store if you add Ably through.
Tha app builds and runs but when you're making an archive and upload it to App Store it won't be validated. Errors while validating:
Is there a chance in will be fixed?
Here's how signing screen looks like:
The text was updated successfully, but these errors were encountered: