Enable VideoPress block on iOS

[SiobhyB]

With this PR, the VideoPress block has been registered behind a DEV flag. The block itself is not complete or fully functional, but is intended to serve as a useful placeholder to be iterated on.

Related PRs

• Gutenberg: [RNMobile] Enable new block in Gutenberg Mobile WordPress/gutenberg#47836
• Gutenberg Mobile: Register VideoPress block behind a DEV flag gutenberg-mobile#5459
• Jetpack: [RNMobile] Register VideoPress block Automattic/jetpack#28812
• Android: Enable VideoPress block on Android WordPress-Android#17928

Testing

Please refer to the Gutenberg Mobile PR as the "central PR" with the most up-to-date testing instructions.

---

Regression Notes

1. Potential unintended areas of impact
2. What I did to test those areas of impact (or what existing automated tests I relied on)

As this is a new block that's been registered behind a DEV flag, it's hoped it won't have any impact on other blocks or areas of the editor. That said, it's always best to be careful and I manually smoke tested some other blocks (including the core video block) to check for any obvious issues.

3. What automated tests I added (or what prevented me from doing so)

No automated tests for now as this is the first step in a larger project. Tests related to this new block will come as it's worked on and functionality is added.

---

PR submission checklist:

• I have completed the Regression Notes.
• I have considered adding unit tests for my changes.
• I have considered adding accessibility improvements for my changes.
• I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.

[SiobhyB]

Enabled only on simple WordPress.com sites for now and added a task to the project board for this to eventually be changed to match the web.

[wpmobilebot]

You can test the changes in Jetpack from this Pull Request by:

• Clicking here or scanning the QR code below to access App Center
• Then installing the build number pr20100-9f6320d on your iPhone

If you need access to App Center, please ask a maintainer to add you.

[wpmobilebot]

You can test the changes in WordPress from this Pull Request by:

• Clicking here or scanning the QR code below to access App Center
• Then installing the build number pr20100-9f6320d on your iPhone

If you need access to App Center, please ask a maintainer to add you.

[fluiddot]

I tested the installable build and noticed that I can add the VideoPress block to a post/page. However, if this block is only meant to be available in development mode (i.e. using __DEV__ flag), it should not be available in the installable builds.

[SiobhyB]

I tested the installable build and noticed that I can add the VideoPress block to a post/page. However, if this block is only meant to be available in development mode (i.e. using DEV flag), it should not be available in the installable builds.

Thanks for spotting this! I'll look into what's causing this. 🧐

[SiobhyB]

@fluiddot, I've added a fix for this with this commit, thanks again for spotting this! No rush to re-review, I don't plan to begin the merge domino until next week 🙇‍♀️

[fluiddot]

I tested the installable build and noticed that I can add the VideoPress block to a post/page. However, if this block is only meant to be available in development mode (i.e. using DEV flag), it should not be available in the installable builds.

As I mentioned in wordpress-mobile/gutenberg-mobile#5459 (review), the VideoPress block is no longer available for insertion, however, it's still being rendered as a regular block instead of an unsupported block.

[SiobhyB]

Noting that I'm working to fix the failing builds.

[SiobhyB]

@fluiddot, the newest installable builds have finished generating now, whenever you have availability for taking another look. Thanks in advance! :)

[fluiddot]

LGTM 🎊 !

I checked that the VideoPress block is displayed as unsupported and that can be edited via UBE (Unsupported Block Editor) on Atomic sites.

NOTE: On Simple sites when using UBE, it shows a warning due to the block not being available on the site. This is expected as the block on the web hasn't been released yet to users.

Tested build pr20100-17ddbb8 on an iPhone 11 (iOS 15.4).