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

Cannot install as a POD #69

Closed
yangricardo opened this issue Oct 20, 2018 · 10 comments
Closed

Cannot install as a POD #69

yangricardo opened this issue Oct 20, 2018 · 10 comments

Comments

@yangricardo
Copy link

yangricardo commented Oct 20, 2018

Even with de pod install, there are a error on import WeScan

@saormart
Copy link

Did you check your local "Pods" folder ?
Did you try build it before use the "import WeScan" ?

@yangricardo
Copy link
Author

yes, the WeScan pod has a lot of errors on build process in new projects with Swift 4.2, even on drag and drog de WeScan folder into my project... only using it by editing the sample project in this repository....

@basememara
Copy link
Contributor

Experiencing same issues with Swift 4.2.

@basememara
Copy link
Contributor

Figured out you have to use Xcode 10's legacy build system under File > Workspace/Project Settings... and works fine. So this is an issue with Xcode 10+ and sounds like there's a radar on it: CocoaPods/CocoaPods#8073

@yangricardo
Copy link
Author

Thanks for the help!
But i think the pod version still needs to be updated, i have to parse some lines of code to run the same version of this repository.

@jcampbell05
Copy link
Contributor

We have a PR to update the podspec which may be causing the issue #65

@jcampbell05
Copy link
Contributor

I guess we should cut a new release @Boris-Em and then we can close this

@Boris-Em
Copy link
Contributor

I'll work on a new version today.

@yangricardo
Copy link
Author

That's nice to know this project is going to be improved! It helped me a lot combining in a my OCR solution :)

@AvdLee
Copy link
Contributor

AvdLee commented Jan 8, 2019

Way later than planned, but the new release is out. Closing this issue as fixed, let me know if any issues occur.

@AvdLee AvdLee closed this as completed Jan 8, 2019
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

6 participants