@Michel29 I already forwarded the issue to colleagues for the fix. I think it should be fixed in the next update, which is version 44 of our app. Thank you for your patience.