problem with exported logs

[markens 11]

The "message" field is missing in exported logs.  Version 5.1.1(1) on ios 12.2.

I have six pending logs, each with a log message saved.  When exporting for use in GSAK I use the "Export .txt File" menu option under Pending Logs.  This used to work fine!   In 5.1.1, the message field is written as "(null)" instead of the saved log message.  I usually export to Dropbox, but I also tried sending via email with the same result.

Here's the .txt file written via either method:

GC87EKZ,2019-05-23T17:50Z,Found it,"(null)"
GC887J1,2019-05-23T18:06Z,Found it,"(null)"
GC87ZQ0,2019-05-23T18:19Z,Found it,"(null)"
GC87F3J,2019-05-23T18:30Z,Found it,"(null)"
GC80R08,2019-05-23T18:44Z,Found it,"(null)"
GC87ZYR,2019-05-23T19:35Z,Found it,"(null)"

[Nic Hubbard 650]

When you view the pending logs, do those logs have log text when you view them?

[markens 11]

2 hours ago, Nic Hubbard said:

When you view the pending logs, do those logs have log text when you view them?

Yes, they all have log text in the "Message" field when I look at them in the Pending Logs section.

[markens 11]

Updated to 5.1.2(3) and tried several more tests:

(1) Added a 7th pending log and exported as .txt -- same result (all seven logs show "(null)" as the log text.

(2) Selected "Send Log Now" for the added entry, and sent it to gc.  It was posted correctly (with the intended log text).

(3) Deleted all pending logs

(4) Wrote and saved a new log entry.  Exported via .txt with same "(null)" log text as before.  Submitted to gc using "Submit All Logs" button; it was posted correctly.

So definitely an issue with exporting via .txt, at least in my instance.  I've used this extensively as part of my normal work flow with no problem until now.

Thanks.

[markens 11]

Also rebooted my phone with no change in behavior.

[Nic Hubbard 650]

This issue has been fixed and will be included in our 5.1.3 update.

 

[markens 11]

Thanks!

17 minutes ago, Nic Hubbard said:

This issue has been fixed and will be included in our 5.1.3 update.