Just to update the thread:
Our developer Rajeev Pahuja who was in contact with Adobe analyst Dov Isaacs did receive a reply from Dov - the delay was because he's out of the office right now.
In his reply Dov acknowledged that they were able to reproduce the issue and "the problem is actively being investigated". His reply also indicated that Dov is not certain on the timeline of an update or fix but indicated it will likely be closer to the end of this year.
We've additionally asked for an incident or error report number so we can refer to the issue in the future, I will update the thread when we hear back from them.
Regards,
Jeremy W.