From c416abf3360bf5fdc07093678b4d0be22317ebf6 Mon Sep 17 00:00:00 2001 From: Chris Bobbe Date: Wed, 4 Oct 2023 20:14:35 -0700 Subject: [PATCH] NotifTroubleshootingScreen: Make email-sent log line actually reach Sentry An alternative approach to #5720, to help us detect potential cases where the user thought they'd contacted support through the app, but we don't see an email on our side. (We're not aware of such cases yet, but in principle it could happen.) It seems probably fine to do it at the "warn" level rather than "info". If someone sends one of these emails, it usually means something's not quite right with notifications somewhere, making "warn" probably at least as appropriate as "info" in more cases than not. --- src/settings/NotifTroubleshootingScreen.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/settings/NotifTroubleshootingScreen.js b/src/settings/NotifTroubleshootingScreen.js index 8159aefad35..5daf8d9e91d 100644 --- a/src/settings/NotifTroubleshootingScreen.js +++ b/src/settings/NotifTroubleshootingScreen.js @@ -408,7 +408,7 @@ export default function NotifTroubleshootingScreen(props: Props): React.Node { break; case MailComposer.MailComposerStatus.SENT: showToast(_('Email sent')); - logging.info('NotifTroubleshootingScreen: MailComposer reports a sent email.'); + logging.warn('NotifTroubleshootingScreen: MailComposer reports a sent email.'); break; case MailComposer.MailComposerStatus.UNDETERMINED: logging.warn('MailComposerStatus.UNDETERMINED');