WordPress for iOS version 17.2 beta is available for testing on TestFlight. You can sign up for our TestFlight program and join as a beta tester by opening that link on your iPhone or iPad.
What’s New?
BLOCK EDITOR
- New Block: Jetpack contact info [#3340]
- Image block: Improve text entry for long alt text. [#29670]
- Bug fix: Allow stepper cell to be selected by screenreader [#3362]
OTHER
- Remove Site Switcher from the Editor clean-up [#16188]
- Fixed an issue where some author display names weren’t visible for self-hosted sites. [#16297]
New App Icons!! 😍
Release notes source: WordPress-iOS/RELEASE-NOTES.txt
Updates that went into this release: WordPress-iOS 17.2, gutenberg-mobile 1.51
What Testing is Most Needed:
- If you have VoiceOver experience, or you want to learn (bonus points!!), please try customizing a Column block with VoiceOver. Better yet, do it with your eyes closed or use Screen Curtain. (With three fingers, quickly triple-tap the screen.)
- Create a Columns Block.
- Double-tap the ‘settings’ gear icon to open it.
- Touch “Number of Columns”. The option should gain and retain focus by the screenreader.
- Image Block alt text: Please add image blocks and use the Alt Text feature. Please try adding lots of text! As this is a UI change, dark mode, landscape orientation and RTL languages are also considerations.
- Navigate through the app, using it how you naturally would. Create a new site and add pages, make a story post, go for a walk and show us what you saw!
Test Setup
- Sign up for our TestFlight program by opening that link on your iPhone or iPad.
- Go to Account > App Settings > Privacy Settings and turn on the Collect information option.
- Go to Account > Help & Support and turn on the Extra Debug option.
- Go to My Site > Settings > Use Block Editor to enable the block editor for new posts.
- If you are comfortable testing in a language other than English, please test in that language.
Where to Report
Please report bugs in GitHub at WordPress-iOS or gutenberg-mobile (for block editor issues) if you are comfortable doing so or add a comment to this post if you have any questions, feedback, or issues you’re not sure how to report.
Instructions for Reporting Issues
- Search the GitHub repository first to see if the bug is a known issue. If you verify a known issue, please leave a comment noting the app and device info you tested with!
- For new issues, please follow the template GitHub repository that shows up when creating a new issue.
- Please be aware that a bot will ask for labels but you may not have rights to add them. Know that labels will be added by someone on the triage team.
- Please do not include full Activity Logs which include tokens. Activity Logs can be very helpful for debugging but you should only include them if you have removed tokens as those should not be shared publicly. You can find the logs at Account > Help & Support > Application log.
Thanks for testing!