Call for Testing: WordPress for Android 14.3

WordPress for Android version 14.3-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.

Please note that 14.3 will have an extremely short development cycle!

To test with an apk, you can download wpandroid-14.3-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 Slack, or head straight GitHub and open an issue—please see “Where to Report” below.

What to Test

To prepare:

  • Go to Account (Me icon) > 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. 1264 Create ordered lists with 4 or less digits in both Aztec and Block Editor and check that the spacing looks good.
  2. 13482 Go to the Blog Details page and use Quick Actions buttons to access parts of a blog. Test from all site types.
  3. 1904 Block editor: add an image block, tap the gear to change to different image sizes, verify the image size changes, verify the image size is preserved if you update the post, leave, return, etc.
  4. 1610 Block editor: add a gallery block and try adding new images to the gallery with all the available options provided. Test from all site types.
  5. 1866 Block editor: add a button block and try to break it. Also see test cases.
  6. 1850 Block editor: add a group block and try to break it. Also see test steps and test cases.
  7. 18574 Block editor: try adding a block from a smaller device or in horizontal mode, verify you can scroll through and add all blocks. Also check that you can scroll the BottomSheet in the image block settings.
  8. 1930 Block editor: create a new post, add a title with any emoji, switch to HTML mode, verify no extra strong elements are added to the title.
  9. 1938 Block editor: add a paragraph block with text, change alignment to right or center, verify alignment changed, tap enter, verify alignment stays set, switch to html, verify alignment is still set properly, go back to visual, verify alignment is still set properly, tap enter in the middle of the text block, verify alignment is still set properly for both blocks.
  10. 1802 Block editor: check that active blocks have a full solid border and a floating toolbar, verify the floating toolbar works as expected. See test steps.
  11. 13496 In iOS Settings > General > Language and Region, set a Region where the week begins on Monday (Lithuania, for example), start a new post and tap to change the Published On / Scheduled date, verify the weekday header starts the week on the correct day. Also test this after changing the WP Admin > Settings > Week Starts On option.

You can find more details about all of the updates for this release in the related PRs targeting WordPress-Android 14.2 and gutenberg-mobile 1.22.

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-3, #android, #call-for-testing, #mobile