Gideon
Gideon
Opened https://github.com/h4llow3En/mac-notification-sys/issues/79
When the upstream issue is resolved (a new release is made), we need to remove the patched version, and bump to the new version instead.
@lawlietl4 your issue with `cargo install` without `--locked` should be resolved in the next release with #1506
> Cargo-binstall is the fix for right now, it downloads the binary from this repo and puts it in the cargo bin directory without compilation Yup, that should always work;...
@lawlietl4 I've just released a new version that downgrades it. I will only bump it when the build failure is resolved. Both `cargo install` and `cargo install --locked` should be...
To add what I said in #21921: This is the enforcement of the opposite of `strict`. > Looks like a duplicate to me as well. Overall I don't dislike the...
In any case this might need reconsideration of the name of the `strict` setting, both extremes are "strict" in their own way.
I have this issue as well; usually when sharing, the app opens (on the share screen), then immediately closes. The second attempt to share works normally.