Unsupported Block: Non-functional question mark button (iOS only)

[fluiddot]

Description

When doing the TC001 test case of Unsupported Block Editing, I noticed a question mark button located at the lower right corner in the unsupported block editor that doesn't provide any functionality on iOS, after tapping on it, it does nothing. However, on Android, this button redirects to the support page.

I'm wondering if it's the same element that is displayed in the web version that displays the help popup (see attached screenshot):

NOTE: This is not a regression because I managed to reproduce it on version 17.5 of the main apps.

Step-by-step reproduction instructions

Precondition:
A WP.com Simple site (it can be reproduced on an Atomic site too).

1. On the site described above, add a post, then add a block that's not yet supported on mobile
2. Log into the WordPress iOS mobile app using the site's WP.com account
3. Open the post and expect to see the block rendered as a placeholder with the text "Unsupported"
4. Tap the (?) icon and expect the option to edit the block in a web browser to be shown
5. Tap the edit in a web browser button and expect the block to be shown, ready to edit, on a new screen
6. Observe the question mark button located at the lower right corner
7. Tap on the question mark button and observe that it does nothing

Expected behaviour

Elements displayed in the unsupported block editor should have functionality.

Actual behaviour

The question mark button is not functional.

Screenshots or screen recording (optional)

WordPress information

• WordPress version: N/A
• Gutenberg version: v10.8.2-with-min-js-assets
• Are all plugins except Gutenberg deactivated? N/A
• Are you using a default theme (e.g. Twenty Twenty-One)? N/A

Device information

• Device: iPhone 11
• Operating system: iOS 14.2
• WordPress app version: 432a8eceb5140e664fcb7e48db234193748d9f1b

[SiobhyB]

The help button was hidden from view in #37221, following a discussion in wordpress-mobile/gutenberg-mobile#4339, where it was decided that hiding was the best course of action for the time being. I'll go ahead to close this issue, as the button is no longer accessible.