The thing is, sometimes the exception does appear in the log file. When I first looked at this a while ago, I couldn't even reproduce the missing exception from the logs, even with a release build compile.

The thing is, sometimes the exception does appear in the log file. When I first looked at this a while ago, I couldn't even reproduce the missing exception from the logs, even with a release build compile.

It's just a few bytes more even if it's duplicate, I think we can afford that.

The thing is, sometimes the exception does appear in the log file. When I first looked at this a while ago, I couldn't even reproduce the missing exception from the logs, even with a release build compile.

It's just a few bytes more even if it's duplicate, I think we can afford that.

Oh, absolutely, I'd love to not have to ask people to give me the screenshot, only for them to have already restarted the app (or never respond in the first place).
Looking forward to this.

Would it be too much to put a "Latest Exception" header before it or something like that? To differentiate it from later ones

The thing is, sometimes the exception does appear in the log file. When I first looked at this a while ago, I couldn't even reproduce the missing exception from the logs, even with a release build compile.

It's just a few bytes more even if it's duplicate, I think we can afford that.

Oh, absolutely, I'd love to not have to ask people to give me the screenshot, only for them to have already restarted the app (or never respond in the first place). Looking forward to this.

Would it be too much to put a "Latest Exception" header before it or something like that? To differentiate it from later ones

The following log will have something like

--------- beginning of main