I'm happy to report the original issue was now fixed in APEX Listener 2.0.2
However I'm having similar issue on the Oracle Database Cloud. APEX admin console reports Oracle DB Cloud is using APEX Listener 3.0.0 (?).
Can you please confirm if this version includes fixes introduced in 2.0.2 ?