Call for Testing: WordPress for iOS 14.7


WordPress for iOS version 14.7 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 Account > App Settings > Privacy Settings and turn on the Collect information option.
  • Go to Account > Help & Support and turn on the Extra Debug option.
  • 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. 13812 Create a new post, tap Publish, change the post date to something in the past or future, change the visibility, add tags, tap “Publish Now”.
    1. Test in portrait and landscape.
    2. Try to break the flow.
    3. Update More > Post Settings and verify the changes are reflected in the Publish bottom sheet.
    4. Change the publish date more than once.
    5. Change the publish date when the device timezone is set to something very different from the site timezone.
    6. Test from a WordPress.com site.
    7. Test from a Jetpack site.
    8. Test from a Self-hosted site.
    9. Verify all changes you make take effect once the post has been published.
  2. 1661 Create a new post, add the columns block, try to break it.
    1. Complete the columns block test cases.
    2. Make sure the final published content looks good when viewed in the Reader, View Site, and on desktop browsers.
  3. 18564 Create a post, add a column block, add new blocks using the appender in the block as well as using the (+) at bottom left and confirm both work independently as expected.
  4. 2114 Create a new page using the blog page template. Customize the page and publish it. Make sure it looks good in View Site, mobile web, and on desktop browsers.
  5. 2123 Start a new page and make sure you can see the page template picker buttons even when in landscape mode (you may need to dismiss the keyboard to see them depending on the device size).
  6. 2086 Create a new page, select a page template so you see the template preview, rotate the device while looking at a page template before applying it and then edit or rotate back and confirm the app does not crash..
  7. 13926 Go to My Site, select a site, verify the header title is “My Site”, select a different site, verify the header title stays as “My Site”.
  8. 13904 Log in using the “entering your site address” option from as many places you can find. Here are 3 examples:
    1. Log out, tap “Log in”, tap the “entering your site address” link text, confirm you are navigated to a screen that asks for the site address.
    2. Log out, tap “Log in”, tap “Continue with WordPress.com”, tap the “entering your site address” link text, confirm you are navigated to a screen that asks for the site address.
    3. Log in with any method, go to Switch Site > + > Add self-hosted site, confirm you are navigated to a screen that asks for the site address.

If you are able to complete the entire list above, please continue testing by looking at the related PRs targeting WordPress-iOS 14.7 and gutenberg-mobile 1.26. Test any that you are able to and that aren’t already represented above.

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 anything at all you’re not sure how to report in GitHub or want to discuss.

Instructions for Reporting Issues

  • Search the GitHub repository first to see if the bug is a known issue.
  • For known issues, please leave a comment on the issue saying you were able to replicate the problem and include device name, iOS version, app version, and type of site you used for testing.
  • For new issues, please follow the template GitHub repository that shows up when creating a new issue.
  • Please be aware that a bot will ask for labels but you won’t have rights to add them. Know that labels will be added by someone on the triage team. 👍
  • If you would like to send Activity Logs to help with debugging (this can be very useful!), you should first trigger the bug and then go to Profile > Help & Support > Activity Logs > Current and use the share icon at top right to copy the logs. Next, go to Help & Support > Contact Us, add a short note mentioning the bug report link, and paste the logs below the note. Please be aware Activity Logs may contain tokens which should not be shared publicly, and that’s why logs should be sent through the Contact Us form.

Thanks for testing! ❤️

#14-7, #call-for-testing, #ios, #mobile