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

WordPress for iOS version 12.9 beta is available for testing on TestFlight. You can sign up for our TestFlight program (open the link on your iPhone or iPad) to join as a beta tester.

Bugs & Feedback

If you find a bug or come up with a feature request while testing, you can let us know in the comments, 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. Be offline, go to Blog Posts > Published or Drafts, tap the “Create Post” button, you should see a save draft option when exiting and the post should then be created as a draft and queued for upload. (12023)
  2. Block editor: add a video block to a post and try to break it. (1150)
  3. Block editor: open any post with the block editor, tap on the empty editor area, a new paragraph block should be added. (1200)
  4. Block editor: open a post with at least one block in the content area, tap the Title, add any block, make sure the new block is added at the top of the post. (1201)
  5. Block editor: open a post with at least one block in the content area, make sure no block is selected, add any block, check that a new block should be added to the bottom of the post. (1201)
  6. Block editor: open a post with at least one block in the content area, make sure an existing block is selected, add any block, see that a new block is added below the previously selected block. (1201)
  7. 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.
  8. Go to Blog Posts and observe there is a new compact layout option. Try to find any problems you can with the Blog Posts screen. (12087)
  9. Go to Blog Posts and check that the post list matches the mockups in 11646. (12087)
  10. Go to My Sites > Switch Site > “+” (at top right) > “Create WordPress.com site”, follow the prompts until you see a site preview, make sure you can scroll all the way down to the bottom of the site and the “Done” button doesn’t block the site view. (12052)
  11. Go to My Sites > Switch Site > “+” (at top right) > “Create WordPress.com site”, accept help when offered assistance, in “Customize Your Site” tap “Upload a site icon” and make sure it behaves well. Try it multiple times in a row. (12051)
  12. Using a very poor network connection, go to Blog Posts > Published, open a post, update it, tap “Preview”, you should see “Generating Preview” in the nav bar. Make sure you can exit the editor and perform other actions. After exiting, the nav bar in the editor should go back to its previous state and no longer say “Generating Preview”. (12031)

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

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

#12-9, #call-for-testing, #ios, #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 iOS 12.7

WordPress for iOS version 12.7 beta is available for testing on TestFlight. You can sign up for our TestFlight program (open the link on your iPhone or iPad) to join as a beta tester.

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. 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. Block Editor: create and publish post using all of the available blocks (Paragraph, Heading, Image, Lists, Separator, Page Break, Video, Quote, More) and check that each one works as expected.
  3. Block Editor: add a video block and try to break it. (687)
  4. Block Editor: add a quote block and try to break it. (207)
  5. Block Editor: add a more block and try to break it. (859)
  6. Block Editor: copy text with attributes (bold, italic, etc.) from another app (e.g. Notes), paste it into a text block (paragraph/list/quote), attributes should not be lost. (1097)
  7. Block Editor: check that the default body text in text blocks (paragraphs/lists/quotes) are now using the updated color scheme: gray-900 for text and blue-500 for links. (1086)
  8. Block Editor: add a list block, try to use the indent and outdent buttons and see if they work correctly, try to delete list items and see if it works correctly. (991)
  9. Block Editor: try the testings steps at gutenberg-mobile/issues/874.
  10. Post Settings: go offline, go to Posts, open a post, go to Post Settings, try to set a featured image, and verify the app lets you do that even when offline. (11895)

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

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

#12-7, #call-for-testing, #ios, #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

Call for Testing: WordPress for iOS 12.6

WordPress for iOS version 12.6 beta is available for testing on TestFlight. You can sign up for our TestFlight program (open the link on your iPhone or iPad) to join as a beta tester.

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.

Please pay extra attention to testing Stats Refresh for this release! 🙏

What to Test

To prepare:

  • 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.

To test:

  1. Block Editor: create and publish post using all of the available blocks (Paragraph, Heading, Image, Lists, Separator, Page Break) and check that each one works as expected.
  2. Stats Refresh: test using a non-English device language (including RTL).
  3. Stats Refresh: test Stats on a brand new site.
  4. Stats Refresh: test Stats on a site with a lot of traffic.
  5. Stats Refresh: make sure cells animate as expected when expanding/collapsing them.
  6. Stats Refresh: when a different time period is selected, ensure all modules are updated as expected. This includes switching between Days, Weeks, Months, Years but also choosing a specific day/week/month/year in the graph.
  7. Stats Refresh: check that the data returned in stats graphs match the data returned in other modules.
  8. Stats Refresh: check that all types of data are returned for each module (e.g. all post types are returned for Posts & Pages).
  9. Stats Refresh: check that the “View All” option appears when/where expected and leads to the expected screen. Be sure to test with the current time period (e.g. current day) and past time periods (e.g. previous day).
  10. Stats Refresh: tap on a post or page to go to the post/page stats detail.
  11. Stats Refresh: tap on a referrer or click and verify the links open properly.
  12. Stats Refresh: change the dates displayed using the date bar at the top of Days/Weeks/Months/Years and on individual posts.
  13. Stats Refresh: check the Views per day for Insights > Latest Post Summary then tap View more to go to individual posts stats.
  14. Block Editor: on the web add a block with invalid content—or this sample content—then open the post in the app and verify blocks with invalid content says “Problem displaying block”. (1021)
  15. Block Editor: create and publish a new post with a link set to “Open in New Tab” in the block editor. Close and re-open the link settings and verify the setting is still correct. (1030)
  16. Share 4 or more images to the share extension and publish. (11780)
  17. Share a TextBundle that includes 4+ images (from Bear, likely). (11780)
  18. Go to Site Settings > Site Title and change the Web Address to something custom (other than the domain) and delete the Site Title. Go to Account Settings > Primary Site and verify it is not empty and the domain is displayed (instead of the Web Address). (11803)
  19. Go to Me > App Settings > About WordPress for iOS and verify Acknowledgements is present. Does anything look amiss? (11776)
  20. Turn on airplane mode, go to comments, reply to a comment, verify you see a snack bar message saying “There has been an unexpected error while sending your reply.” (11817)

Find all other changes/fixes in the related PRs targeting 12.6 and 1.6.

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, especially anything stats-related!, or issues you’re not sure how to report in GitHub.

Thanks for testing! ❤️

#12-6, #call-for-testing, #ios, #mobile

Call for Testing: WordPress for Android 12.6

WordPress for Android version 12.6-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.6-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. Create and publish post using all of the available blocks (Paragraph, Heading, Image, Lists, Separator, Page Break) and check that each one works as expected.
  3. On the web, add a block with invalid content—or use this sample content—then open the post in the app and verify blocks with invalid content say “Problem displaying block”. (1021)
  4. Create and publish a new post with a link set to “Open in New Tab” in the block editor. Close and re-open the link settings and verify the setting is still correct. (1030)
  5. Go offline, create a local draft, go online, verify local drafts have been updated. (9902)

Find all other changes/fixes and details in the related PRs targeting 12.6 and 1.6.

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