-
Notifications
You must be signed in to change notification settings - Fork 48
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
Problems Launching on Briss 2.0 #60
Comments
Hey, @mattlynskey . Can you share the PDF that is not being loaded successfully by Briss 2.0? Which alpha release of Briss 2.0 exactly are you using? |
Thank you so much for you help @cleydyr! Here is a .pdf where the problem occurs (although, the same issue occurs on multiple .pdfs). I am using the most recent alpha release v2.0-alpha-4. Thanks for your help! |
No problem, @mattlynskey . I can't reproduce the behavior in a MacOS using the document that you've attached. What operating system, processor architecture and Java version are you using? |
I just upgraded to MacOS Ventura 13.1. My processor is 2.3 GHz Quad-Core Intel Core i5. When I upgraded, Briss 0.9 stopped working. Then, I found Briss 2.0. I tried to use Briss 2.0 but I had the error message in the first post: "The application 'JavaLauncher' can't be opened." I updated Java version 8. I still could not get the program to run (the error message above get coming). A friend helped me run the program through Terminal (maybe this is part of the problem, not sure??). When I run the program, the Briss screen shows up, but any pdf I run does not fully load. I hope this explains the situation. Thanks so much for your time @cleydyr. Any help you can provide would be greatly appreciated! |
Hey, @mattlynskey . I'm also running MacOS Ventura 13.1, but on a M1 Pro processor. And I'm using updated versions of java:
When you run it through the terminal, is there any error message there when the program gets stuck loading the document? |
Here is what Terminal says as it gets stuck. |
@cleydyr Could there be a better way to run the program rather than through Terminal? If so, I wonder what the problem is by the original error message: "The application 'JavaLauncher' can't be opened." |
BTW, here is what Terminal says my Java updates are: java version "19.0.2" 2023-01-17 Does anything look off here? |
I don't think this is something we have much control of, as #59 is also about not being able to double click after upgrading the MacOS version. My comment there may allow you to prescind of the terminal to run Briss 2.0. It looks like you have a way too updated Java runtime (version 19). We use the JavaFX version 11, which requires Java 10 or 11 according to their release notes. It looks like we'll have to update our JavaFX dependency to allow for use of Java 19. So, for now the workaround is to use a not so recent version of Java, like 17. Or you can wait until we provide support for Java 19. |
Hey @mattlynskey we just released an updated version which also works for Java 19 and hopefully simplifies things a lot. Give it a try here: https://github.com/mbaeuerle/Briss-2.0/releases/tag/v2.0-alpha-5 |
Thanks @mbaeuerle. I appreciate the update and the continued work on this application. I look forward to working with it! |
Greetings! I am a grateful user of Briss 0.9 for some time. It is a great app. I recently stumbled upon this update when I upgraded to Ventura and Briss 0.9 no longer works. I was very excited to learn about this upgrade! It is such a useful utility!
However, I am having a difficult time installing Briss 2.0. I am at a very, very rudimentary level of technical understanding. I just upgraded to Ventura on my MacOs. When I try to launch the Briss 2.0 file I get the following error (see image below).
This may not be the correct spot to ask for help on the install problems, but I would be grateful for any help in getting this newer version of Briss 2.0 to work on my upgraded MacOs.
Can anyone provide some help?
Thanks in advance! (And thanks for your great work on this utility!)
The text was updated successfully, but these errors were encountered: