Ok, I lost a day on this already. Trying to find out what was wrong with a query in my web app.
I get a rowset, and iterate it into a string array, and add a row.
Works in the first session I try on cloud but if I open a new browser and try nothing populates.
After a ton of testing I thought to print out the row count of the list box, which apparently was 36 and no data showing.
So I implemented the error event and it tells me Invalid JSON response and suggests a url to better understand the error.
I’m not using JSON data, so I’m assuming it’s in the Xojo implementation.
Never happens on Mac, only Xojo cloud.
There is nothing tricky in the strings: all simple a-z and 0-9.
narrowed it down.
Three columns from the rowset specifically each cause this error.
I’m showing the values in a text area (which can display them fine).
Examples of the offending strings are:
Chris Pregent-Halford
chris’s macbook air
Apple M2
each one of those strings, on their own, cause the error.
I first thought it might be a necessity to escape the commas, but it happens in the word “Apple M2” - seriously, WFT. This is why we really need to be able to do a remote debug session in xojo cloud.
Now that you’ve got it narrowed down, you should open a feedback case so @Ricardo_Cruz can take a look. I’ve not seen this with my deployments, but I typically don’t have access to a Xojo Cloud server. It may, however, be a bug that’'s been fixed if you’re using an old(er) version of Xojo. I seem to remember seeing another similar thread relatively recently, but I can’t find it now.
Yeah, I’ll do that.
It’s always fun to have to reduce it to a simple project that exhibits the problem. In my experience it’s usually a matrix of contributors that gets to the point where it can be shown.
Certainly is. Bump against this constantly myself. Hopefully this won’t be one of those occasions where you have to provide a novel of instructions just for reproduction of the issue.
After a lot of testing I found out what is happening.
Somehow some data had an ascii character 65533 in it. I have no idea how that could have gotten there, but it did.
Now I just test everything with encodings.utf.isValidData and if it isn’t i replace it in the lisbox with ???
Xojo, please enable remote debugging in Xojo cloud!
yep, but there are also invalid single byte characters.
Since i’m controlling how these get entered into the database, i need to figure out the root cause.
