You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We replace the "-" char for the whole bundle name.
While we should replace it only for that target name.
For example if we use https://github.com/braze-inc/braze-swift-sdk which its package - i.e project name contains "-" (dashshses) we replace those too, and as such the bundle name we search for is wrong
Here is an example from my env vs a vanila App Project that uses BrazeUI
I created a PR chain between this fix and this PR, as they are somehow linked (I found the bug while I fixed the fixture for the other)
I think that once we merge #6146 we can just directly merge this PR to main
What happened?
We replace the "-" char for the whole bundle name.
While we should replace it only for that target name.
For example if we use
https://github.com/braze-inc/braze-swift-sdk
which its package - i.e project name contains "-" (dashshses) we replace those too, and as such the bundle name we search for is wrongHere is an example from my env vs a vanila App Project that uses BrazeUI
Tuist fixture
App + Vanila SPM
How do we reproduce it?
fixtures/app_with_spm_dependencies
tuist install && tuist generate
import BraseUI
6.1) Something like:
You'd see that the precondition failes
Error log
No specific error, its just when we will try and reach the bundle through SPM it will not be there, as it will look for the wrong name
macOS version
14.4.1
Tuist version
4.9.0
Xcode version
15.3
The text was updated successfully, but these errors were encountered: