​@vaishali1201 I just installed the package into our development control room. I did something similar to what you did, but I did not export it as a .txt file as shown in your Local file path. I exported it as a PNG and had no issues.

Use the Message Box to display the specific error from your vQRCode variable.

Hi ​@vaishali1201,

The reference picture shows the input in structured format.

Can you try the input in this format

{“data”:”Test”}

Still not working, getting the same error

Hi ​@vaishali1201,

 

The reference picture shows the input in structured format.

Can you try the input in this format

{“data”:”Test”}

Still not working, getting the same error

​@vaishali1201 It’s pretty obvious that the author did not URL encode the data string to be sent to the web-based API. You can easily break these by even adding a newline character at the end of the string.

This means characters like quotes “ need to be converted to their URL-encoded versions.

{“data”:”Test”} becomes {%22data%22%3A%22Test%22}

Use a site like this one to URL-encode your string: https://www.urlencoder.org/

​@vaishali1201 Interestingly, this works too, from the same web-based API that the package uses:

Apparently we DO URL-encode the string before sending it with this action.

​@vaishali1201 Interestingly, this works too, from the same web-based API that the package uses:

Apparently we DO URL-encode the string before sending it with this action.

This worked in one- go . Thank you.

​@vaishali1201 Interestingly, this works too, from the same web-based API that the package uses:

Apparently we DO URL-encode the string before sending it with this action.

I have used this browser method to generate the QR code and it works but I am not able to generate the same string from the QR code generated. Having the same error when using the package.Is that something that can be resolved? Thanks for your inputs.

Hey ​@vaishali1201 , I just got a reply back from the author of the package. 

He was unable to replicate the issue, so I tried in my control room. I am now unable to replicate the issue anymore either! I think something may have changed at the API side of things (api.qrserver.com) that fixed the issue.

Give it a try!