-
Notifications
You must be signed in to change notification settings - Fork 726
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
SwiftGen 6.5.1 crash (installed via Mint) #905
Comments
Hi @goodocy There seems to be something wrong with your installation, the path to the bundle that Swift is trying to load is wrong. Note that SwiftGen doesn't do this, the system (Swift / SPM) does it for us. Mint itself does not support SPM resource bundles yet, so we had to add a workaround for it with our 6.5.0 release, which was fixed in 6.5.1. See the issue here and the related Mint issue. Make sure you're using the latest Mint version, and if needed reinstall it & SwiftGen. If the issue persists, I'd recommend creating an issue in the Mint repo. |
Same problem for me. |
me too in 6.5.1. |
As I said before, this is (afaik) a Mint issue, not a SwiftGen issue. Going to close this for now. |
I think this issue still is not resolved in any way, even if it hasn't anything to do with SwiftGen. It doesn't work and we need to think about a possible fix or at least a workaround. What do you think guys? Here is the essence of the issue: When calling Copying the bundle to This needs another fix in some way. Env:
|
I second @Fab1n that this issue is not resolved or suffering a regression.
Workaround
|
I'm also facing this issue. The workaround worked for me. |
Hi.
Make a good tool, so I always use it well
Crash problems are found and reported.
image.yml
then
and i found same result ( happens anywhere (with or without swiftgen.yml ) )
after a little analysis, I got some hints
swiftgen bin
And after moving to the actual path
It seems that
swiftgen
does not properly recognize theSwiftGen_SwiftGenCLI.bundle
path when installing withmint
please check
The text was updated successfully, but these errors were encountered: