Call for Testing: WordPress for iOS 14.2

WordPress for iOS version 14.2 beta is available for testing on TestFlight. You can sign up for our TestFlight program and join as a beta tester by opening that link on your iPhone or iPad.

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 Profile > App Settings > Privacy Settings and turn on the Collect information option.
  • Go to Profile > Help & Support and turn on the Extra Debug option.
  • If you are comfortable testing in a language other than English, please feel free to test in that language.

To test:

  1. Media Editing: You can now crop, zoom in/out and rotate images that are inserted or being inserted in a post. (#13309)
    1. Create a new post or page and add an image to it, or open an existing post or page with an image in it.
    2. Select the image in the post editor and then select “Edit.” (In the block editor, you will need to select the edit button that appears over the image when you select it.) Confirm the media editor opens.
    3. Try editing the image in various ways: crop, zoom in or out, and/or rotate it.
    4. Confirm the edited image looks correct in the app editor.
    5. Save your changes and preview the post. Confirm the preview shows your edited image as expected.
    6. Additional scenarios to test: Ensure editing works with the block editor enabled and disabled (My Sites > Settings > Use block editor toggle); rotate your device while editing the image; change the image settings (e.g. image link, alt text) and ensure they are retained after editing; go offline (e.g. airplane mode), edit an image, and ensure the edits are uploaded when the device is online again.
  2. Post Preview: Added a new Desktop preview mode on iPhone and Mobile preview on iPad when previewing posts or pages. (#13334) Added new navigation, “Open in Safari” and Share options when previewing posts or pages. (#13334)
    1. Go to My Sites > Site Pages or Blog Posts.
    2. Select “View” to preview a post/page (under the … menu for Site Pages).
    3. On the preview screen, confirm you see an icon in the bottom right that allows you to switch between a desktop and mobile preview.
    4. Go back to the list of posts/pages and select a post or page to open it in the editor.
    5. Open the … menu and select “Preview.”
    6. On the preview screen, confirm you see an icon in the bottom right that allows you to switch between a desktop and mobile preview.
    7. While previewing the post or page, in either desktop or mobile mode, test the other options to navigate forward/back, share, and open in Safari.
  3. Reader: Added Post Reblogging feature. You can now reblog a post from the reader to your WordPress.com site(s). (#13361)
    1. Ensure you are logged in to a WordPress.com account with at least one site hosted on WordPress.com.
    2. Go to the Reader and confirm you see a reblog button for each post, both in the Reader list view and after selecting a single post in the Reader. Tap the reblog button on a post.
    3. If you have multiple WordPress.com sites: A site selector will appear; select the site you want to reblog to.
    4. When the post editor appears, make any desired edits and publish the post.
    5. Additional scenarios: Log in to a WordPress.com account with no WordPress.com-hosted sites and confirm that when you tap the reblog button, you get a clear, actionable message (instead of being taken to the post editor); log in to a self-hosted site but not WordPress.com, and confirm no reblog buttons appear; try reblogging with and without the block editor enabled (under My Sites > Settings > Use block editor).
  4. Comment Editing: Fixed a bug that could cause the text selection to be on the wrong line. (#13316)
    1. Publish a long comment on one of your blog posts or pages.
    2. In the app, find the comment (under My Sites > Comments or in a notification on the Notifications tab). Note: A notification will only be created if you publish the comment using a different WordPress.com account.
    3. Select Edit to open the comment editor.
    4. Choose a word in the middle of the comment text and double tap that word to select it. Confirm the correct word was selected.
  5. Block Editor: Long-press Inserter icon to show options to add block before/after. (#1835) Add support for image size options in the gallery block. (#1798) Retry displaying image when connectivity restores. (#1686)
    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.
    5. Add a gallery block to your post, and add some images. With the gallery block selected, tap the settings icon and select “Images Size” to choose a size for the images in the gallery. 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.)
    6. Add an image block to your post, and choose to add an image from the WordPress Media Library. Disable your internet connection and then choose an image from the media library. Confirm the image doesn’t load. Enable your internet connection, and confirm the image eventually loads and all other editor features continue to work as expected.
  6. Comments: Fixed a bug that could cause HTML markup to be displayed in the comment content. (#13351)
    1. Publish a comment that include HTML markup on one of your blog posts or pages.
    2. In the app, find the comment (under My Sites > Comments or in a notification on the Notifications tab). Note: A notification will only be created if you publish the comment using a different WordPress.com account.
    3. Confirm you see the comment in plain text, without any HTML markup.
    4. Select Edit to open the comment editor. Confirm you see and can edit the comment in plain text, without any HTML markup.
  7. Signup and Login: Signup or login via magic link now supports multiple email clients. (#13275)
    1. Start logged out of the app.
    2. Log in or sign up to WordPress.com using the magic link option.
    3. After tapping “Open Mail,” confirm that it either opens Apple Mail (if that is your only mail app) or you see a list of your mail apps (if you have multiple apps installed) and can choose which app to open.
    4. Confirm the correct app is opened and you can continue logging in/signing up as expected.
  8. Posts: Fixed a bug that could disable comments on a draft post when previewing that post. (#13362)
    1. Go to My Sites > Settings > Discussion > confirm the Allow Comments setting is enabled (toggled on).
    2. Start a new post. Add some content and save the post as a draft.
    3. Tap to edit the draft. Add some new content and then preview the draft.
    4. Publish the post. View the post and confirm comments are enabled.
    5. Go to My Sites > Settings > Discussion > toggle off the Allow Comments setting. Repeat steps 2-4 and confirm comments are disabled.

You can find all other changes/fixes and details in the related PRs targeting WordPress-iOS 14.2 and gutenberg-mobile 1.22.

Where to Report

  • WordPress-iOS 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 > Activity Logs > Current and use the share 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 Activity Logs 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! ❤️

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

X-post: Get Involved Table at WordCamp Asia 2020

X-post from +make.wordpress.org/community: Get Involved Table at WordCamp Asia 2020

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 iOS 14.1

WordPress for iOS version 14.1 beta is available for testing on TestFlight. You can sign up for our TestFlight program and join as a beta tester by opening that link on your iPhone or iPad.

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 Profile > App Settings > Privacy Settings and turn on the Collect information option.
  • Go to Profile > Help & Support and turn on the Extra Debug option.
  • Go to My Site > Settings and turn on the Use Block Editor setting to enable the block editor for new posts.
  • If you are comfortable testing in a language other than English, please feel free to test in that language.

To test:

  1. 19534 Create a new post in the block editor, add any shortcode, try to break the block. Try with at least 5 randomly chosen shortcodes.
  2. 13242 In the app, open a site that has some traffic registered in the Stats section, and go to Stats > Widgets > Use this site. On the device, add the WordPress This Week widget to your Today view. Verify the widget works as expected and that the numbers match what you see when you check stats for the same site from WordPress.com using a web browser.
  3. 13236 In the app, follow any private blog that requires login to view the post. Go to the Reader and find a post from that blog, tap Visit for that post, and verify the post is displayed properly when authenticated (no on-screen error, no errors in the console). Test using all three site types: WordPress.com, Jetpack, Self-hosted.
  4. 13236 Using a WordPress.com account with a site that has an upgrade or plan, go to My Site > Settings > Advanced > Delete Site > Show Purchases, and verify that the “Show Purchases” page is displayed properly. Complete the process to delete a site and verify it worked.

You can find all other changes/fixes and details in the related PRs targeting WordPress-iOS 14.1 and gutenberg-mobile 1.21.

Where to Report

  • WordPress-iOS 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 > Activity Logs > Current and use the share 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 Activity Logs 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, #call-for-testing, #ios, #mobile

X-post: WCEU 2020 – Leave no Contributor Behind

X-comment from +make.wordpress.org/updates: Comment on WCEU 2020 – Leave no Contributor Behind

Call for Testing: WordPress for iOS 14.0

WordPress for iOS version 14.0 beta is available for testing on TestFlight. You can sign up for our TestFlight program and join as a beta tester by opening that link on your iPhone or iPad.

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. 13112 Enter any comment flow (reader, notification, comments), add some text, tap the full screen toggle button, add more text, tap the exit full screen button, enter more text, tap reply/save button.
  2. 13195 On the device, add the Today and/or the All-Time widget to the Today view. In the app, Go to Stats > Widgets > Use this site, switch to a different site, go to Stats, close the app, return to the Today view and tap a widget, tap Done to close the modal, verify the Stats view then displays the Stats for the selected site (not the widget site).
  3. 13196 On a site with high traffic, go to Stats > Widgets > Use this site, add the Today and All-Time widgets to the Today view, verify the widget numbers are abbreviated as they are in the app.
  4. 13131 With a site you haven’t accessed before or modified insights, check that the default insights list is: Latest Post Summary, Today, All-Time, Follower Totals. Tap Add stats card and check that the view is presented modally and functions as expected. Also test on iPad.
  5. 13158 Trigger some notifications and tap on them. The app should be opened correctly and should not crash.
  6. 13128 Set the Site Time Zone to a different Time Zone than the device, schedule a post, check that the displayed scheduled time matches the site’s time zone and is published on that date.
  7. 13173 Rename an image saved on your device or iCloud Drive. In the app, go to Media > + and add a new image, select ‘Other Apps’, select the renamed image, after it uploads click on the image and verify the original file name was kept (lowercased and without extension).
  8. 1669 In the block editor in the app, add an image via link, add a second image from the Media Library, close and reopen the post, verify the Image Sizes option is displayed for the image inserted from the Media Library and not for the image added via link.
  9. 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.
  10. 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.

You can find all other changes/fixes and details in the related PRs targeting WordPress-iOS 14.0 and gutenberg-mobile 1.20.

Where to Report

  • WordPress-iOS 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, #call-for-testing, #ios, #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 iOS 13.9

WordPress for iOS version 13.9 beta is available for testing on TestFlight. You can sign up for our TestFlight program and join as a beta tester by opening that link on your iPhone or iPad.

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. 13043 Swipe right over the Home or Lock screen, scroll down, tap Edit, add the All Time widget, verify the unconfigured view is displayed, go to Stats > Widgets Use this site and verify the widget displays data for the selected site and matches what is displayed in the app.
  2. 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
  3. 1628 Add an image blog, open image settings, rotate the device, dismiss the settings sheet, the app should not crash.
  4. 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.
  5. 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.
  6. 13092 On a site that has Quick Start available, go to Next Steps > Grow Your Audience > Follow other sites, complete the “Tap < Reader to continue” step and verify the hint goes away after that.

You can find all other changes/fixes and details in the related PRs targeting WordPress-iOS 13.9 and gutenberg-mobile 1.19.

Where to Report

  • WordPress-iOS 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, #call-for-testing, #ios, #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