Skip to content
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

Unable to submit to Appstore #18

Open
ajkerfaisal opened this issue Oct 15, 2017 · 5 comments
Open

Unable to submit to Appstore #18

ajkerfaisal opened this issue Oct 15, 2017 · 5 comments

Comments

@ajkerfaisal
Copy link

Dear 3pillarlabs,
From xCode 9

screen shot 2017-10-16 at 1 38 24 am copy

@dmacra
Copy link
Collaborator

dmacra commented Oct 17, 2017

Thank you for feedback. We are working on fixing it.

@BogdanTC
Copy link
Contributor

Framework is now compatible with Carthage and CocoaPods, please use either one to add the framework to your project and your error should be resolved.

@ajkerfaisal
Copy link
Author

ajkerfaisal commented Oct 20, 2017 via email

@BogdanTC
Copy link
Contributor

Hey there Faisal, I'm very sorry to hear that you are having trouble with CocoaPods. I ran some tests but alas no problems, could you perhaps create a fresh project and use CocoaPods to add the framework, maybe that will confirm if the problem indeed exists or whether it's just your specific project that throws errors. If the problem persists with other projects as well(since I was not able to reproduce the error) can you give me more details for instance is your project a swift or objective c project?
Do you have any other pod's in your podfile besides AutoCompletion, perhaps there is a typo somewhere. Check if you have the latest CocoPods installed as well.

@david-livadaru-3pillarglobal
Copy link
Contributor

david-livadaru-3pillarglobal commented Oct 24, 2017

Hey @ajkerfaisal,

I think that you're having a caching common issue using CocoaPods.
CocoaPods has to fetch the new pods from master in order to install them. Usually that happens when you're doing pod install or pod update. If either commands yields that command means that you do not have that pod on your local repository. As a result, you need to a fetch from master using pod repo update master and thereafter pod update.

Have a good day,
David

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

4 participants