Call for Testing: WordPress for iOS 14.8

WordPress for iOSiOS The operating system used on iPhones and iPads. version 14.8 betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 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, pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” one of us in the #mobile room on Slack, or head straight GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. and open an issue—please see “Where to Report” below.

Release Notes

  • Login and Signup UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. has been updated to offer a more user-friendly experience.
  • BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor: New block: Buttons. From now you’ll be able to add the individual Button block only inside the Buttons block.
  • Block editor: Add support for upload options in Cover block.
  • Block editor: Prefill caption for image blocks when available on the Media library.
  • Block editor: Fix bug where whitespaces at start of text blocks were being removed.
  • Block editor: Fix Quote block so it visually reflects selected alignment.
  • Block editor: Fix bug where buttons in page templates were not rendering correctly on web.

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. 14035 Complete the sign up flow and verify the screen you see after a successful signup is the one shown in 14035. Change as many optional settings changes as you can during signup and verify each works as expected.
  2. 14035 Log in and verify the screen you see after a successful signup is the one shown in 14035.
  3. 1933 Create a new post or page and add the Buttons block. Complete the 22 test cases for the Buttons block.
  4. 1933 Try to think of a scenario that would break the buttons block and test it out. For example, try adding and removing buttons successively.
  5. 2190 Create a new page, apply one of the page templates (about, blog, portfolio, services, team), make some edits, publish the page, verify the button block on the page looks correct on the web.
  6. 2174 Create a new post, add a Cover block, test each of the upload options (Choose from device, Take a Photo, Take a Video, WordPress Media Library, Free Photo Library, Other Apps), and make sure each option works as expected.
  7. 2156 Go to Media, upload an image, and save a caption for that image. Create a new post, add the image from before, verify that if there was a caption saved in the media library that it is pre-filled when that image is added in the editor.
  8. 2127 Create a new post, add a text block such as the paragraph block, type some spaces, then tap the toolbar bold button and verify the cursor stays in place.
  9. 2127 Create a new post, add a paragraph or verse or pre-formatted block, type some spaces and then text, highlight the text portion, tap any of the formatting options on the menu at the bottom of the editor area, verify the whitespace does not get removed. Compare this to the web editor, does it work the same way?
  10. 2006 Create a new post, add several quote blocks with different alignments, publish the post, verify the alignments look correct in the editor, Reader, and web.
  11. 2118 Create a post or page, add a block that allows nested blocks (Columns, Buttons, Media & Text), navigate through the nested blocks and verify the FloatingToolbar is rendered at the bottom of the screen on iOS and that the Navigate-Up button is clickable.

If you are able to complete the entire list above, please continue testing by looking at all the related PRs targeting WordPress-iOS 14.8 and gutenberg-mobile 1.27, specifically 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-8, #call-for-testing, #ios, #mobile