CORS issues about dymo-connect-framework HOT 91 OPEN

I have exactly the same issue with the latest version of Dymo Connect and have found it frustrating that a fix does not appear to be forthcoming. Fortunately we still have one workstation with the old version of the software, but that's not a long term solution.

One possible alternative could be QZTray, which can be configured to print to a Dymo label printer from your web app, securely. I've been able to print what I need to from a browser to a Dymo using it, although the formatting is not quite right and as these are legally required 'dangerous goods' labels the formatting has to be exactly right.

from dymo-connect-framework.

@timint We are beginning to investigate this issue. Thanks for your help so far diagnosing it.

from dymo-connect-framework.

After tearing my hair out over this for some time I finally found a solution to my issues. It turns out the label type specified in my label template was not compatible with the language that the DYMO software was installed in. It seems that if DYMO Connect is installed on an English US version of Windows, metric-based label types (e.g. Name badge 54 x 101mm S0722430) will not print. I don't understand why all label types are not supported regardless of OS locale, or why error messages were not printed to DYMO Connect Web Service logs to indicate the issue.

Anyways, as @dpolivy suspected, when trying to print my labels the PrintLabel endpoint would return a 500 before complete headers were returned, which is why the "Access-Control-Allow-Origin: *" was missing. I changed my Windows display language to a metric-based one, reinstalled DYMO Connect, and I was back in business.

@ethanpil I'm not sure if this is your issue as well, but to confirm, open DYMO Connect and check which label types (i.e label sizes) are available, and ensure that the label type used in the sample script is among them. If not, you will get a 500 error.

from dymo-connect-framework.

I am too having this CORS issue and can't get around it.
This is on both MacOS and Windows with the latest JS framework on Github.
Firefox, Chrome and Edge are all affected.
Using last DCD software with the last JS library from Github.

This a problem with today's stricter security policies by web browser makers.

VM12:1 Access to XMLHttpRequest at 'https://127.0.0.1:41951/DYMO/DLS/Printing/PrintLabel' from origin 'https://www.domain.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

The following did not solve my problem:

chrome://flags/#block-insecure-private-network-requests
disabled

I figured out why StatusConnected Works
https://127.0.0.1:41951/DYMO/DLS/Printing/StatusConnected

Returns true

And PrintLabel doesn't:

DYMO needs to consistently add the CORS policy to all server responses, not just some.
This should be escalated to the DCD developers.

from dymo-connect-framework.

Sorry, none of these solutions work for me. Here's a screenshot from my chrome which clearly indicated the issue is simply the missing headers from 127.0.0.1 which is the DYMO HTTP server...

from dymo-connect-framework.

@ethanpil I think the CORS issue might be a red herring here. The original request is returning a 500 error which might indicate some other issue on the system. It's possible (likely?) there's a bug in the web service where it is not including the CORS header when returning a 500 error. If you look at the prior GetPrinters or StatusConnected API calls that succeed, my guess is the CORS header will be there. If you look at the actual response, is there a more detailed error message?

from dymo-connect-framework.

What's the status on Mac? The lack of any kind of documentation makes this all very confusing, but from what I can tell DYMO Connect doesn't have a web service on Mac, so we're running Dymo Label Service. As of recent Chrome versions it fails CORS checks like everyone is pointing out, but it also completely hangs on certain requests, which, I believe, is due to a CORS preflight request that Chrome issues. The web service takes the connection but never responds, so it just hangs indefinitely.

You can reproduce this with cURL as follows:

curl -H "Origin: https://example.com" -H "Access-Control-Request-Method: GET" -H "Access-Control-Request-Headers: X-Requested-With" -X OPTIONS --verbose https://127.0.0.1:41951/DYMO/DLS/Printing/GetPrinters

Which, instead of getting an XML response and closing the connection, will just sit waiting forever.

Firefox doesn't seem to have this issue (yet) but it's probably only a matter of time before printing with the web service is broken there too.

from dymo-connect-framework.

DYMO just uploaded (4 hours ago) a new version of the DLSSidecar and it works for me. It is version 1.4.3.123-beta.

Yesterday i tried with the DLSSidecar_1.4.3-150-beta-WS.exe and it did not work. I had to uninstall Dymo Connect, before i was able to install the 1.4.3.123 version.

https://github.com/dymosoftware/Beta-Version/blob/main/DYMO%20Connect%20Windows/DLSSidecar-1.4.3.123-beta.exe

from dymo-connect-framework.

1.4.3.93 beta on macOS does not work for me. Diagnose gives an error:

Curl shows some kind of SSL error:
curl: (35) error:1400410B:SSL routines:CONNECT_CR_SRVR_HELLO:wrong version number

from dymo-connect-framework.

I gave up a long time ago and bought one of these Brother printers instead.
Their JS SDK works great and the machine is a beast!
https://amzn.to/3YBXum6

from dymo-connect-framework.

@dartacus Don't feel like you need to apologize. We have all been there. This repository, the development team, and upper management has been a total disaster. Still is. Fact. I say speaking our minds is the best we can do to make ourselves heard. One day they might care.

from dymo-connect-framework.

how can this be fixed ?

from dymo-connect-framework.

Also experiencing this issue. I assume Dymo Connect Service needs to be updated to return "Access-Control-Allow-Origin: *" in the header on all requests to avoid this issue.

from dymo-connect-framework.

I have called DYMO and emailed this address per the phone support sdkreply @ newellco.com
Perhaps if we all call and email we might get some attention faster...

from dymo-connect-framework.

I was able to find a workaround for chrome.
chrome://flags/
disable > Block insecure private network requests.

Not sure on how safe it is, but it got me up and running. I too have reached out to support with no help.

from dymo-connect-framework.

I was able to find a workaround for chrome. chrome://flags/ disable > Block insecure private network requests.

Not sure on how safe it is, but it got me up and running. I too have reached out to support with no help.

This worked for me. my client was using edge which is based on chrome, i think it might have broken because of this
https://developer.chrome.com/blog/private-network-access-update/

from dymo-connect-framework.

Also having this issue. I can get it to work right up until the call to print. Turning off browser security seems like the wrong answer. Is Dymo still supporting this framework or not?

from dymo-connect-framework.

I was able to find a workaround for chrome. chrome://flags/ disable > Block insecure private network requests.

Not sure on how safe it is, but it got me up and running. I too have reached out to support with no help.

I just tried this, and I still get the CORS error when it tries to issue the print.

To be fair, I also had to use combinatronics to even link the js into the project.

IT seems like they are just letting this die, which is sad. Very useful feature.

from dymo-connect-framework.

I've recently been trying to reverse-engineer the dymo-connect-framework.js file to solve a new issue that has come up for me - the getPrinter function has suddenly stopped returning printers even though the GetPrinters Web Service endpoint is returning them (I resorted to building a simple Ajax function to fetch the printer from the endpoint directly instead of using the framework's function). The file is in a real messy state and the code seems severely over-engineered. Without attention from Dymo the only hope is if the community takes over ownership and maintenance.

from dymo-connect-framework.

I know the DYMO team is a bit overloaded at the moment with the launch of the new LabelWriter 5xx series printers. I will raise this with my contacts there and see if we can get an official response/update.

In the meantime, have you tried going back to the older DYMO Label Software v8.7.4? That's what I'm currently running and it looks like the web service is returning the access-control-allow-origin: * header in the response.

from dymo-connect-framework.

Thank you @dpolivy in case they cant get this fixed, I found this page with some higher ups at Dymo and we can try emailing some bosses to get attention... https://www.elliott.org/company-contacts/newell-brands/

from dymo-connect-framework.

Thank you for your patience.

labelwriter.com will be deprecated sooner or later because it is aged server.
And labelwriter.com ran into an issue passed into 127.0.0.1 which blocked by CORS policy:
The request client is not a secure context and the resource is in more-private address space local.

Javascript SDK works with sample html files with your local framework.js file against your local Web Api without blocking CORS policy with following steps.

We have a shortterm work-around is:

1. Download dymo.connect.framework.js file and sample files into client's local folder.
2. Put it in the parent folder for the html.

Dymo.connect.framework.js file is:
https://github.com/dymosoftware/dymo-connect-framework

Sample files are:
https://github.com/dymosoftware/DCD-SDK-Sample/tree/master/JavaScript

from dymo-connect-framework.

Sorry @dymosoftware don't understand. Many of us are printing from a remote server on the web to a local printer. How will this solve the CORS issue of printing from a remote web server https://example.com/dymo.connect.framework.js to DYMO printer on localhost?

I read from @dpolivy that reverting to older version of DYMO connect will work. Where can we find DYMO Label Software v8.7.4 downloads for Mac and Windows?

from dymo-connect-framework.

@ethanpil You can find links to the older versions on the Compatibility Chart page here:

https://www.dymo.com/compatibility-chart.html

from dymo-connect-framework.

Yeah, that answer doesn't work. I'm not writing a web service to run on my computer to talk to the printer on my computer. I need to be able to have our hosted site send labels to the connected printer.

I'm also not able to include the 'labelwriter' source, as it is not https. I had to use a third party site to convert the raw.github file.

from dymo-connect-framework.

Hi, do you have any link with a sample that we may try on our side to test with web service?

from dymo-connect-framework.

DYMO web api accepts all cross origins as default already, and we had to setup new sample website which fixes CORS issue between http://labelwriter.com and https://127.0.0.1:xxxx or https://localhost:xxxx.
http://labelwriter.com will be deprecated sooner or later.

The new sample web pages are found "Sample Html Pages" section in Readme file in https://github.com/dymosoftware/DCD-SDK-Sample.

The same sample html pages links are:
https://s3.amazonaws.com/download.dymo.com/dymo/Software/JavaScript/CheckEnvironment/CheckEnvironment.html
https://s3.amazonaws.com/download.dymo.com/dymo/Software/JavaScript/VisitorManagement/VisitorManagement.html
https://s3.amazonaws.com/download.dymo.com/dymo/Software/JavaScript/PreviewAndPrintLabel/PreviewAndPrintLabel.html

Thank you for your patience.

from dymo-connect-framework.

Hey Guys, First off thank you for your response. Moving the script local to the project does work, I also used combinatronics to scrape it from your github. JSDelivr I think does the same thing. That also gets around the https issue but still allows us to grab the framework from you.

ON my issue of the CORS issue when issuing the label.print, that seems to have gone away. My printer stopped being detected, and I had to manually install the driver to a usb port. After that, label.print begain working. The error I was getting back before was rejected due to CORS, but that error might actually have been false?

I'm up and running, so thank you. Not sure if ethanpil is still having the same issue.

from dymo-connect-framework.

@ande2407 my experience is exactly the same, however I have not managed to get the printer to be detected. You wrote "manually install the driver to a usb port" -- what does that mean, could you explain what you did?

from dymo-connect-framework.

@dymosoftware I tried the sample html pages from the AWS links you provided, but they don't even work to detect my printer. At least the demo as I have locally will detect the printer but has the CORS issue.

I'm at a complete loss here, since the suggestions made by @dymosoftware the official developers don't make any sense, and don't address the issues at hand for anyone!

from dymo-connect-framework.

@ande2407 my experience is exactly the same, however I have not managed to get the printer to be detected. You wrote "manually install the driver to a usb port" -- what does that mean, could you explain what you did?

Sure. I'm on Windows 10. When going to 'add printers', the Labelwriter 450 turbo would not show up. I would just click, my printer wasn't detected. Then I would 'add it manually' and select the printer manufacturer and model. I created a usb virtual port for it and let it install the driver.

After that it worked, although only on one port. I assume I might have to create a second virtual port for it for my other USB port, but didn't explore it.

I have the latest Dymo Connect software installed.

from dymo-connect-framework.

@ethanpil I did my testing in firebase. I was able to load the label printer sample to a hosted app there and get it to work. I only had to change the include for the framework. I used combinatronics to create a cdn from the raw.github. After that it worked.

If you think it is helpful for you, I can set that back up and send you the link. I took it down as it was only for testing before moving to my actual project.

from dymo-connect-framework.

Hi, do you have any link with a sample that we may try on our side to test with web service?

I have tried changing the Chrome setting, just to see if it work, it did not.
I updated to the latest dymo-connect-framework JavaScript, it did not help.

It's clear to me that @cage85 is correct. The only solution is to release a new verision of Dymo Connect which sends the correct HTTP headers.

Just to be clear, I am using a remote web server with the printer on the local computer.

I am happy to send you a link I do not want to post publicly here.

from dymo-connect-framework.

If it helps, here is a link to the dymo sample running, hosted in firebase. The only thing different is how the framework is included.

https://dymo-original.web.app/

This works printing to my machine with a 450 turbo.

from dymo-connect-framework.

@dpolivy @ethanpil Yes, I have come to the same conclusion. There is some other error happening which is resulting in a 500 before all the headers are sent. Unfortunately there is no detailed error description to be found anywhere including Dymo Connect Web Service logs. I've spent many hours trying different ways of invoking the print command (label.print, printLabel etc.) and other things but have come up empty. Next I'm going to test different label templates to see if that's the issue.

from dymo-connect-framework.

DYMO web api accepts all cross origins as default already, and we had to setup new sample website which fixes CORS issue between http://labelwriter.com and https://127.0.0.1:xxxx or https://localhost:xxxx. http://labelwriter.com will be deprecated sooner or later.

The new sample web pages are found "Sample Html Pages" section in Readme file in https://github.com/dymosoftware/DCD-SDK-Sample.

The same sample html pages links are: https://s3.amazonaws.com/download.dymo.com/dymo/Software/JavaScript/CheckEnvironment/CheckEnvironment.html https://s3.amazonaws.com/download.dymo.com/dymo/Software/JavaScript/VisitorManagement/VisitorManagement.html https://s3.amazonaws.com/download.dymo.com/dymo/Software/JavaScript/PreviewAndPrintLabel/PreviewAndPrintLabel.html

Thank you for your patience.

Unfortunately I'm still getting the CORS error even on your sample html pages.

from dymo-connect-framework.

@rfdrake27 see above, the CORS issue is probably due to another error occurring before the Dymo Connect Web Service has had a chance to send the correct headers.

from dymo-connect-framework.

Hi,
i had exactly the same Issue. WIN10H1 aktuell Dymo .82
Afer Reinstalling the Software it was working on Chrome and Edge

from dymo-connect-framework.

I am loading label and update label text fields and printing label using latest dymo connect software and windows10 but i am keep getting CORS issue.

tried with Chrome://flags setting but not working.

can anybody please help

from dymo-connect-framework.

@dymosoftware it would be really nic if the webservice would handle internal errors properly, i.e. send correct headers from the error handler.

It's really about time this was implemented.

from dymo-connect-framework.

I am loading label and update label text fields and printing label using latest dymo connect software and windows10 but i am keep getting CORS issue.

tried with Chrome://flags setting but not working.

can anybody please help

Using latest dymo javascript SDK
Tried reinstalling label and dymo connect software but no luck.
windows service is running on port 41951

https://s3.amazonaws.com/download.dymo.com/dymo/Software/JavaScript/CheckEnvironment/CheckEnvironment.html
above url shows

isBrowserSupported: true
isFrameworkInstalled: true
isWebServicePresent: true

@ethanpil @stormframe @rfdrake27 @ande2407 @dpolivy Please let me know if any anybody has working solution or any suggestions about above issue.

@dymosoftware ??

from dymo-connect-framework.

@akash-s-simformsolutions the PrintLabel endpoint is throwing a 500. Maybe your (or Dymos) test page is using a metric-based label type and your Windows installation is non-metric (e.g. US English) or vice-versa.

from dymo-connect-framework.

Hi all,

I've managed to get the Dymo LabelWriter 450 working from Dynamics 365 CE.
It took me a while and I thought I also had an issue with CORS.

I debugged the JS lib of Dymo and in the end it turned out to be an error in my label xml. So, the CORS error message might be a 'red herring', meaning if your sending the printer invalid data, you might get the wrong error message...
(I think @cage85 also is pointing to this...)

Now my label xml is OK and I have no issues using the Dymo Labelwriter 450. So please make sure your data is correct.
(of course, you do need to have the Dymo service running on your local computer)

Good luck!
Ernst

from dymo-connect-framework.

@cage85 Thanks for sharing details. i will check about label type.

@ErnstWolthaus Thanks for sharing details. I am also trying same with Dymo label Printer 450 4XL.
I have created Label using Latest Dymo connect software and i am using that label and updating few dynamic values.

var labelXml = "XML file content geneated by software .dymo file content"
var label = dymo.label.framework.openLabelXml(labelXml);

// Updating some values in label to update it dynamically
label.setObjectText("ITextObject0", "XYZ");
label.setObjectText("ITextObject4", "ABC");

// After updating label i check if its valid or not
label.isValidLabel();  <-- This prints True

// Print label 
label.print("DYMO LabelWriter 4XL");   <--- This is where getting errors.

Also if i do not update label and use as it is which is generated from dymo connect software its giving same issue.

Please check above flow and let me know anything if i am missing. Thanks in advance.

@ErnstWolthaus : If you can share how you created label that would be also helpful.

from dymo-connect-framework.

Hi @akash-s-simformsolutions

1. the labelXml is not correct... it's not xml, so dymo.label.framework.openLabelXml will not process that.
2. are you sure the printername is correct?
3. Is Dymo Connect service up-and-running?

If you are a developer, you can download the full version of the framework and debug into the library to see what's wrong...

I have used this code (changed the labelXml to actual xml, see attachment), and it works for me.

FYI: I have created the label xml with Dymo Connect software. Just create the label and save it to disk. Then use the xml content of that file.
Please make sure you are able to print a label with the Dymo Connect software, just to make sure the standard software works...

labelsample.txt

from dymo-connect-framework.

Hi @ErnstWolthaus Thanks for quick response and example.

1. the labelXml is not correct... it's not xml, so dymo.label.framework.openLabelXml will not process that.
   -> I understood that. i have used proper xml here. but just for understanding i have mentioned that its content of .dymo file, I will try with your label once. Thanks

2. are you sure the printername is correct?
   -> Yes i have used dymo's method to get printer name and using same name in code as well.

3. Is Dymo Connect service up-and-running?
   -> Yes dymo connect service is up and running.

I will test it with new label and let you know updates.

Thanks.

from dymo-connect-framework.

We have same issue as well, the only workaround we managed to work is to use DYMO Label Software 8.5.4 and block DYMO Connect Service from using first port, then it works without issues.

I will see if I can connect debugger to DYMO service to see what it fails on...

from dymo-connect-framework.

@0xE1 They are missing the Access-Control-Allow-Origin: * header in the HTTP response for PrintLabel.

from dymo-connect-framework.

For every response? Was mentioned "not just some", so it might be that the service just throws an exception for most requests and then response does not include necessary headers.

from dymo-connect-framework.

@0xE1 If any DYMO Connect response does not hold an Access-Control-Allow-Origin HTTP header in the response, the browser will return a HTTP 500 error. They implemented it on some responses like /StatusConnected, and /GetPrinters but not /PrintLabel.

They have to compile a new DYMO.WebApi.Win.Host.exe with the fix.

from dymo-connect-framework.

As @ande2407 wrote in previous comments, have you tried to include the script in your web project?
https://s3.amazonaws.com/download.dymo.com/dymo/Software/JavaScript/dymo.connect.framework.js

from dymo-connect-framework.

@dymosoftware This issue ticket is already addressed not to be a user problem. But a problem in DYMO.WebApi.Win.Host.exe.
#30 (comment)

from dymo-connect-framework.

@dymosoftware I am very delighted to hear this. So are my clients. 👍 🙂

from dymo-connect-framework.

@dymosoftware it has been over a week. How long does it take your developers to add this one header? Our project is currently stalled because of this issue. Can you please provide an accurate time estimate? We need to make a decision to downgrade versions to get this working in our systems. We would prefer not to downgrade for obvious reasons. If this will be fixed soon we will wait. But, if not, we have not other choice but to downgrade.

from dymo-connect-framework.

I don't think it's a high priority for them. Seems as if all their focus is on the actual printers and the printer desktop software, whereas a library like this is an afterthought. It took them almost 3 months to even start working on this so i wouldn't count on them fixing it with any degree of urgency.

from dymo-connect-framework.

Hi all, could you try to run your app with this preview version of DLSSidecar_1.4.3-147-beta-WS.exe installed?

Let us know if you still have issues with API headers.

from dymo-connect-framework.

@dymosoftware The CORS problem is fixed. But a new fatal error HTTP 400 was returned.

Error printing label. Exception: 'Element' is an invalid XmlNodeType. Line 22, position 4.

I tried the XML of two different .dymo files. Same line error. (Yes I removed the Byte Order Mark.. that's another confirmed bug see issue #45 ).

from dymo-connect-framework.

@dymosoftware The CORS problem is fixed. But a new fatal error HTTP 400 was returned.

Error printing label. Exception: 'Element' is an invalid XmlNodeType. Line 22, position 4.

I tried the XML of two different .dymo files. Same line error. (Yes I removed the Byte Order Mark.. that's another confirmed bug see issue #45 ).

@timint could you attach the payload sent through the PrintLabel request from Network tab? Specially the labelXML value.

from dymo-connect-framework.

@dymosoftware I have created a separate issue ticket for that. See issue #47

from dymo-connect-framework.

@dymosoftware is there a plan to fix the DYMO CONNECT version 1.4.2 on macOS? We're facing an error on macOS Big Sur DYMO Label Plugin is not installed. Thank you

from dymo-connect-framework.

Hi all, could you try to run your app with this preview version of DLSSidecar_1.4.3-147-beta-WS.exe installed?

Let us know if you still have issues with API headers.

OK with the Beta installed ( and rebooted ) it works fine! Thank you!
Do you know at which Version this fix will be included?

from dymo-connect-framework.

Hi all, could you try to run your app with this preview version of DLSSidecar_1.4.3-147-beta-WS.exe installed?
Let us know if you still have issues with API headers.

OK with the Beta installed ( and rebooted ) it works fine! Thank you! Do you know at which Version this fix will be included?

Fix will be included in 1.4.3 release, expected on March.

from dymo-connect-framework.

I'm the originator of this issue and I just came back happy to find this closer to being resolved, however it seems the link to DLSSidecar_1.4.3-147-beta-WS.exe is now invalid?

from dymo-connect-framework.

@ethanpil : You can find exe and mac application on this URL Beta Version

from dymo-connect-framework.

I'm the originator of this issue and I just came back happy to find this closer to being resolved, however it seems the link to DLSSidecar_1.4.3-147-beta-WS.exe is now invalid?

@ethanpil You can find DLSSidecar_1.4.3-150-beta-WS here

from dymo-connect-framework.

@dymosoftware it seems that link is not working anymore. It mentions something about LFS quota being reached. Can you please put the EXE somewhere we can download it?

from dymo-connect-framework.

Yep. See dymosoftware/Beta-Version#1

from dymo-connect-framework.

I'm the originator of this issue and I just came back happy to find this closer to being resolved, however it seems the link to DLSSidecar_1.4.3-147-beta-WS.exe is now invalid?

@ethanpil You can find DLSSidecar_1.4.3-150-beta-WS here

I installed this version on one of our client machines (Win7) . It doesnt work at all. The Dymo Connect GUI crashes with this info:

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: DYMOConnect.exe
Problem Signature 02: 1.4.3.150
Problem Signature 03: 61f4072b
Problem Signature 04: mscorlib
Problem Signature 05: 4.6.1590.0
Problem Signature 06: 5787ed44
Problem Signature 07: 4168
Problem Signature 08: 0
Problem Signature 09: System.Windows.Markup.XamlParse
OS Version: 6.1.7601.2.1.0.320.65
Locale ID: 1043
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

And the Connect services crashes too:

from dymo-connect-framework.

On another PC with Win7 it does install succesfully. The CORS issue still occurs though:

mainjs?v=JW3WR4tR-tptGWtItcMMRRypi85OXD4RYaO3umL1AOI1:1 Access to XMLHttpRequest at 'https://127.0.0.1:41951/DYMO/DLS/Printing/GetPrinters' from origin 'XXXXXXXX' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

Seems like the allow-origin is still missing here.

from dymo-connect-framework.

On another PC with Win7 it does install succesfully. The CORS issue still occurs though:

mainjs?v=JW3WR4tR-tptGWtItcMMRRypi85OXD4RYaO3umL1AOI1:1 Access to XMLHttpRequest at 'https://127.0.0.1:41951/DYMO/DLS/Printing/GetPrinters' from origin 'XXXXXXXX' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

Seems like the allow-origin is still missing here.

Is there any news on this? We have been forced to revert back to Chrome 97 (Chromium) for many (100+) of our clients. Which is far from ideal and not future-proof at all.

from dymo-connect-framework.

Stable DCD on Mac is missing Web Service, Beta version has it - but it fails to start properly due to SSL error.

We have to ask people to use --disable-features=PrivateNetworkAccessRespectPreflightResults flag to be able to use DYMO on Chrome 98 since it does not handle prefligh requests in any of expected ways, it simply keeps connection opened indefinitely and 3000ms timeout on request actually never times out.

from dymo-connect-framework.

Is there documentation for the api endpoints? It seems that would help in narrowing down some issues.

I've read through the entire thread. These are things that don't work:
❌ Printing from DYMO's sample webpages on amazon
❌ Printing from @ande2407 's example webpage
❌ Printing from my own remote web page (yes, with the dymo connect js library directly within my codebase and not using a cdn or external reference)
❌ Disabling Block insecure private network requests does not fix the issue for a remote requests to localhost

✅ The only fix for me is to run the web app on localhost (which isn't a fix because that's my local dev environment and not available to my users).
✅ I have no issues with my label's xml and no HTTP 500 errors. Everything prints fine from local. I use the exact same label structure and dymo js in code deployed to other servers, so no change there. Additionally, I get the error on any call to the printer webapi including just a status check /DYMO/DLS/Printing/StatusConnected

If we could get some documentation to understand how to form a good request then we could make our own calls to the endpoint. So, if it is Chrome hiding a 500 error for whatever reason at least we could diagnose properly.

The CORS header must be the issue because it just doesn't happen when the code is running from localhost, or from other browsers (and older versions of Chrome). Wouldn't we see issues on local if there were in fact mal-formed label xml or otherwise?

Access to XMLHttpRequest at 'https://localhost:41951/DYMO/DLS/Printing/StatusConnected' from origin '{REMOTE}' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

from dymo-connect-framework.

Direct link to the corresponding (?) Mac app, uploaded at the same time: https://github.com/dymosoftware/Beta-Version/blob/main/DYMO%20Connect%20Mac/DYMOConnect-1.4.3.93-beta.pkg

Not in a position to try it out currently.

from dymo-connect-framework.

I get the following error on 1.4.3.93-beta

from dymo-connect-framework.

There is an work-around for the beta version Web Api issue.
dymosoftware/Beta-Version#2

from dymo-connect-framework.

There is an work-around for the beta version Web Api issue. dymosoftware/Beta-Version#2

Following @blester-mvc's instructions to remove everything and start from a blank slate worked for me.

from dymo-connect-framework.

Well, the CORS issue has now hit with the latest Firefox update, so the workaround we had of using Firefox instead of Chrome is now dead.

When is this issue going to get resolved? It's been months now!

Running DYMO Connect 1.4.3.103 for Mac

This is in the Firefox console:

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://127.0.0.1:41951/DYMO/DLS/Printing/StatusConnected. (Reason: CORS request did not succeed). Status code: (null).

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://localhost:41951/DYMO/DLS/Printing/StatusConnected. (Reason: CORS request did not succeed). Status code: (null).

from dymo-connect-framework.

Turns out it works in Chrome now, but it's broken in Firefox.

from dymo-connect-framework.

I implemented the Dymo.connect.framework on an in-house PHP/Javascript system in late 2021 and it's been working fine until recently - I presume due to the Firefox updates. We don't use Chrome on any computers.

We too are now getting the CORS error: "Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://127.0.0.1:41951/DYMO/DLS/Printing/StatusConnected. (Reason: CORS request did not succeed). Status code: (null)."

The networking tab in Firefox inspector shows no response, but I presume that's because the failed CORS check completely blocks the response.

I tried to make a copy of the framework with https disabled so that I could do some testing in plaintext (and potentially see error information) but I don't have enough knowledge to do that. The dymo.connect.framework.js file is far more complex than anticipated.

from dymo-connect-framework.

@dymosoftware This issue has been ongoing for a year soon. We know what the cause of the problem is. We know how to properly fix it. Why can't we have a proper fix?

This is a total blockstopper for my clients who run the printer.

Simply implement CORS headers for all your Web Service responses and we should be good.

Access-Control-Allow-Origin: *

from dymo-connect-framework.

They recently updated the beta version for windows of the dymo connect software. I was running into this issue and installing that version cleared it up for me. https://github.com/dymosoftware/Beta-Version

from dymo-connect-framework.

@lmason98 What if they could spend some time on actually maintaining these issue reports? Nah prolly takes a rocket engineer for that.

from dymo-connect-framework.

I too gave up and bought some used Zebra printers. I had it printing our stuff in ZPL in just a couple of hours, vs days of initial time investment getting Dymo Framework to run. So simple to use, both using the Zebra print service or printing directly to the printer's IP address!

from dymo-connect-framework.

@zsoden That's the right thing to do. I tried reaching out to DYMO management regarding this complete disaster they have for development. But they didn't want to hear from me. Totally their loss. I have discontinued all DYMO work. Some of my clients also got the Zebra instead. Happy to hear the move went well. I will spread the word.

from dymo-connect-framework.

This has been devastating for me as founder personally doing tech support. Thank you to anyone helping give us solutions.

from dymo-connect-framework.

This has been devastating for me as founder personally doing tech support. Thank you to anyone helping give us solutions.

The previous wording of my comment at the time was probably coloured by several wasted hours grappling with this issue, so I apologise for that: it was needlessly pejorative but I was not in a great frame of mind. I hope you do find a solution: the older version of the software functioned perfectly for many years printing direct from a browser (still is, on one PC).

from dymo-connect-framework.

Hi guys!

I'm also having trouble with the CORS issue for a while now. I'm trying to print labels from an ecommerce website so that my client can print the labels when they added new products.

Were now looking for other alternatives than Dymo. Any good suggestions? I prefer a printer that I can use with an javascript SDK

Thanks!

from dymo-connect-framework.

At this stage it's honestly better to create label pdf either client-side or server-side and present it for printing using normal printing dialog (for example using window.print() of a child frame or window),
and wait for recently proposed Web Printing API to be implemented so you can engage any system printer directly.

I have already created a DYMO label parser (pre-Connect format), preview renderer and PDF export that works perfectly well with chrome.printing API, I just need to clear it with company before I can publish it on Github. Ideally creating vendor-indepentend label format would be best output so it can be printed on anything while maintaining element placement if different paper size is used, though even current form works on any printer.

from dymo-connect-framework.

For anybody else facing this issue, uninstalling and reinstalling Dymo Connect solved my issue - the CORS policy errors went away and I was able to debug again.

from dymo-connect-framework.

I was on windows 10. I saw about (KB5015807) on the software download center. I saw this one inside my update but not the fixed. So I installed all possible updates. Also I made sure I took the correct compatible software for the printer. https://www.dymo.com/support?cfid=dymo-compatibility-chart
Than I rebooted and everything seems to be okay now.

from dymo-connect-framework.

Hi everyone,
I'm working on project where my client want to print label direct from website it work fine 3 4 times then it is giving me error of CORS anyone have any idea how can I handle this error?
TIA

from dymo-connect-framework.