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

• Added reblog functionality
• Block editor: You can now crop, zoom in/out and rotate images from the device that are being inserted in a post.
• Block editor: New block: Buttons. From now you’ll be able to add the individual Button block, only inside the Buttons block
• Block editor: Fix bug where buttons in page templates were not rendering correctly on web
• Block editor: Add support for upload options in Cover block
• Block editor: Fix bug where whitespaces at start of text blocks were being removed
• Block editor: Prefill caption for image blocks when available on the Media library
• Block editor: Fix titles in the media picker
• Block editor: Floating toolbar, previously located above nested blocks, is now placed at the top of the screen
• Block editor: Fix the icons in FloatingToolbar on RTL mode
• Block editor: Add alignment options for heading block
• Block editor: Update quote block to visually reflect selected alignment

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:

1. 11800 Go to the Reader and test the reblog functionality on posts with and without a featured image.
   1. Test reblogging from an account with many sites, verify the site picker is presented and works as expected.
   2. Test from a WordPress.com and a Jetpack site.
   3. Test reblogging from an account with only one site.
   4. Test reblogging from an account with no sites.
   5. Verify the reblog button is not available for posts on private sites.
2. 11742 Create a new post or page, add an image, verify you can crop, zoom in/out, and rotate images from the device that are being inserted in a post. Note: related updates are listed under the Media Editing label.
3. 1933 Create a new post or page and add the Buttons block. Complete the 22 test cases for the Buttons block.
4. 1933 Try to think of a scenario that would break the buttons block and test it out. For example, try adding and removing buttons successively.
5. 2190 Create a new page, apply one of the page templates (about, blog, portfolio, services, team), make some edits, publish the page, verify the button block from the page looks correct on the web.
6. 2174 Create a new post, add a Cover block, test each of the upload options (Choose from device, Take a Photo, Take a Video, WordPress Media Library, Free Photo Library, Other Apps), and make sure each option works as expected.
7. 2127 Create a new post, add a paragraph block, type some spaces, then tap the toolbar bold button and verify the cursor stays in place.
8. 2127 Create a new post, add a paragraph or verse or pre-formatted block, type some spaces and then text, highlight the text portion, tap any of the formatting options on the menu at the bottom of the editor area, verify the whitespace does not get removed. Compare this to the web editor, does it work the same way?
9. 2156 Go to Media, upload an image, and save a caption for that image. Create a new post, add the image from before, verify that if there was a caption saved in the media library that it is pre-filled when that image is added in the editor.
10. 11757 Open a post or page in the editor and complete the 4 test cases noted in 11757 to verify the titles in the media picker are correct for each scenario.
11. 2118 Create a post or page, add a block that allows nested blocks (Columns, Buttons, Media & Text), navigate through the nested blocks and verify the FloatingToolbar is rendered on top of the screen on Android and that the Navigate-Up button is clickable.
12. 2118 Open a post or page that contains a block with nested blocks and verify the icons in FloatingToolbar are correct for RTL mode.
13. 2006 Create a new post; add heading, paragraph, pullquote, verse, and quote blocks, change the alignment for each, publish the post, verify the alignments look correct in the editor, Reader, and web.

If you are able to complete the entire list above, please continue testing by looking at all the related PRs targeting WordPress-Android 14.8 and gutenberg-mobile 1.27, 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! ❤️

+make.wordpress.org/test/

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

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

1. 2023 Create a new post or page, add any block that contains a slider (such as the spacer block), press on the slider row title, verify the row being pressed doesn’t blink when pressed. Test sliders to make sure they are still working normally.
2. 1661 Create a new post or page, add the columns block, try to break it.
   1. Complete the columns block test cases.
   2. Make sure the final published content looks good when viewed in the Reader, View Site, and on desktop browsers.
3. 18564 Create a post or page, add a column block, add new blocks using the appender in the block as well as using the (+) at bottom left and confirm both work independently as expected.
4. 2114 Create a new page using the blog page template. Customize the page and publish it. Make sure it looks good in View Site, mobile web, and on desktop browsers.
5. 2123 Start a new page and make sure you can see the page template picker buttons even when in landscape mode (you may need to dismiss the keyboard to see them depending on the device size).
6. 2086 Create a new page, select a page template so you see the template preview, rotate the device while looking at a page template before applying it and then edit or rotate back and confirm the app does not crash..
7. 11518 Create a new post or page, add some image, gallery, media & text, and video blocks using the “Choose media from device” option and make sure everything works normally. Verify the app requests permissions when necessary.
8. 11518 Create a new post or page, add any media block (image, gallery, media & text, video, etc), verify that adding media from the following sources work normally: Take a Photo, WordPress Media Library, Choose from Free Photo Library.
9. 11613 Set an RTL language (like Hebrew) and check you have the Me menu with Gravatar on the left. Long press and tap to test the functionality. Note: the Me section is the account/profile section and a Gravatar is a profile picture.
10. 11691 Go to My Site, select a site, verify the header title is “My Site”, select a different site, verify the header title stays as “My Site”.

If you are able to complete the entire list above, please continue testing by looking at all the related PRs targeting WordPress-Android 14.7 and gutenberg-mobile 1.26, 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! ❤️

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

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:

1. 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.
2. 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.
3. 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.
4. 2034 Create a new post, add a cover block, try to break it. Also see test cases.
5. 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.
6. 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.
7. 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.
8. 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.
9. 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.
10. 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! ❤️

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