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

WordPress for iOS version 13.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 My Site > Settings > Use Block Editor to enable the block editor for new posts.

To test:

  1. (12234) Go to Profile > Account Settings, tap username, change the username. Note: if the user is an A8C user you shouldn’t be able allowed to change it.
  2. (12275) Go to Stats > Days/Weeks/Months/Years and verify there is a File Downloads and it has data if downloads have happened on the site you are working with. Disable your network and verify File Downloads still has data.
  3. (12273) Open an existing draft and ensure the ... menu doesn’t show a Stats item and does show a Publish Now item. Make sure Publish Now and all of the other items work as expected.
  4. 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.
  5. [UPDATED] Go to Profile > Help & Support and test the Contact Us form. Try sending logs both as an attachment and via copy/paste. (12107)

You can find all other changes/fixes for this release in the related PRs targeting 13.1.

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-1, #call-for-tesitng, #ios, #mobile

Call for Testing: WordPress for iOS 13.0

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

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

To prepare:

  • Completely uninstall and re-install the app so that you have a fresh install of the app.

To test:

  1. 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. (12066)
  2. 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. (12066)
  3. Try to break the “Use block editor” setting. Does it do anything you did not expect? (12066)
  4. 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)
  5. 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)
  6. Start with a site with the timezone set a day ahead of your local timezone. Go to My Sites > Stats > Days/Weeks/Months/Years and check that a “Site timezone” label appears showing the offset from UTC.(12159)
  7. Go to My Sites > Stats > Days/Weeks/Months/Years and verify changing the date via the bar or the chart works as expected and matches the same view from Calypso (especially the Days view). (12159)
  8. Go to My Sites > Stats > Insights and verify Today shows today’s stats. Go to Year > View more and verify the date bar behaves as expected. Verify the Latest Post Summary chart is correct. (12159)
  9. Go to My Sites > Stats > Latest Post Summary and click a post to open post stats and verify the date and chart behaves correctly and that the chart data is correct. (12159)
  10. Go to My Sites > Settings and change the site timezone. Go to My Sites > Stats and verify the date bar is updated accordingly. (12159)

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

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-0, #call-for-tesitng, #ios, #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 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 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 iOS 12.5

WordPress for iOS version 12.5 beta is available for testing on TestFlight.

Not part of the beta program yet? Please sign up for our TestFlight program (open the link on your iPhone or iPad) to join as a beta tester.

Release Notes

  • Fixed Notices sometimes showing behind the keyboard.
  • Implemented auto saving a post on preview.
  • The app now launches a bit more quickly.
  • Fixed a crash for Reader comments with multiple gifs.

What to Test

  1. Notices. (11632)
    1. Go to Blog Posts, tap Search to trigger keyboard, go offline, pull to refresh. You should see an offline notice appear.
  2. Autosave before Preview on published posts. (11638)
    1. On a WordPress.com blog, make a change to a previously published post and ensure you can see the change in a preview.
  3. Reader comments with multiple gifs. (11698)
    1. Find some posts with lots of comments and like them. (1, 2)
      In the app, go to Reader > My Likes.
      Tap to view comments for one of the liked posts.
      Quickly scroll the list.
      Repeat until you crash the app.
  4. Gutenberg Mobile (1.5)
    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. 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. Add an image with a centered caption that contains rich text such as bold, italic, link, and strikethrough. (941)

Find all other changes/fixes in the related PRs targeting 12.5 and 1.5.

Bugs & Feedback

Did 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, report it using the TestFlight feedback link, or head straight to the iOS GitHub repository and open a new issue or the Gutenberg Mobile repository to open a new issue for the block editor.

Thanks for testing!

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

Call for Testing: WordPress for iOS 12.4

WordPress for iOS version 12.4 beta is available for testing on TestFlight.

Not part of the beta program yet? Please sign up for our TestFlight program (open the link on your iPhone or iPad) to join as a beta tester.

Release Notes

  • You can now mark notifications as unread with just a swipe.
  • Fixed a crash when searching the Free Photo Library.
  • Fixes issues some folks were having logging into a self-hosted site.
  • Account Settings Primary Site now shows the site URL if the site has no name.
  • Improves how quotes look in reader.
  • Made small improvements to accessibility across the app.

What to Test

  1. Notifications (PR #11573):
    1. Go to Notifications and find a read notification. Swipe left-to-right and confirm it is marked as unread.
    2. Swipe left-to-right on an unread notification and confirm it is marked as read.
    3. Open the same WordPress.com account in a browser and check the read state is reflected on the notification there. Note that you may need to reload the page to see your changes on the app take effect.
  2. Free Photo Library (PR #11550):
    1. On a site hosted on WordPress.com or using the Jetpack plugin, access the Free Photo Library. (To access it, go to My Sites > Media > + > Free Photo Library, or disable the block editor in App Settings > Start a new post > Add media > tap 3-dot menu > Free Photo Library.) Perform searches that have no results. Verify it doesn’t crash.
  3. Self-hosted Site Login:
    1. Start login using a site address, or if already logged in go to My Sites > Switch Site > + > Add self-hosted site. Enter an invalid URL (e.g. example with no domain ending) or a URL for a non-WordPress site and tap Next. Confirm an error message appears under the site address field. (PR #11563)
    2. Enter a valid self-hosted site URL (with or without a prefix) and confirm you can log in as expected. (PR #11639)
  4. Account Settings Primary Site (PR #11577):
    1. Log in to WordPress.com in the app and confirm you have at least one site hosted at WordPress.com. If you have multiple sites, go to Account Settings > Primary Site to identify your primary site.
    2. Go to My Site (selecting your primary site) > Settings > Site Title and remove the site title. Go to Account Settings > Primary Site. Verify the URL is displayed.
    3. Go to My Site (selecting your primary site) > Settings > Site Title and give the primary site a title. Go to Account Settings > Primary Site. Verify the Title is displayed.
  5. Reader Quotes (PR #11401):
    1. Find a post or comment in the Reader that includes a block quote. (You can create a post/comment with a quote if needed.) Confirm that the quote appears with a left border (line).
  6. Accessibility (PR #11578):
    1. Go to Settings > General > Accessibility > VoiceOver and toggle the setting on.
    2. If you already have a site with Quick Start (the “Next Steps” section at the top of My Sites), go to that site, double tap on “Customize Your Site”, and skip to step 6.
    3. If you don’t have a site with Quick Start, go to My Sites > Switch Site > + > Create WordPress.com site.
    4. Follow the site creation prompts until you reach “Want a little help getting started?”
    5. Double tap the “Yes, Help Me” button.
    6. Try interacting with any of the cells on the “Customize Your Site” screen. Confirm that VoiceOver reads the text/accessibility hints as expected as you go through the tour.
  7. Find all other changes/fixes in the related PRs targeting 12.4.

Bugs & Feedback

Did 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, report it using the TestFlight feedback link, or head straight to the iOS GitHub repository and open a new issue.

Thanks for testing!

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