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