@Triton said in Logging: no attachment when sharing log to K-9 mail:
Ok, so sharing debug info works? Did you share the debug info to K-9 mail, too? Debug info and log sharing use almost the same mechanism (but of course the problem can be in detail).
Well, no, I did not even try that. I had copied the text, saved it to a file, and copied that via USB.
If you have Amaze installed (isn’t it installed by default in most Lineage builds?), you can share to “Save as…” to save the file:
So perhaps the bug is: Sharing of logs only works after sharing of debug info done once? It may actually not be K-9-Mail related, as the changed title now suggests.
If you find a way to reproduce this, please let me know. I couldn’t reproduce it even when clearing the app data before and then sending it to K-9 mail.
I have changed the title to what happened according to your description, because “Logging fails” doesn’t contain specific information for people who might have the same problem.
Also, for privacy reasons I would really appreciate some method of looking at the logs locally on the device before sending them anywhere.
This seems to be a misunderstanding: “Sharing” the log doesn’t mean to “send” it to a server or something like that. It just shares the data with another app in a policed way. For instance, you can “share” with Amaze’s “Save as…”, or “share” with “Save to clipboard”, or “share” with Share via HTTP to make the file temporarily available on a local (!) Web server.
When DAVx⁵ would save the logs to a folder, every app with external storage permission could access the logs, so it would be the same as you would permanently “share” the logs to all apps with external storage permission.
Saving them to some folder would be sufficient. From there on eyerything would be under the user’s control.
If you save the logs to a folder on an external storage, every app with permissions to access external storage can read the logs and all its private data. This is why we have pointed out that users should delete logs as soon as they didn’t need it anymore.
Logs on external storage (DAVx⁵ until 2.2): All apps with external storage permissions can access the logs. Users don’t have control which apps are accessing the logs. Malware might watch the external storage for changes and immediately send all files to a malicious server. If the logs are saved to your SD card, people can physically remove the SD card from your device and read the logs (except you have set up encryption for the SD card).
Also, it’s very cumbersome because you need a file manager app, fiddle around with file locations, permissions etc. It’s just not how Android apps should feel like.
Logs in internal directory, sharing over FileProvider as recommended in Android guidelines (DAVx⁵ 2.2+): Logs can’t be read by any other apps (without root privileges). Only when the user “shares” the log to another app, this specific app can temporarily access the logs.