Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics

Easy Feedback Form

Easy Feedback brings detailed player feedback and bug reporting to your Unity game directly to you! · By Noah Ratcliff

invalid value for desc

A topic by joeymaru created Mar 23, 2017 Views: 305 Replies: 3
Viewing posts 1 to 3
(1 edit)

Hey there!

Hitting a weird warning sometimes and I'm not really sure what is going on with it? It seems to be kind of inconsistent in when it happens, so I'm having trouble nailing it down.

In the trello.cs class I'm getting this message back when I try to send feedback. I checked the description value that is passed into the add card function and it seems to be fine.

invalid value for desc
EasyFeedback.ExternalAPI.Trello.<AddCard>c__Iterator0:MoveNext() (at Assets/Easy Feedback/Scripts/ExternalAPI/Trello/Trello.cs:103)
UnityEngine.SetupCoroutine:InvokeMoveNext(IEnumerator, IntPtr)

I can get it to work if I change a few things around, on line 103 in trello.cs:

 if(LastRequest.downloadHandler.text == "invalid value for desc") {
 UploadError = true;
 ErrorMessage = "invalid value for desc";

Before it was just logging it out, but if I treat this as an error, it will show an alert, and fail, but every time after when I try to submit it works!

So it seems like classifying it as an error clears some weirdness out and allows it to work on the next go.

Any idea on why this would happen? I can get more info if needed. :)


PSA: after some debugging via email, we've identified that the issue here.

Because of verbose output in the debug log, the description of the card on Trello was longer than their API limit of 16,384 characters. Multiple file attachments with reports are in the works. With that update, I'll be moving the debug log out of the card description, and into its own attached text file.

Additionally, I'll be limiting the length of the overall description to 16,384 characters, and give a more descriptive error when that limit is exceeded.

Thanks for reporting this issue and taking the time to work it out with me!


This bug is resolved in 0.7.1

Nice! Going to look into updating the reporter after I get a little farther along with the playstation stuff I'm working on atm