-
Notifications
You must be signed in to change notification settings - Fork 149
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Wrong repo for pod in submodule #154
Comments
That's part of resolving Circle CI issues. You don't need to download submodule to use themis. Do you see any error while fetching repo? |
Forget about submodule. |
Thank you @valeriyvan. That's part of issue #152. Working on this. |
Won't |
It's not the issue of putting wrong podspec path :) It's obviously wrong and will be changed later. It was made intentionally while setup Circle-CI tests in past. However, Circle-CI is not working as expected |
At least we agree it's wrong) |
No one denied it is |
forget about boring gitsubmodules! new future is coming: testing using bitrise 💪 i'll remove submodule and close this issue when set up separate test workflow via bitrise #152 |
Why is Podfile in submodule set for different repo for themis???
The text was updated successfully, but these errors were encountered: