WordPress for Android version 14.6-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.6-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.
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:
- 11580 (Android 9.0+) Switch to Dark Theme on Android. Create a new post with every block you can find and look for any visual problems related to Dark Theme display mode.
- 11580 (Android 9.0+) Switch to Dark Theme on Android. Look through as many screens as possible in the app to try to find visual problems related to Dark Theme display mode.
- 2062 Create a new post, add an image block, tap the Edit Image icon (top right) on the image, try making as many changes in Image Edit mode as you can find (i.e. crop, zoom in/out, rotate) and verify the controls behave as you would expect.
- 2034 Create a new post, add a cover block, try to break it. Also see test cases.
- 2024 Create a new post, add a video block using the “Take a Video” option, verify the icon is now a movie icon and not a camera icon, verify that adding a video works as expected. Bonus: try from a slow network connection.
- 2042 Create a new post, add a group block, create some nested structure, navigate through the blocks, expect that unselected blocks do not get dimmed when navigating the block hierarchy.
- 2076 Create a new post and add Heading, Paragraph, Image, and MediaText blocks. Change alignment options in each one and verify that they look correct in View Site and on the web on the device and on a larger display.
- 20848 Create a new post, add a paragraph and/or button block (or, even better, any block with a link), tap the link to open link settings, tap the keyboard return button, verify it closes the settings panel as well as closing the keyboard.
- 11550 Create a new post add link pointing to
wordpress://read, view a preview of the post, tap the link, verify the app opens to the Stats screen. - 11568 Ensure you have 20 or more pages. Go to My Site > Site Pages, tap on one of the existing pages, verify that you don’t see a blank page when you were expecting to see content and that the content loads normally.
You can find more details about all of the updates that went into this release in the related PRs listed at WordPress-Android 14.6 and gutenberg-mobile 1.25.
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! ❤️