JetPack and WordPress mobile app: accessibility issue introduced

Hello, I'm here to share an experience with latest JetPack mobile app, version 23.0. It's the one used to blog on WordPress sites, both self-hosted and WordPress dot com blogs.
Released between 20th and 21st August 2023, it has introduced this bug:
till 22.x, when inside a new article's editor, you could double-tapp on the "add paragraph block" or "post title" and the standard edit box appeared, so that with Input Braille Screen or your preferred editing mode you could easily write what you needed.
Now, double-tapping on the post title (or the block editor), it actually shows up the keyboard but the text field is treated as closed - saying "double tap to edit" instead of "is editing". The consequences are the following:
- you can't use Input Braille Screen to type content;
- you can't use the "select text" by character, word, line, page or select all, from VoiceOver rotor, to manage text selection;
- you can't paste the text written in another editor (such as a MarkDown editor) to work the issue around, as being the edit field closed, the copy-paste-cut... menu on the rotor, does not appear.
- Bluetooth keyboard is the solution? No, it's the illusion because, yes. It lets you write whatever you want in the field but, together with being uncomfortable to take a keyboard everywhere to write some content just in one app, when you press Enter to create a new paragraph after writing one, the focus randomly jumps where it wants, even a dozen blocks before the one involved in your editing, so it slows the job down. Let's say the JetPack app has become unusable by blind people from this version and I hope it's just a temporary issue which is going to be fixed.
I just reported it to the JetPack "happiness engineer" how customer service calls itself, and to do it you have to go to the "me" page, that's on right top corner of the main JetPack screen, then "help and support", and tickets. Create a ticket in there.
But, meanwhile, please tell me if you encountered the same experience and managed to work it around properly.
Thanks.