Notify on checkout err

[laur89]

Note this depends on #427

[claabs]

This can work if we're okay with there being no message on the notification.

I'd also like to change the reason from PURCHASE_ERROR to something like RUNTIME_ERROR. PURCHASE_ERROR is a legacy enum from when the project could actually make purchases. Where these errors are caught, it could be for various reasons.

[laur89]

Personally I'd be okay with no message. Reason alone is enough to just pull my attention to check out what's happening, I don't need stacktraces on my phone.

I'd also like to change the reason

Dunno, IMHO it states pretty accurately what's going on - something went haywire at purchase/checkout step.

[claabs]

I'm still hesitant on this since it's quite confusing for the user, especially if they're not the owner of the server.

For example, it says "Click to proceed", but can't be clicked. There's not really a call-to-action.

As the EULA page is the main cause of interruptions these days, I'm looking into either automating it, or at least detecting it and notifying the user with a link to agree to it.

[laur89]

Could always make this an opt-in change.

There's not really a call-to-action

Noticed the same thing but chose to leave the message as-is. And I'd agree checking what's going on is still an action that needs to be... performed.

I'm looking into either automating it, or at least detecting it and notifying the user with a link to agree to it

This would be hands-down the better option.