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

[1.14.0-beta1] Failed to launch JVM #3519

Closed
2 tasks done
FadeMind opened this issue Aug 19, 2024 · 2 comments
Closed
2 tasks done

[1.14.0-beta1] Failed to launch JVM #3519

FadeMind opened this issue Aug 19, 2024 · 2 comments
Labels
type:bug Something isn't working
Milestone

Comments

@FadeMind
Copy link

Please agree to the following

Summary

Failed to launch JVM error

What software is involved?

  • Operating System: Windows 11 Pro 23H2
  • Cryptomator: 1.14.0-beta1

Volume Type

None

Steps to Reproduce

  1. Install 1.14.0-beta1
  2. Launch app.

Expected Behavior

Working app

Actual Behavior

20240819-1724083494

Reproducibility

Always

Relevant Log Output

No response

Anything else?

No response

@FadeMind FadeMind added the type:bug Something isn't working label Aug 19, 2024
@infeo
Copy link
Member

infeo commented Aug 20, 2024

Thanks for the report. Faulty commit is 82368e2.

Further tests shown, it is the dagger update from version 2.51.1 to 2.52. I'm pretty sure it is related to

Add a jakarta.inject.Provider runtime dependency in preparation for supporting Jakarta Providers (google/dagger@a8581e0)

@infeo infeo added this to the next milestone Aug 20, 2024
@infeo infeo closed this as completed in d65beb6 Aug 20, 2024
@infeo
Copy link
Member

infeo commented Aug 20, 2024

@FadeMind Thanks for testing the beta und informing us about the issue! We released a new beta just now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants