Call for Testing: WordPress for Android 14.5

WordPress for Android version 14.5-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.5-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.
  • If you are comfortable testing in a language other than English, please test in that language.

To test:

  1. 1931 Open any post or page, add a Latest Posts Block, verify that tapping on the gear icon opens block settings, save and publish the post or page, verify the updates show on the web (mobile and desktop), re-open the post for editing from the web (mobile or desktop), change each setting, verify from another platform (mobile or desktop) that the settings were updated and are reflected on the published post and drafts as expected.
  2. 1987 Create a new page, notice there are five new starter page templates, tap each one and modify the content for each template and publish. Try from portrait and landscape mode. Does the page template behave as expected? Please be aware of known issues in 2012 and 2013 which are already in progress for a future release.
  3. 1964 Go to https://automattic.com/work-with-us/, copy the first part of the page (from Work With Us until the end of the Coming on board paragraph), paste into any post or page using the block editor, check that all blocks are created and the app does not crash. Try with the content of at least one other web page of your choice that has HTML including wrapped images.
  4. 11478 Turn on airplane mode, go to My Site > Blog Posts, create two posts and publish them, turn off airplane mode so the upload can start and then turn it on quickly before the uploads finish, wait until the upload fails and make sure the UI is not flickering a bug where failed post uploads were sometimes being retried indefinitely.
  5. 11420 Test the signup, site creation, and login flows. Watch for any visual issues or blockers.

You can find more details about all of the updates that went into this release in the related PRs listed at WordPress-Android 14.4 and gutenberg-mobile 1.24.

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! ❤️

#14-5, #android, #call-for-testing, #mobile