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

Targets names are not compliant with UTI #458

Open
kapitoshka438 opened this issue Apr 2, 2024 · 4 comments
Open

Targets names are not compliant with UTI #458

kapitoshka438 opened this issue Apr 2, 2024 · 4 comments

Comments

@kapitoshka438
Copy link

In an ideal world, targets names have to be Uniform Type Identifiers.
Although the classic approach to add SPM dependencies through Xcode works fine with KSCrash by replacing slash symbol (/) with underscore (_) but it makes it tough to build an xcframework.
KSCrash and also those who import it as a transitive dependency don't work with Tuist - the most popular tool for generating Xcode projects and managing and caching SPM dependencies.
Do you mind removing slashes from targets names in Package.swift.
Firebase is a great example.

@TopIvanAbramov
Copy link

@GLinnik21 actually the problem wasnt solved, we still get similar error due to stange naming: use of "/" in names

Can you fix it?

@GLinnik21
Copy link
Collaborator

Hi!
The development focus is currently on the branch release-2.0, and no stable release has been made with the necessary changes. You might consider using this branch as a dependency temporarily. However, be cautious, as it may include some breaking changes and could be unstable. It might be worth waiting for a more stable release if your project requires high reliability.

@TopIvanAbramov
Copy link

Thank you! Do you have any specific dates for the stable release?

@GLinnik21
Copy link
Collaborator

This is an open-source project developed in the contributors' free time, so it's a bit tough to pin down exact timelines for stable releases. We could potentially roll out a beta version for SPM, but as I mentioned earlier, it might be highly unstable and it would also lack the required privacy report. If you're keen to see the changes sooner, you could definitely speed things up by contributing a PR with the necessary fixes. That would be super helpful!

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

3 participants