Sentry logs not capturing errors from App Store or GEO Diary

[HollyJoyPhillips]

Summary: Errors created in the App Store and GEO Diary are not being captured by Sentry.

Expected Behaviour: Errors created should be logged and notifications sent through the channel

Errors & Images:

The following error was created in App Store by trying to submit an app whilst reaching the limit of 'Unlisted' apps:

The following error was created in GEO Diary by trying to cancel an appointment (_etag issue):

[duong-se]

@HollyJoyPhillips now the error capture when ever front-end have crash bug by code not by the backend return result. So do you want to capture error from backend also?

[vuhuucuong]

I believe Sentry only captures Uncaught errors, which are errors that are thrown without catch, so that we can track down the error to handle it correctly. Since all the errors in Holly's example have been caught and show an appropriate error message, that will not be logged to Sentry. So I think that's expected behavior.
What do you think @willmcvay ?

[willmcvay]

Can we log caught errors as info? Would be good to get some feedback on how our users are interacting with the product in production, where they are going wrong etc. Just a small logging module to replace the console.error in our catch blocks eg

const logger = (err: Error) => {
if (process.env.NODE_ENV === 'production`) {
     // send an event to Sentry
} else {
   console.error(err.message)
}
}

Usage:

logger(err.message)

[willmcvay]

Obviously the above is pseudo code but you get the idea :-)

[vuhuucuong]

Okay, I got the idea. So that means we need to apply it to all apps, including AML and LTL, right? @willmcvay