What if you look in the Network tab of the browser’s developer tools? When you invoke a service from Backendless console, the invocation is a REST request sent by the browser, so you will see it there. Please check and see what it shows.
It looks to be returning a 400 bad request, with this as a response:
{
"code" : 0,
"message" : ""
}
Not sure if related or not, but there seems to be some react errors in the debugger, which maybe could explain why the response doesn’t show in console?
I’m basically trying to execute a DELETE request against mailchimp (tested and working in postman), but for whatever reason, when executed in backendless, it fails with a bad request, with no kind of contextual error.
b) I was trying to use the logger block to see if I could gain some more context on the issue, and no logs are being saved to the log file in Console > Manage > Log Management > Files > {Today’s date}.
Byte size for the file shows 1024, and is an empty file. I’m sure this was working the other day, as I was able to see my previous output logs in there.
As for your suggestion, there doesn’t seem to be much glaring out at me, logic and (translated) code wise. I currently have a codeless function (where the external HTTP request logic sits), which is then called in my service function. I thought I would try and re-create the request call directly in the service (since it seems the response is not passed correctly), and that’s when I hit the error above when trying to deploy.
Hi Mark, Yes, I see it in the model under the codeless tab …
An .xml file for each of my service functions, and a single index.js file? Is that correct?
We’re working on a nasty bug which deregisters a service if it contains any errors in the resulting JS. Once the bug is fixed, we will be able to “re-wire” your service so it shows up in the app.
That makes total sense - I did notice that index.js file had some kind of syntax error in the generated JS. To test, I commented out the line, saved the JS in the coding tab (did not know I could do that in console!!) and deployed, and the service showed up.
hmm just tried that out as well, and seems to be doing the same. I created a very simple GET function in a test service (whose responsibility is simply the print out) and logs still seem to not be produced. I have all of the log levels set to “DEBUG” in console as per the documentation?
That’s where I have been looking the last few hours … the odd thing is that there now are logs from before that have populated. I didn’t realize that there would be some kind of delay for them to show up in the file. Odd, but I guess its resolved nonetheless.
