WordPress for iOS version 14.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 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:
- 13351 Create a new draft, go to the Posts List, re-open the draft, go to More > Post Settings, tap “Publish Immediately”. Check that it says “Publish” and not “Published” and that it says “Immediately” instead of showing a date and time.
- Browse different areas of the app and try to uncover any screens that load too slowly.
You can find all other changes/fixes and details in the related PRs targeting WordPress-iOS 14.4 and gutenberg-mobile 1.24.
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! ❤️