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

Call for Testing: WordPress for Android 14.4

WordPress for Android version 14.4-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.4-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. 11378 Turn on airplane mode, create a draft, add an image, click on Back, create another draft, add the same image, click on Back, turn off airplane mode, wait until uploads complete, open second post, switch to HTML mode, make sure the image is not using a local path. Test with and without the block editor turned on.

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

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 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 (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

Call for Testing: WordPress for Android 14.2

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

  • If you are comfortable testing in a language other than English, please test in that language.

To test:

  1. Block editor: Long-press Inserter icon to show options to add block before/after. (#1835)
    1. Start a new post and confirm that the block editor is enabled by default. Optional: Add some content to your new post.
    2. Long press on the “Add Block” icon in the editor toolbar, and confirm an action sheet appears with options about where to add the block:If no block or the title is selected, the options should be “Add to beginning” and “Add to end.”
    3. If a block is selected, the options should be “Add Block Before” and “Add Block After.”
    4. Make a selection and confirm the block picker comes up and your selected block is added in the correct place.
  2. Block editor: Add support for image size options in the gallery block. (#1798)
    1. Add a gallery block to your post, and add some images.
    2. With the gallery block selected, tap the settings icon and select “Images Size” to choose a size for the images in the gallery.
    3. Preview the post and confirm your images appear with the correct size. (You may need to preview the post on a desktop browser to confirm the size.)
  3. Block editor: Retry displaying image when connectivity restores. (#1686)
    1. Add an image block to your post, and select “WordPress Media Library” as the image source.
    2. Disable your internet connection and then choose an image from the media library. Confirm the image doesn’t load.
    3. Enable your internet connection, and confirm the image eventually loads.
    4. Confirm all other editor features continue to work as expected.
  4. Block editor: Fix retry media upload action. (#11237)
    1. Add an image block to your post, and then disable your internet connection.
    2. Select “Choose from device” and select an image. Notice the upload failure message.
    3. Enable your internet connection, tap the image, and retry the image upload.
    4. Confirm the image upload is restarted and the image is successfully uploaded.
  5. Block editor: Fix blank post when sharing media from another app. (#11121)
    1. Go to My Sites > Settings and confirm “Use block editor” is enabled.
    2. Open a different app on your device that contains photos or videos.
    3. Select a photo or video and share it to the WordPress app.
    4. Confirm that WordPress opens and the photo or video was successfully uploaded and is visible in the app.
    5. Repeat the same steps, sharing links from your device web browser or from another app (e.g. YouTube, Twitter). Confirm the editor is opened and includes a clickable link.
    6. Repeat the same steps, but with the “Use block editor” setting disabled.
  6. Block editor: Fix issue that sometimes prevented merging paragraph blocks. (#1867)
    1. Add a paragraph block and add some text to it.
    2. Tap in the middle of the text and hit enter to move the right half of the text to a new block.
    3. Hit backspace and watch the new block merge back correctly with the previous block.
    4. Hit enter from the middle of the text again to create a new block.
    5. This time delete one or more characters from the beginning of the new text block.
    6. Continue to hit the backspace key and confirm the new block is merged back with the previous block.

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

Call for Testing: WordPress for Android 14.1

WordPress for Android version 14.1-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.1-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 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. 11098 Start with a fresh installation so there are no posts in the DB, use a WordPress.com site for testing, go to My Site > Posts (do not scroll at all), type a search query for a very old post or for a post in the trash. Verify that the same search returns the same results using WordPress.com/sites > Posts > Search.
  2. 11099 Go to My Sites > Switch Site, tap and hold a Jetpack or Atomic site, verify that the “Remove Site” dialog is not shown and instead you are able to show/hide the site instead. Repeat the steps for a WordPress.com and a Self-hosted site and verify that only the Self-hosted site gets the option to “Remove site”.
  3. 19534 Create a new post in the block editor, add any shortcode, try to break the block. Try with 5 randomly chosen shortcodes.
  4. 992 Open a post that has many blocks and verify the padding between blocks isn’t unreasonably large.
  5. 10505 Create a post with 500-1,000 paragraph blocks, quickly scroll through the post for a while, verify you cannot crash the app even after a minute or so of scrolling. (53s)
  6. There is an open-ended ask to test every area of the editor with both and without the block editor turned on. A lot of changes to the saving/uploading logic were made which basically touched everything in the editor. Please test creating a few new posts and publishing them, at least one while you are online and one while you are offline plus one that’s scheduled to publish at a later time.

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

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

Call for Testing: WordPress for Android 14.0

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

To test with an apk, you can download wpandroid-14.0-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 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. 1631 On the web, create a draft with aligned images. In the app, open an empty post (to load the js from the metro bundler), go to Blog Posts > Drafts, turn on airplane mode, open the draft, make sure images have placeholder images.
  2. 1701 In the block editor in the app, add a paragraph block, type some characters, undo changes until the block is removed. Repeat if necessary. App should not crash.
  3. 11074 Check that the profile icon is at top right and no longer in the bottom menu. Tap on the profile icon, make sure everything loads normally, tap the back arrow, make sure you are taken back to the My Site screen.
  4. 11074 Go to My Site and tap the “+” button at bottom right to open a selector, the tooltip should go away at that point, select one of the options, make sure editor opens, create a post/page and tap on the back arrow, confirm you are taking back to the main screen and you see a notice that the post was saved, check the new created post or page was created and available in the correct list (Published/Draft).
  5. 11074 Create a new site from the app and tap Accept on the dialog below to get access to the Quick Start tutorials. Go through the tutorials and check that everything works as expected, especially the Publish Post step.
  6. Last, there is an open-ended ask to test every area of the editor with both Aztec and Gutenberg. A lot of changes to the saving/uploading logic were made which basically touched everything in the editor.

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

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.

Thanks for testing! ❤️

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

Call for Testing: WordPress for Android 13.9

WordPress for Android version 13.9-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-13.9-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 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. 1498 Add a gallery block to a post or page and try to break it: add images, remove images, change the number of columns, crop images, add captions, rotate the device while interacting with the block
  2. 1615 Add a preformatted block to a post or page and used some text with various types of white space. Add another preformatted block and merge the two blocks.
  3. 1619 Add a list block, change it to an ordered list (numbered), change the start value of the list and make the numbering go in reverse order.
  4. 1601 Add a video block, tap on the settings icon (cog), change each one of the video settings, save changes, and verify the settings are each working as expected.
  5. 10717 From a WordPress.com site that has a domain credit available, start the domain registration process, pick a domain that you know is not available, verify you see an error if the domain is taken or invalid.
  6. 10833 Go to My Sites > Switch Site > + > Add self-hosted site, enter an address, when you see the username and password prompt minimize the app and wait an hour then go back to the app and verify the app does not crash.
  7. 10833 Go to the Log In screen and input incorrect credentials, minimize the app, go back to the app and verify you can log in using the correct credentials.
  8. 10479 Add a QuickPress widget, switch to a different blog in the app, click on the widget. The app should not crash.
  9. We improved accessibility via TalkBack in Sign up and login, the editor and the empty view screens. If you are a TalkBack user, please tell us if this helps you navigating the app.

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

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.

Thanks for testing! ❤️

#13-9, #android, #call-for-testing, #mobile

Call for Testing: WordPress for Android 13.8

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

What to Test

To prepare:

  • 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. 10817 Add a spacer block to any post. Try to break it. View results on various screen sizes, including desktop, and make sure the block works as expected.
  2. 10837 Go to My Sites > Blog Posts and search for various posts including published, drafts, scheduled, and trashed. Can you find what you’re looking for?
  3. 10763 Add images and videos to any post or page. Try rotating the screen during editing. Switch to HTML during editing. Try with both the classic and block editors. Leave the editor then edit again and make sure media appears as expected. See additional testing ideas here.
  4. Create and publish a new post with as many blocks as possible.
  5. Try tapping on push notifications to launch the app, does it crash?
  6. There were 26 unique crash and bug fixes included in this release! In general, can you figure out any ways to crash the app?

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

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.

Thanks for testing! ❤️

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

Call for Testing: WordPress for Android 13.7

WordPress for Android version 13.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-13.7-rc-1-universal.apk from here.

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 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. 1533 On the web, create and publish a post with as many different block types as you can. Open the post in the mobile app and check that the titles of the blocks are accurate.
  2. 1542 Start a new post, tap the “+” button to insert a new block, and confirm you can see the “Add New Block” indicator when there are no blocks at all and when at the last block.
  3. 1537 Copy a URL from Safari or elsewhere, select some text in a post, tap the link button, confirm that the URL field is automatically populated using the link from the clipboard. Edit an already existing link and check that the link in the clipboard does not override the one already existing. Try adding a few other links in different ways.
  4. 1546 Add the Media & Text block and test vertical alignment options.
  5. 1577 Selecting an image block should show a blue border and you should be able to press the image to see a full-screen preview.
  6. 1582 Add and remove empty blocks a few times in a row and try to crash the app.
  7. 10788 Edit an existing post on the web, wait for an autosave, and close the browser tab without saving—then open the post in the app and confirm the dates in the conflict resolution dialog are accurate according to your device timezone. Follow up at 10773 too.

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

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.

Thanks for testing! ❤️

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

Call for Testing: WordPress for Android 13.6

WordPress for Android version 13.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-13.6-rc-1-universal.apk from here.

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 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. 10713 Check as many different screens as possible and look for the bottom navigation color to be white (limited to Android 8.1+).
  2. 10708 Verify that page ordering is now case insensitive.
  3. 1469 Try adding images using the “Choose from Free Photo Library” and “Choose from Giphy” option and make sure the images are added and appear as expected in previews and after publishing the post. Test adding an image in a post or page as well as as a featured image.
  4. 1460 Add several images in different ways to a post and pick different alignments. Check that image alignments made in the block editor on mobile are reflected on the web from a laptop and vice versa.

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

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.

Thanks for testing! ❤️

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