Open SabikAbtaheeSelise opened 4 months ago
Same issue still persists for us. I noticed that a file with filename that has no spaces is uploaded successfully.
example.png
-> success
Screenshot 2024-04-18 at 11.53.55.png
-> "FSP response contains incorrect JSON syntax"
Hi @slipslop and @SabikAbtaheeSelise
Thanks for reaching out on GitHub. Unfortunately, this is not a frequently monitored support channel. To ensure you receive the best and fastest support, please submit your inquiry through our dedicated support ticket system. This helps us address your issues more efficiently and keep track of your requests.
Using the support ticket system ensures your queries receive priority attention and streamlined resolution. We appreciate your cooperation and look forward to assisting you further.
Best regards, Lorenzo | Beefree SDK
I am trying to connect my own file storage system. In case of GET request the plugin fetches successfully from the implemented API.
For POST and DELETE calls I always get an error
{"status":"error","message":"FSP response contains incorrect JSON syntax"}
I have checked multiple times that the json return is perfectly aligned with the documentation. I also tried to send response according to AWS storage system response but still getting this error. For example : { "status": "success", "data": { "meta": { "name": "test", "path": "/test/", "last-modified": 1711621484000, "permissions": "rw", "extra": [], "mime-type": "application/directory", "size": 0, "item-count": 0 } } }
{ "status": "success", "data": { "meta": { "name": "test", "path": "/test/", "last-modified": "1711621484000", "permissions": "rw", "extra": [], "mime-type": "application/directory", "size": "0", "item-count": "0" } } }
According to documentation last-modified,size and item-count are int datatypes. But when using aws storage system i inspected and saw they are string data types. Nonetheless I tried both data types but nothing worked.
how can I debug or find out the reason behind this error
{"status":"error","message":"FSP response contains incorrect JSON syntax"}