-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Rename SwiftProtobuf to avoid issue #3599
base: master
Are you sure you want to change the base?
Conversation
Hi @dinhnhat0401, thank you for opening the PR! |
@satoshiotomakan thanks. I think all the CI passed (except one for not related issue) |
Hi @dinhnhat0401, unfortunately, we cannot merge the PR since we do not have time to well test it. |
Happy new year. |
@satoshiotomakan I'm also interested in a resolution to this. Any progress? |
Hi @doovers, @dinhnhat0401, sorry for the late reply |
Hey, so this just renames the library, at runtime you'll get a warning since the system can't determine which framework to actually use. |
@dimitris-c do you have any suggestion to make it explicitly defined? |
not off the top of my head, a lot of maintenance would be required to rename the SwiftProtobuf library for it to be unique |
@satoshiotomakan any updates on this? |
Hello! Any updates on this? |
I made a working proof of concept, renaming the SwiftProtobuf dependency during integration. This was mainly achieved by providing a local TWSwiftProtobuf.podspec with an updated library name and minor changes in the build scripts. All related changes can be found here. The working SPM package of the latest wallet-core version was released. It can be integrated into a project with an existing SwiftProtobuf SPM dependency in the same way as stated in the documentation. Unfortunately, this breaks CocoaPods compatibility (WalletCore.podspec) since the podspec specification does not allow for specifying a local pod's dependency. I also tried a different approach to rename SwiftProtobuf on the fly (during pod install) by adding pre/post-install hooks in the Podfile, but it ended up with a broken framework built. |
Hi @podkovyrin, thanks for the update, and especially for the PoC! We'll test if it doesn't break our iOS app, and then borrow the changes 👍 |
Thanks @podkovyrin I tried on an empty project with your release and Firebase via SPM and no complaints from Xcode or runtime warnings |
Description
Change SwiftProtobuf lib name to avoid conflict with other Swift SPM packages.
This will solve this issue: #2088
How to test
Should have no change to functionality.
Types of changes
Change SwiftProtobuf lib name to avoid conflict with other Swift SPM packages.
Checklist
If you're adding a new blockchain