WordPress for iOS version 14.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 Account > App Settings > Privacy Settings and turn on the Collect information option.
- Go to Account > Help & Support and turn on the Extra Debug option.
- If you are comfortable testing in a language other than English, please feel free to test in that language.
To test:
- 2034 Create a new post, add a cover block, try to break it. Also see test cases.
- 1990 Create a new post, add a heading block, check that alignment options are visible on the block toolbar and work correctly, check that changing header size works correctly.
- 2076 Change alignment options in the Heading, Paragraph, Image, and MediaText blocks. Verify that they look correct in View Site and on the web in various screen sizes.
- 2042 Add a group block, create some nested structure, navigate through the blocks, expect that unselected blocks do not get dimmed when navigating the block hierarchy.
- 13624 (iPhone X and up) View the Notifications screen in landscape orientation, verify that content and navigation elements are not hidden under the notch (example).
- 13749 Go to the Reader, find a post with no comments, tap the comment icon, notice the no results view with “Be the first to leave a comment” showing, tap the reply field, type
@to display a selector for user mentions and verify you can select users from the selector. Note: best tested from a site with multiple users. - 13753 Access all the tabs on
Site Pagesand verify the post dates appear and that the app does not crash. - 13796 (iOS 13+) Check that post previews now show as fullscreen. Try previews from Blog Posts, Site Pages, the Post or Page Published/Updated notice, from the block editor, or in Spotlight. Test iPhone and iPad.
- 13809 Add an image using the “Other Apps” option and verify a Cancel button is present, uses the same color, and works even when switching back and forth between “Recents” and “Browse”. Test from the block editor, the classic editor, and the Media section in the app.
- 13808 (iOS 12) Go to My Sites and tap the Posts Quick Action button (at the top) several times rapidly on an iPad running iOS 12 and verify the app does not crash.
- 13805 Go to Reader and open any post, switch between light & dark modes, verify the area around the image and title is updated properly (example).
- 13793 On a slow network, go to Stats > any period (Days, Weeks, Months, Years), toggle light/dark mode while the ghost (placeholder) animation is displayed, verify the date bar, chart, and stats rows update properly.
You can find all other changes/fixes and details in the related PRs targeting WordPress-iOS 14.6 and gutenberg-mobile 1.25.
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.
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! ❤️