WordPress for Android version 16.0-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.
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
- Reader: The new redesigned Reader detail shows your post as beautiful as ever. And if you add a featured image it would be twice as beautiful! [13151]
- Reader: Allow users to access Reader even when they do not follow any tags/topics. [13146]
- Block Editor: Full-width and wide alignment support for Video, Latest-posts, Gallery, Media & text, and Pullquote block. [2605]
- Block Editor: Fix unsupported block bottom sheet is triggered when device is rotated. [2710]
- Block Editor: Unsupported Block Editor: Fixed issue when cannot view or interact with the classic block on Jetpack site. [2709]
- Stats: Added the possibility to report and unreport a referrer as spam. [13047]
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:
- View individual posts in the Reader from a variety of different types of sites (WordPress.com, WordPress.com Business, Jetpack, self-hosted, non-WP) and confirm that the actions in the overflow menu (top right) are working properly (browser, share, follow, block this site, report this post) as well as the options in the header (tags, post title, site name, author) and the actions in the bottom bar (bookmark, reblog, comments, likes). Try scrolling quickly. Check that featured images appear as expected. Verify you can read and leave comments. Test in light and dark mode.
- Go to Reader > Discover and confirm you see a “Get Started” option if you are not following any tabs or if your account is brand new. Verify that you can follow new tags and also remove them.
- Create a new site, add blocks for video, latest posts, gallery, media & text and pullquote then change each one to use full-width and wide alignment and verify the posts appear as expected in the editor, web, and Reader.
- On the web, create a post that contains an unsupported block (i.e. audio), rotate the device, expect that a bottom sheet will NOT appear.
- On the web, create a post with a classic block on a Jetpack site. In the app, open the post and try to edit the classic block using the unsupported block editor.
- Using a site that has referrer traffic, go to Stats > Years > Referrers > long press > Mark/Unmark as spam. These actions should work the same way they do on the web.
Updates that went into this release: WordPress-Android 16.0, gutenberg-mobile 1.39.
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. 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! ❤️