Create Sentry issue if we fail to create a file

[ssawchenko]

We will want to be careful that we are not reporting this TOO frequently such that we overwhelm our Sentry limit. We may want to keep track of if we have reported this issue during the App lifetime and only report it once?

[phileo]

will also be helpful to know if Sentry.captureEvent(fileAttachment) failed as well

reference:
https://steamclock.slack.com/archives/CQCEV6YBU/p1692121100482689?thread_ts=1692110239.806389&cid=CQCEV6YBU

[ssawchenko]

will also be helpful to know if Sentry.captureEvent(fileAttachment) failed as well

reference: https://steamclock.slack.com/archives/CQCEV6YBU/p1692121100482689?thread_ts=1692110239.806389&cid=CQCEV6YBU

Good idea, I'll add in a report for that as well.

Update: Dug into this a little further - sounds like in Daniel's case the entire Sentry report isn't being sent. I'm not sure if we can check to see if the Sentry event was properly sent to Sentry or not... ie. I don't think we can simply wrap that call in a try/catch as I believe Sentry batches up reports to send asynchronously.

I can check to see if we have failed to attach files to a user report though, and log a separate crash report for that, but that seems like a different edge case then Daniel is talking about here.

Since doing either of these things is a little larger in scope, I will split this comment out into a separate ticket so that we can move forward with first having Steamclog report on bad file paths: #121