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

Call for Testing: WordPress for Android 13.5

WordPress for Android version 13.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-13.5-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. 1331 Block editor: add multiple images or videos at once and check that all get added. Do any problems happen when you upload the post? How many did you add in one go?
  2. 1394 Block editor: add an image link that opens in a new tab.
  3. 1439 Block editor: try adding and removing the Media & Text block. Try to break it.

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

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

Call for Testing: WordPress for Android 13.4

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

  • Set up a Jetpack site for testing if you don’t already have one. You can use jurassic.ninja to quickly create a Jetpack testing site.
  • Go to My Site > Settings > Use Block Editor to enable the block editor for new posts.

To test:

  1. Block Editor: create and publish post several available blocks—get creative, think like a user, try to break the editor.
  2. 10536 Verify that changes to a draft or published post on self-hosted and Jetpack sites are labeled as “local changes” and are not auto-uploaded.
  3. 10536 Try previewing changes to pre-existing drafts or previously published posts on self-hosted sites and Jetpack. Previews are not supported on these types of sites so you should see a preview unavailable notice.
  4. Come up with an additional scenario to test an autosave, auto-upload, or remote preview. There have been several changes in this area.
  5. 10106 Post List: try previewing a trashed post. You should not see Edit or View buttons and you should not be able to preview before restoring the post. Note the type of site you tested.
  6. 10457 Post List: Create an unpublished revision in WP Admin, open the post in the app, select “More recent version/The version from another device”, go back without making changes, then open the post in the app again and verify the change made in WP Admin is showing in the app.
  7. 10402 Create a private draft while offline, go online, publish the post, verify the post is still private.
  8. 10536 Create a new draft then exit without saving and verify an autosave happens. Try with different site types (self-hosted, Jetpack, or WordPress.com). Note: new drafts should always be autosaved and auto-uploaded.
  9. 10557 Open an existing draft in the block editor, add an image, tap back before the upload finishes, open the post again and check the HTML and make sure you do not see a local path for the image.
  10. 10517 Create a draft on a self-hosted site, turn on airplane mode, add an image, tap Publish, turn off airplane mode, confirm the post and media are published with no errors.
  11. 14270 Block editor: select text, tap Link button, exit without adding a link, check that no link was added. Check that adding a link after that still works.

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

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

Call for Testing: WordPress for Android 13.3

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

To test with an apk, you can download wpandroid-13.3-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:

  • Set up a Jetpack site for testing if you don’t already have one. You can use jurassic.ninja to quickly create a Jetpack testing site.
  • Go to My Site > Settings > Use Block Editor to enable the block editor for new posts.

To test:

  1. Block Editor: create and publish post using all of the available blocks (Paragraph, Heading, Image, Lists, Separator, Page Break, Quote, More) and check that each one works as expected.
  2. 10497 Change your username in the app.
  3. 10468 From a Jetpack site in the app, go to Settings > Performance and try updating the options and verifying they were saved by comparing the updated settings via the web. Try from accounts with different types of plans.
  4. 10476 Check that a site with <100 published pages are ordered topologically and a site with >=100 pages are ordered chronologically.
  5. 10434 Browse as many pages in stats as you can. Does the performance seem good? Is anything extremely slow loading?
  6. 10483 Open a draft, edit title and content, close and re-open the app, make sure the title and content edits were not lost.
  7. 1200 Open the block editor, tap on the empty editor area, verify that a new empty block is created.
  8. 975 Add a caption with rich text to a video block.
  9. 1254 Open a post that has a paragraph and a video block—tap between the caption and paragraph block and make sure the keyboard stays open.
  10. 1262 Select an empty paragraph block, tap + to add a new block, the empty paragraph block should be hidden and when a block is selected then it should get replaced by the new block that is added. See other test scenarios at 16931.

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

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

Call for Testing: WordPress for Android 13.2

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

  • Create test accounts at LinkedIn, Tumblr, and Twitter for testing Sharing connections.
  • Have an Author or Subscriber user role setup for at least one test site.
  • Add some files to a WordPress.com test site and click to download them while logged out to generate some stats for testing the new File Downloads section in Stats.
  • Set up a Jetpack site for testing if you don’t already have one. You can use jurassic.ninja to quickly create a Jetpack testing site.
  • Go to My Site > Settings > Use Block Editor to enable the block editor for new posts.

To test:

  1. 10362 Go to My Site and make sure the new quick action buttons work. Check that tapping on Site Name or URL opens site preview. Log in to a test site as an author or subscriber role and note that the Pages button is not there.
  2. 10378 Go to My Site > Sharing and connect a LinkedIn, Tumblr, and Twitter account then make sure sharing works as expected. If you already had any connected, disconnect and reconnect them.
  3. 10276 Go to My Site > Blog Posts, select Everyone in the author filter, check that both list view and cards view (icon at top right) show an author name. Select Me in the author filter and check that the author name is not shown.
  4. 10411 From a WordPress.com site, go to My Site > Stats > Days/Weeks/Months/Years and scroll until you see the File Downloads card. Does everything look good? Are the numbers correct? Repeat the test from a Jetpack site and check that the File Downloads card is not there.
  5. 10425 Go to Profile and check that the following notice appears, “Notification Settings can now be found in the Notifications tab.” Find the Notification Settings in the Notifications tab and make sure they work as expected.
  6. Block Editor: create and publish post using all of the available blocks (Paragraph, Heading, Image, Lists, Separator, Page Break, Quote, More) and check that each one works as expected.

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

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

Call for Testing: WordPress for Android 13.1

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

  1. Have a publicly accessible Facebook page available, or create one, to use for testing.
  2. Go to My Site > Settings > Use Block Editor to enable the block editor for new posts.

To test:

  1. Go to View Site or My Site > Blog Posts > View to preview content and use the icon at bottom right to change to a desktop view and back again. (10326)
  2. Go to My Site > Sharing > Facebook > Connect and add a published Facebook page. (10376)
  3. Block Editor: create and publish post using all of the available blocks (Paragraph, Heading, Image, Video, Lists, Separator, Page Break, Quote, More) and check that each one works as expected.

You can more details about updates to version 13.1 in the related PRs targeting WordPress-Android 13.1 and gutenberg-mobile 1.10.

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

Call for Testing: WordPress for Android 13.0

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

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.

Noteworthy: this release contains an update to how the block editor is auto-enabled in the app—it has moved from an app-wide setting in your profile to a per-site setting in site settings.

What to Test

  1. Delete the app, do a fresh install, tap “Log in”, tap “Help” at top right and verify the app does not crash. (10302)
  2. Go to My Sites > Settings and observe the “Use block editor” setting is disabled. Open any post containing blocks. Go to My Sites > Settings and observe the “Use block editor” setting is now enabled. (10254)
  3. Go to My Sites > Settings and disable the “Use block editor” setting. Close and re-open the app. Switch sites. Switch back. Check to make sure the classic editor opens for the site where “Use block editor” was disabled when creating a new post or editing a post created with the classic editor. (10254)
  4. Try to break the “Use block editor” setting. Does it do anything you did not expect? (10254)
  5. Start a new post in the block editor. Open an existing post or draft that has content already, tap on the title, tap the + icon at bottom left, check that an “Add Block Here” indicator is shown. (1219)
  6. Open a post, select the post title, add any “non-text” block (imagevideomoreseparator, or page break), and make sure the cursor is no longer active in the post title. (1231)
  7. Open a post that has an image block in it, add a caption, select caption text and add formatting (i.e. bold), verify the image caption remains horizontally centered. (1243, gutenberg/16722)
  8. Go to Sites > Switch Site, click on the + button at top right, enter a site address and verify an error is only shown if you have not typed anything for at least 2 seconds and that the Next button is only enabled if the URL is valid. (10255)
  9. Log out, tap “Log in”, tap “Login by entering your site address”, enter a self-hosted site address and verify an error is only shown if you have not typed anything for at least 2 seconds and that the Next button is only enabled if the URL is valid. (10255)
  10. Go to Settings > General > Accessibility > VoiceOver Settings > Accessibility > TalkBack and toggle the setting on. Go to Stats and explore. Is anything broken? (10274, 10277)
  11. Browse through various screens from the app and look for any colors different from Color Studio v2.0.0 colors. (10283)

You can more details about updates to version 13.0 in the related PRs targeting 13.0.

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

Call for Testing: WordPress for Android 12.9

WordPress for Android version 12.9-rc-1 is available for testing on the Beta channel. Request 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.

Bugs & Feedback

If you find a bug or come up with a feature request while testing, you can comment here, or 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

  1. From the Reader or from the My Site > Comments > Comment Detail screen, use the expand/collapse icon to expand the view when editing a comment. (10140)
  2. Block editor: add a video block to a post and try to break it. (1150)
  3. Block editor: on the web, create a group block as described at 1206 or use the sample content noted in 1209 then open the post in the app and make sure no content is lost.

You can more details about updates to version 12.9 in the related PRs targeting 12.9 and 1.9.

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

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

Call for Testing: WordPress for Android 12.8

WordPress for Android version 12.8-rc-1 is available for testing on the Beta channel. Request 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.

Bugs & Feedback

If you find a bug or come up with a feature request while testing, you can discuss it here, 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

  1. Using 12.8-rc-1 or later, go to Me > App Settings > Use Block Editor to enable Gutenberg Mobile for testing on new posts. Posts created using Gutenberg on the web should open in Gutenberg on the app regardless of what is selected in App Settings.
  2. Widgets for All-time, Today, Weekly Stats are now available for your device home screen. (10122)
  3. Block editor: Open the editor (a new post or existing post), select the Post Title field, delete any existing title content, and paste some text inside the empty Post Title. Check that pasting works as expected. Press Enter and check that it creates a new block and that gets focus as expected. (16116)
  4. Under My Sites > Stats in the Posts and Pages, Authors, Tags and Categories sections, a percentage bar has been added to graphically show the impact of each item. (10073)
  5. On a site using Jetpack, go to My Sites > Blog Posts and tap the search button. Try different searches and confirm that the search results work as expected. (10023)

Find all other changes/fixes and details in the related PRs targeting 12.8 and 1.8.

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

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

Call for Testing: WordPress for Android 12.7

WordPress for Android version 12.7-rc-1 is available for testing on the Beta channel. Request 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.

Bugs & Feedback

If you find a bug or come up with a feature request while testing, you can discuss it here, 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

  1. Using 12.7-rc-1 or later, go to Me > App Settings > Use Block Editor to enable Gutenberg Mobile for testing on new posts. Posts created using Gutenberg on the web should open in Gutenberg on the app regardless of what is selected in App Settings.
  2. Turn on airplane mode, create a local draft, turn off airplane mode, check to make sure an upload post system notification appears. (9956)
  3. Create a post with title + content, tap overflow menu > Save as draft, press Up button (arrow) before the upload finishes, make sure the app doesn’t create two drafts. (10009)
  4. Follow “Test Steps” in WordPress/pull/9783 to see that there is no scroll bleed on the themes screen. (9783)
  5. Block Editor: press Enter repeatedly on the Post Title, there should not be any keyboard flickering. (1076)
  6. Block Editor: add a quote block and try to break it. (207)
  7. Block Editor: add a more block and try to break it. (859)
  8. Block Editor: create and publish post using all of the available blocks (Paragraph, Heading, Image, Lists, Separator, Page Break, Quote, More) and check that each one works as expected.

Find all other changes/fixes and details in the related PRs targeting 12.7 and 1.7.

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

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