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

WordPress for iOS version 13.6 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. Offline Support Check that posts created while offline are updated when you go back online. Test with WordPress.com, Jetpack, and Self-hosted sites.
  2. Offline Support Edit a published post while offline and check that the changes are synced properly when you go back online. Test with WordPress.com, Jetpack, and Self-hosted sites.
  3. Offline Support Edit and existing draft and publish it while offline and make sure the changes are visible in the published post when you go back online. Test with WordPress.com, Jetpack, and Self-hosted sites.
  4. Offline Support In general, if you make changes to a post or page while offline, do the changes get uploaded or published as expected when you go back online? Try to break autosave or auto-uploads.
  5. Offline Support Try changing post settings for any post while offline and check that the changes are updated or published as expected when you go back online.
  6. 12814 Log out of the app.. Add a self-hosted site. Go to the Profile page (Me) and verify it is not blank.
  7. 12670 While offline, edit an existing pending for review or scheduled post, make some changes, tap X and update the post. Verify the post is still pending or scheduled and was not published.
  8. 1460 Add several images in different ways to a post and pick different alignments. Check that image alignments made in the editor on mobile are reflected on the web from a laptop and vice versa.

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

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

Call for Testing: WordPress for iOS 13.5

WordPress for iOS version 13.5 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. 12286 Block editor: Long-press/3D touch on the app icon, select the “New Photo Post” option to add an image to a new post.
  2. 1394 Block editor: Add an image link that opens in a new tab.
  3. 1415 Block editor: Switch to light mode, add a List block, write some text on it, switch to dark mode, delete the text and write new text, check that the text color is white.
  4. 1439 Block editor: try adding and removing the Media & Text block. Try to break it.
  5. Various Pick any dark mode update from here and test it to make sure it’s working as expected.
  6. 12243 Go to Stats > Insights and rearrange the cards. Look through the stats to make sure everything looks okay. Close and re-open the app and make sure the custom order is preserved.
  7. 12711 On a slow network connection, check that Stats Insights loads reasonably fast.

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

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-5, #call-for-testing, #ios, #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 iOS 13.4

WordPress for iOS version 13.4 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 your native language is not English or if you are comfortable testing in another language you are proficient in, please test in that language.

To test:

  1. Block Editor: create and publish post several available blocks—get creative, think like a user, try to break the editor. For example, try adding several images at once while offline then go online.
  2. Test that you can receive push notifications, notifications in-app, and email notifications for likes, comments, and follows.
  3. 12552 Sign In With Apple: log in with SIWA, open app switcher (double tap home button), select iOS settings, disconnect Apple account(Settings > Password & Security > Apps Using your Apple ID > WordPress > Stop Using Apple ID), go back to the WordPress app—verify you are logged out and the following message appears in app logs “Apple credentialRevokedNotification received. User signed out.”
  4. 12585 Sign In With Apple: log in with SIWA, background the app, disconnect your Apple account on the device (Settings > Password & Security > Apps Using your Apple ID > WordPress > Stop Using Apple ID), open the app—verify you get logged out.
  5. 12606 Sign In With Apple: login/signup with SIWA using an email that matches a WP account, log out and log in with SIWA again, verify the email address is displayed on the password entry view.
  6. 12637 Like some posts in the Reader using dark and light mode.
  7. 12616 Check that popup menus for headings and lists have a dark background in Aztec.
  8. 12610 Log out and when you log back in make sure the spinner at bottom right is visible while logging in.
  9. 12590 Open an individual post in the Reader, minimize the app, and verify the app doesn’t crash.
  10. 12590 Put the app in the background and switch from light to dark mode (or vice versa), re-open the app, make sure the colors look correct and that buttons and content is generally readable.
  11. 12560 Browse comments, pending comments, edit a comment, resize/crop your Gravatar, and view the country map in stats to make sure all of those things look good in dark mode.
  12. 12560 Share content from Safari to the WordPress app, add enough content so it goes behind the keyboard, try to scroll.
  13. 12575 Create a document in iA Writer, tap the share icon at the bottom, select “New Draft on WordPress” (a custom iA Writer action, NOT the WP sharing extension), verify the link opens in Safari.
  14. 1382 Block editor: check if links in content are tappable without opening a Safari instance on iOS 13.
  15. 14270 Block editor: select text, tap Link button, exit without adding a link, check that no link was added. Check that adding a link right after that still works.

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

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-4, #call-for-testing, #ios, #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 iOS 13.3

WordPress for iOS version 13.3 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.

To test:

  1. 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.
  2. Try uploading images in different ways in a few different posts.
  3. 12452 Open the app and publish a post, close the app and go offline, edit the post to add an image, go back online, tap “Update”, and verify the image updates properly and looks good in previews and the web.
  4. 1305 (requires iOS 13) Create a new post and check that HTML mode works normally in the block editor.
  5. 12540 (requires iOS 13) Open the Reader, on the device go to Settings > Display & Brightness and change the appearance (light to dark or vice versa), check that the app looks correct, put the app in the background, change the appearance again (light to dark or vice versa), check that the app still looks correct.
  6. 12521 (requires iOS 13 and an iPad) Open the Profile (Me) section in the app, switch to a different app, go back to the WordPress app, make sure the appearance is not split between light and dark modes.
  7. 12338 (if you have a pending iOS update) Open the app and log in, leave the app open for a while, update iOS, then open the app again and please let us know in the comments if you find the app crashing at all. 🙇‍♀️

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

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

Call for Testing: WordPress for iOS 13.2

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

An important update in this release is the introduction of the option to Sign In with Apple in preparation for the release of iOS 13. 🎉

Disclaimer: iOS 13 is currently in beta. Beta software refers to a version of software that is still under development and is not yet released to the public. Make sure to back up your devices before installing beta software and install only on devices and systems that you are prepared to erase if necessary. If you do not have a device you would like to use, feel free to skip the steps that require iOS 13 (there are just two at the end of the list).

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 a new Apple ID with two-factor authentication enabled to use for testing.
  • 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, Video, Lists, Separator, Page Break, Quote, More) and check that each one works as expected.
  2. 12377 Go to My Site and pull to refresh many times to try to get duplicate sites to show. If you can see duplicates, either pull to refresh or wait for a bit for the site to sync and the duplicates should go away.
  3. 12287 Go to Profile and notice the Notifications Settings option is no longer there. Go to Notifications and tap the cog icon at top right. Make some changes to your notifications settings and ensure they work as expected.
  4. 12363 Go to My Site > Settings > Time Zone and choose a timezone other than your device timezone and not UTC. Go to My Site > Stats > Days and make sure the site timezone setting is displayed correctly.
  5. 12303 Create a new post, add a title, add an image, save as a draft, go to More > Preview and make sure the image loads in the preview.
  6. 12107 Go to Profile > Help & Support and test the Contact Us form. Try sending logs both as an attachment and via copy/paste.
  7. 12305 Log out, tap “Log in”, a button view should appear with the following options: “Continue with Apple” (only if you have iOS 13), “Continue with WordPress.com”, “Continue with Google”, and “Or log in by entering your site address.” Check that each login flow works as expected.
  8. 12336 (requires iOS 13) Log out, tap “Log In”, select “Continue with Apple” and follow the prompts to Sign In With Apple.
  9. 12379 (requires iOS 13) Go to Settings > Display & Brightness and tap Dark to switch to Dark Mode. Browse around in the app. Does anything look wrong when in Dark Mode? Try editing a few posts that contain blocks using the block editor and a few posts without blocks using the default editor. Please post general Dark Mode problems/screenshots to the comments on 12320.

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

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