Flower Platform Error Handling and Reporting Strategy
We want every product from the Flower Platform family to converge towards perfection.
We don't want to hide errors and/or provide superficial corrections (e.g. unnecessary !null checks everywhere, etc.). This can lead to unwanted application states and behaviors that can be annoying, hard to reproduce, etc.
It's better to see errors than to swallow them and have obscure bugs & behaviors.
That's why you are seeing error dialogs from time to time. We recommend enabling error reports sending. You can always see what data is sent, you are not bothered while you work and you help a lot the user community.