Mac Chrome 98 update not working

[ValerieMichaud]

Since the latest update of Chrome, if we load the dymo.framework.full.js script, the page freezes. It seems like there's an issue with the Web Service connection.

Please see here the workaround that some people provided: https://support.inventorylab.com/hc/en-us/articles/115004970613-DYMO-Not-Working-With-Chrome-Update-Solution

[BillDuggin]

Disabling TLS 1.3 in Chrome flags does not fix the issue. The issue is directly related to Chrome's new Preflight Request CORS response header policy. Currently this is only affecting Mac Chrome 98, but indications are it will affect all platforms with version 101 later this Spring. Any fix, Dymo? This has us dead in the water.

?

[ivanmartynov]

A workaround is to run Chrome with --disable-features=PrivateNetworkAccessRespectPreflightResults flag. Check some discussion regarding this issue here https://github.com/dymosoftware/dymo-connect-framework/issues/30

[loganjmoore]

@dymosoftware can we get an acknowledgement of this issue? This appears to be a different issue than what was able to be fixed with the TLS 1.3 flag workaround fixes. Also launching chrome using the private network access respect preflight results flag did not work either. Our customers are unable to use this on the latest version of Google Chrome on macos and the issue is only going to become a bigger deal as more browsers are updated.

I am running DYMO Label Version 8.7.5.47 and I am using Google Chrome Version 98.0.4758.80 (Official Build) (x86_64) macOS Catalina Version 10.15.7

[miguelduarte42]

I can confirm that we have been hit by this as well. As Chrome is rolling out the update for our users, the Dymo integration stops working. I have tried debugging the issue and indeed the requests to the local Dymo are hanging.

[zach2825]

Having this issue, I tried using the latest js code and it's riddled with undefined goog errors, it's unusable. So I can't test the latest js dymo code

[onlinelaser]

+1 @dymosoftware it's hit us and killed all our printers as well.

[systemx-xx]

@dymosoftware Could we please get some updates on this.

[cod3rshotout]

Download this software https://www.dymo.com/support?cfid=user-guide and the issue will gone

[blester-mvc]

This issue is being addressed by DYMO for the next Connect update, which I've been told will release around March 1st. I'm not sure if the old DLS web service will receive this update.

With that said, DYMO has made available a beta release of Connect that you can install and test out/use in the interim. If you do wish to install the beta, I would suggest following the steps outlined below to avoid any issues:

• Disconnect (unplug) all DYMO printers
• Go to System Preferences > Printers & Scanners and remove any DYMO printers
• Click on the DYMO Web Service icon in the top menu bar and select Exit
• Delete all instances of the DYMO application (Connect and DLS v8) from the Applications folder
• Go to /Library/Frameworks and delete the Dymo folder
• Go to /Library/Printers and delete the Dymo folder
• Go to /Library/Extensions and delete DymoUsbPrinterClassDriver.kext (and any other files with dymo in the name, if they exist)
• Go to /Library/LaunchAgents and delete com.dymo.dls.webservice.plist (and any other files with dymo in the name, if they exist)
• Go to /Library/LaunchDaemons and delete com.dymo.pnpd.plist (and any other files with dymo in the name, if they exist)
• Go to Keychain Access and remove the following system certificates (if they exist):
  • DYMO Root for CA
  • localhost (the one issued by DYMO, in the event you have more than one localhost certificate)
• Empty the trash
• Download the run the beta package installer:
  • https://github.com/dymosoftware/Beta-Version/raw/main/DYMO%20Connect%20Mac/DYMOConnect-1.4.3.93-beta.pkg
• Once the installer is finished, within 30-60 seconds a terminal window should open prompting you for your password. This will run a script that reinstalls new copies of the certificates removed earlier. Another password prompt may pop up to confirm the update to your system settings. If so, enter password to confirm.
• You should now see a new DYMO Connect icon in the top menu bar. If you click on it and select "Diagnose", you should see a message that starts with: "DYMO Connect Service is running . . ."
• Go to System Preferences > Printers & Scanners and re-add your DYMO printer(s)

[frederfred]

Thanks for the detailed instructions @blester-mvc ! I can confirm that the beta version 1.4.3.93 solves the Chrome printing issue for me 🥳. I'm on macOS Big Sur v. 11.6.

I don't know if this was a random failure or not, but first time i ran the installer it didn't work. The installation was successful after a computer restart.

[andlitvak]

Wanted to check in and see if the new connect update is still on track for March 1st? Also, one issue we have with connect is that we cannot get it to support custom label sizes. This was supported out of the box using Dymo Label. Anyone have any work arounds for this issue? Our customers often buy labels from suppliers that offer a wider range of sizes than Dymo currently offers. CC @ivanmartynov

[andlitvak]

@blester-mvc Thanks for the awesome instructions. Using the beta build, I was able to print with the Connect service from our application via Chrome. The odd thing is that the beta is version 1.4.3.93 and there is now version 1.4.3.103 available from Dymo's website. When I follow your instructions for removing all the old software, and then install version 1.4.3.103, I receive an error when I try to 'Diagnose' from the Dymo Connect icon in the menu bar. Error reads "securechannelfailure". Any ideas?

[blester-mvc]

@andlitvak The only thing I can recommend, based on experience, is to try going through the steps again - perhaps with a reboot between removing everything and reinstalling. I haven't yet installed the GA version (thanks for sharing that it's been posted!), so I'll have to see if I run into the same issue.

[andlitvak]

Thanks @blester-mvc Just filed https://github.com/dymosoftware/dymo-connect-framework/issues/54 so hopefully we get some resolution.

[BillDuggin]

Testing the latest Dymo package (1.4.3.103) on a Mac, it does indeed install the new Dymo Connect server, and it appears to install new certificates (/bin/bash /Applications/DYMO.WebApi.Mac.Host.app/Contents/Resources/InstallCertificates.sh). However, hitting Diagnose in the service menu shows the TrustFailure message.

I followed blester-mvc's detailed instructions to uninstall all DYMO packages and remove any older DYMO certs, then reinstalled the package, but still getting the TrustFailure message.

[andlitvak]

@BillDuggin Finding a similar problem (See https://github.com/dymosoftware/dymo-connect-framework/issues/54)