error not reported to FES

[tomholub]

I got an error that was not reported to FES

I'm on 8.5.10-dev on Firefox

Couldn't find the actual error in browser error console or in extension debugger console either.

On our EAP I see:

Which looks like too few errors, and my version is not there.

[tomholub]

here is the response to the error call from FES

[sosnovsky]

Looks like extension tries to send exception to shared-tenant-fes, where flowcrypt.com is in the list of disabled domains.
Need to check why it not uses FlowCrypt ES instance.

For mentioned error we have a separate issue - #5971, which caused by some changes in Gmail API, as some users are able to send rich text PGP/MIME, while others get such error. Currently trying to find how we can update encrypted message structure to make it sendable through Gmail API.

[sosnovsky]

Yes, let's also report errors when attemptSendMsg fails, it'll be helpful to find how many users have issues with message sending.

But original issue, described in Tom's comment, is present too - when sending error reports, shared-tenant-fes is used even when user's domain has their own FES configured. For example, when you send password-protected message from ...@flowcrypt.com, it'll use our company's instance, not shared-tenant.
But the same logic doesn't work for sending error reports. It happens because we use SHARED_TENANT_API_HOST for all reports, but need to check if user has another FES URL set in their config (by using isCustomerUrlFesUsed):

flowcrypt-browser/extension/js/common/platform/catch.ts

Line 340 in a55ad90

url: `${SHARED_TENANT_API_HOST}/api/v1/log-collector/exception`,

[sosnovsky]

By the way, did you check original reported issue (#5971)?
It'll be great to find what causes 500 Error and fix it, to make rich-text messages work again.