WordPress for Android version 14.9-rc-1 is available for testing on the Beta channel. You can ask to join the Beta Program at Android App Testing on Google Play. Once you have been accepted, click the “Become a Tester” button at the same link.
To test with an apk, you can download wpandroid-14.9-rc-1-universal.apk.
Bugs & Feedback
If you find a bug or want to share a feature request after testing, you can comment on this post, ping one of us in the #mobile room on WordPress.org Slack, or head straight GitHub and open an issue—please see “Where to Report” below.
Release Notes
- Block Editor: New block: Pullquote
- Block Editor: Add support for changing background and text color in Buttons block
- Block Editor: Remove Subscription Button from the Blog template since it didn’t have an initial functionality and it is hard to configure for users.
- Block editor: Page templates have been updated to make use of the newest blocks.
- Block editor: Fix bug in Free Photo Library which allowed selecting multiple images but only inserted one
- Block Editor: Fix the icons and buttons in Gallery, Paragraph, List and MediaText block on RTL mode
- Fix issue with Preview post not working after switching to classic editor from inside the post
What to Test
To prepare:
- Go to Account > App Settings > Privacy settings and turn on the “Collect information” and “Crash reports” options.
- Go to My Site > Settings > Use Block Editor to enable the block editor for new posts.
- Switch to Dark Theme when testing Android 9.0+ devices for this release. On the device, go to Settings > Display > Advanced > Device theme and choose “Dark”.
- If you are comfortable testing in a language other than English, please test in that language.
To test:
- 21930 Create a new post, add a pullquote block, and try to break it.
- 2096 Create a post or open an existing post that contains buttons with colors, make changes to the button text and background colors using the app, publish or update the post, verify the colors appear correctly in the editor, previews, View Site, Reader, and the web.
- 2179 Create a new page, apply the “About” Page template, scroll through to ensure the content is using the blocks described here. Repeat the test for the “Blog” and “Services” page templates. Note: subscription buttons should now be (temporarily) removed page templates since they didn’t have an initial functionality and were hard to configure for users—you should not see any inactive subscription buttons in final published pages from page templates.
- 2261 Create a new post or page, add a Cover block, add images using the Free Photo Library option, verify you can only select one image at a time. In contrast, the Gallery block should allow multiple image selection, verify you can still select multiple images for the Free Photo Library upload option when working with a Gallery block. (Related: 2255.)
- 11649 Create a new post, add a title and some content, tap the 3-dots menu and “Switch to classic editor”, tap the 3-dots menu again and “Preview”, verify the preview appears and the app doesn’t get stuck on “Saving…”.
- 21502 Switch the device to an RTL language, verify the icons and buttons in Gallery, Paragraph, List, and Media Text blocks match with the screenshots showing in 21502.
- Smoke test the bottom navigation bar. We’ve done some changes and there shouldn’t be any user-facing issues, but it might be worth paining extra attention to any weird behavior.
If you are able to complete the entire list above, please continue testing by looking at all the related PRs targeting WordPress-Android 14.9 and gutenberg-mobile 1.28, specifically any that you are able to and that aren’t already represented above.
Where to Report
- WordPress-Android on GitHub for non-block-editor issues.
- gutenberg-mobile on GitHub for block editor issues.
- This post for questions, feedback, or issues you’re not sure how to report in GitHub.
Instructions for Reporting Issues
- Search the GitHub repository first to see if the bug is a known issue.
- For known issues, please leave a comment on the issue saying you were able to replicate the problem and include device name, iOS version, app version, and type of site you used for testing.
- 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 won’t have rights to add them. Know that labels will be added by someone on the triage team. 👍
- If you would like to send Activity Logs to help with debugging (this can be very useful!), you should first trigger the bug and then go to Profile > Help & Support > Application log and use the copy icon at top right to copy the logs. Next, go to Help & Support > Contact us, add a short note mentioning the bug report link, and paste the logs below the note. Please be aware that the Application log may contain tokens which should not be shared publicly, and that’s why logs should be sent through the Contact us form.
Thanks for testing! ❤️