Nikias Bassen

It's coming from the device side. I will implement this as a no-op though, since I can't make the idevicebackup2 handle any disk purging (like empty trash etc.). I will...

I can't find any trace of this being handled on the host side (macOS). On the device side I can see there's an error message basically saying that the host...

Even worse, the DeviceLink framework actually disconnect when it receives an unknown message (where the above is considered unknown on macOS Catalina). Not sure what is going on here...

If you can trigger this condition, you can try this patch: ``` diff --git a/tools/idevicebackup2.c b/tools/idevicebackup2.c index 6412fe2..068420d 100644 --- a/tools/idevicebackup2.c +++ b/tools/idevicebackup2.c @@ -2252,6 +2252,11 @@ checkpoint: plist_t freespace_item...

@mexmer you don't have by any chance a full sample message plist?

The milliseconds for the debug output is fine; but the date+time is reflecting whatever the device is sending and I cannot just change that. There's a newer service called `os_trace_relay`...

FYI I compile it with MinGW on Windows.

Some questions. First of all: Which operating system are you using? Did you link libimobiledevice against OpenSSL? Or gnutls? When you built from master, did you make sure it is...

@truonggiang0710 I would love to know myself, but I don't know this unfortunately.

idevicesyslog is passing the data coming from the device byte by byte. Either this is what the device sends or your terminal can't handle the encoding.