We are aware of this issue and have already communicated it to the developer. No eta on a resolution.