Improve prompt rejection UX #19
Description
Is your feature request related to a problem? Please describe.
When a prompt is rejected it's unclear to the end user what went wrong, there's only a system notification informing the user that the prompt was rejected or failed.
In order to debug the issue you need to run the BeetEOS client to get the terminal logged issue to figure out that the deeplink contents are invalid or that you had insufficient funds to cover operation fees.
Describe the solution you'd like
Perhaps launch an error prompt window for rejected prompts.
Emit from the main thread to the renderer the errors for web console debug logging - enabling production debugging of the network error responses.
Describe alternatives you've considered
Perform action checks before broadcast to network.
Check fee payer's balance is sufficient for requested operations within the prompt, if not then prevent approving the prompt.
Direct users to run the development build if they run into issues.
Additional context
Considering users can craft their own deeplinks, qr codes and local json files to generate blockchain prompt requests, they're likely to incorrectly configure prompts before getting it right, so prompt rejection should be more informative.
We offer an optional receipt for when a prompt is successful, but we don't offer anything for a failed approved prompt.