-
Notifications
You must be signed in to change notification settings - Fork 146
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
indy-sdk-react-native as declared dependency instead of vendoring #156
Comments
I'm not 100% sure what you mean by this issue. Could you elaborate a bit @cvarjao? |
It is about getting |
Ah makes sense. That would be really great! Are you going to package the indy binaries with the package, or going to install them with some post install script? |
I just create the issue so I can get somebody else looking into it :D I am not an iOS developer. But, I think it might require some work on the Indy repository side to do the publishing. Hopefully, we can leverage CocoaPods dependency management to take care of the fetching/installing as opposed to the hacky custom download/extract post install script I've introduced for Android. But similar along the lines where the dependency is declared and somewhat installed. |
Going to close this one. The work @TimoGlastra is doing to move AFJ towards ASKAR will make this issue irrelevant. The's already created several tickets to track this work. See #617 for more information. |
…ove-contact-test-dev Trun off retry attempts on failure for BCW tests
As per Twelve-Factor App methodology, switch to "Explicitly declare and isolate dependencies" to "declares all dependencies, completely and exactly, via a dependency declaration manifest"
The text was updated successfully, but these errors were encountered: