I remember too, it was indeed a nightmare and I don't want to live that again.
It took me a while but I found a workaround that doesn't need any user action nor any adherence to ATK wrapper.
We can just catch the AWTError and try again to re-create our MainFrame. As the ATK initialization fails only after the AWT toolkit has been created, the second call succeeds:
Kevin, can you please check tomorrow that it works for you too?
I'm leaving the ticket open a few days as we will probably receive many more bug reports this week.
Right now it's too difficult to disable ATK on Java 10 and remain compatible with Java 8. I'll revisit this topic once we migrate to Java 11.
Cheers,
Vincent