Open BrunolourencoLucas opened 4 days ago
After three days of searching, testing, and crying, I decided to make the issue public. Just minutes later, I found the problem. It seems there is a conflict between QZ Tray and this plugin: https://github.com/CodeByZach/pace.
@BrunolourencoLucas thanks for filing this bug report. I believe that your actual error stems from the polyfill library that you are using, but I'm not entirely certain as we use promises heavily in our library, and are compatible with 3rd party promise libraries.
Since versionCompare
is part of the backtrace, this may be a duplicate of #1301, which is caused by a race condition in our JavaScript library. Can you test to see if the qz-tray.js from our master branch fixes this? I've linked in in the bug report,
I have conducted some tests, and it seems that the issue is not related to #1301. The master branch does not fix it.
I have conducted some tests, and it seems that the issue is not related to #1301. The master branch does not fix it.
I tested with promise-polyfill@8.3.0
and the reported symptom/bug does not occur.
Since the sample code does not reference exactly which JS libraries you are using, can you please zip up all dependencies in the linked example and attach? That way we can dive deeper on which one's conflicting with QZ Tray.
Hello everyone, I'm new to using QZ Tray, and I'm having an issue. Unfortunately, I can't establish a connection with QZ Tray. Every time I use websocket.connect() and try to use other API functions like printing, it shows that I don't have an established connection with QZ Tray. After using websocket.connect() and then websocket.isActive, it returns false. However, in the application, it shows that a connection was established. If I reload QZ Tray from the sidebar, it shows the "closed connection" log. If someone could help me, I would appreciate it.
The flavor is actually set to plain. I printed it before and tested it on plain, but I still get the error.