Call for Testing: WordPress for iOS 14.2

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

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 Profile > App Settings > Privacy Settings and turn on the Collect information option.
  • Go to Profile > 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:

  1. Media Editing: You can now crop, zoom in/out and rotate images that are inserted or being inserted in a post. (#13309)
    1. Create a new post or page and add an image to it, or open an existing post or page with an image in it.
    2. Select the image in the post editor and then select “Edit.” (In the block editor, you will need to select the edit button that appears over the image when you select it.) Confirm the media editor opens.
    3. Try editing the image in various ways: crop, zoom in or out, and/or rotate it.
    4. Confirm the edited image looks correct in the app editor.
    5. Save your changes and preview the post. Confirm the preview shows your edited image as expected.
    6. Additional scenarios to test: Ensure editing works with the block editor enabled and disabled (My Sites > Settings > Use block editor toggle); rotate your device while editing the image; change the image settings (e.g. image link, alt text) and ensure they are retained after editing; go offline (e.g. airplane mode), edit an image, and ensure the edits are uploaded when the device is online again.
  2. Post Preview: Added a new Desktop preview mode on iPhone and Mobile preview on iPad when previewing posts or pages. (#13334) Added new navigation, “Open in Safari” and Share options when previewing posts or pages. (#13334)
    1. Go to My Sites > Site Pages or Blog Posts.
    2. Select “View” to preview a post/page (under the … menu for Site Pages).
    3. On the preview screen, confirm you see an icon in the bottom right that allows you to switch between a desktop and mobile preview.
    4. Go back to the list of posts/pages and select a post or page to open it in the editor.
    5. Open the … menu and select “Preview.”
    6. On the preview screen, confirm you see an icon in the bottom right that allows you to switch between a desktop and mobile preview.
    7. While previewing the post or page, in either desktop or mobile mode, test the other options to navigate forward/back, share, and open in Safari.
  3. Reader: Added Post Reblogging feature. You can now reblog a post from the reader to your WordPress.com site(s). (#13361)
    1. Ensure you are logged in to a WordPress.com account with at least one site hosted on WordPress.com.
    2. Go to the Reader and confirm you see a reblog button for each post, both in the Reader list view and after selecting a single post in the Reader. Tap the reblog button on a post.
    3. If you have multiple WordPress.com sites: A site selector will appear; select the site you want to reblog to.
    4. When the post editor appears, make any desired edits and publish the post.
    5. Additional scenarios: Log in to a WordPress.com account with no WordPress.com-hosted sites and confirm that when you tap the reblog button, you get a clear, actionable message (instead of being taken to the post editor); log in to a self-hosted site but not WordPress.com, and confirm no reblog buttons appear; try reblogging with and without the block editor enabled (under My Sites > Settings > Use block editor).
  4. Comment Editing: Fixed a bug that could cause the text selection to be on the wrong line. (#13316)
    1. Publish a long comment on one of your blog posts or pages.
    2. In the app, find the comment (under My Sites > Comments or in a notification on the Notifications tab). Note: A notification will only be created if you publish the comment using a different WordPress.com account.
    3. Select Edit to open the comment editor.
    4. Choose a word in the middle of the comment text and double tap that word to select it. Confirm the correct word was selected.
  5. Block Editor: Long-press Inserter icon to show options to add block before/after. (#1835) Add support for image size options in the gallery block. (#1798) Retry displaying image when connectivity restores. (#1686)
    1. Start a new post and confirm that the block editor is enabled by default. Optional: Add some content to your new post.
    2. Long press on the “Add Block” icon in the editor toolbar, and confirm an action sheet appears with options about where to add the block:If no block or the title is selected, the options should be “Add to beginning” and “Add to end.”
    3. If a block is selected, the options should be “Add Block Before” and “Add Block After.”
    4. Make a selection and confirm the block picker comes up and your selected block is added in the correct place.
    5. Add a gallery block to your post, and add some images. With the gallery block selected, tap the settings icon and select “Images Size” to choose a size for the images in the gallery. Preview the post and confirm your images appear with the correct size. (You may need to preview the post on a desktop browser to confirm the size.)
    6. Add an image block to your post, and choose to add an image from the WordPress Media Library. Disable your internet connection and then choose an image from the media library. Confirm the image doesn’t load. Enable your internet connection, and confirm the image eventually loads and all other editor features continue to work as expected.
  6. Comments: Fixed a bug that could cause HTML markup to be displayed in the comment content. (#13351)
    1. Publish a comment that include HTML markup on one of your blog posts or pages.
    2. In the app, find the comment (under My Sites > Comments or in a notification on the Notifications tab). Note: A notification will only be created if you publish the comment using a different WordPress.com account.
    3. Confirm you see the comment in plain text, without any HTML markup.
    4. Select Edit to open the comment editor. Confirm you see and can edit the comment in plain text, without any HTML markup.
  7. Signup and Login: Signup or login via magic link now supports multiple email clients. (#13275)
    1. Start logged out of the app.
    2. Log in or sign up to WordPress.com using the magic link option.
    3. After tapping “Open Mail,” confirm that it either opens Apple Mail (if that is your only mail app) or you see a list of your mail apps (if you have multiple apps installed) and can choose which app to open.
    4. Confirm the correct app is opened and you can continue logging in/signing up as expected.
  8. Posts: Fixed a bug that could disable comments on a draft post when previewing that post. (#13362)
    1. Go to My Sites > Settings > Discussion > confirm the Allow Comments setting is enabled (toggled on).
    2. Start a new post. Add some content and save the post as a draft.
    3. Tap to edit the draft. Add some new content and then preview the draft.
    4. Publish the post. View the post and confirm comments are enabled.
    5. Go to My Sites > Settings > Discussion > toggle off the Allow Comments setting. Repeat steps 2-4 and confirm comments are disabled.

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

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! ❤️