Call for Testing: WordPress for iOS 15.2

WordPress for iOSiOS The operating system used on iPhones and iPads. version 15.2 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

  • Reader content improved: a lot of fixes in how the content appears when you’re reading a post.
  • A site’s title can now be changed by tapping on the title in the site detail screen.
  • Added a new Quick Start task to set a title for a new site.
  • 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: Add support for customizing gradient type and angle in Buttons and Cover blocks.
  • Block editor: Display content metrics information (blocks, words, characters count).
  • Fixed a crash that results in navigating to the block editor quickly after logging out and immediately back in.

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. various Go to the Reader, tap on any section, verify the actions for Reader cards work as expected (save, reblog, comment, like), test the main tab layout, search, tag detail, blog detail, and feed detail.
  2. 14365 Smoke test the Reader including headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. byline in dark mode, left/right image alignment, images should appear as a whole instead of slowly appearing, broken images should not be displayed, loading view, error view, noresults view, quote block citation, list bullet point color, gallery with Link to > Media File on, tiled galleries, spacing between content should be reasonable, Twitter embeds look like Twitter embeds, coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. code block is differentiated by background color or an outline.
  3. 2199 Verify reblogged content looks correct in the Reader.
  4. 14390 Tap on a Site Title in the site detail screen and verify a new title can be saved and appears correctly on the web.
  5. 14384 Create a new site, tap “Yes, Help Me” when prompted, verify that the Quick Start task to set a title works properly.
  6. 22493 Customize the gradient type and angle in button and cover blocks and verify the selected settings show up correctly in the editor, web, and Reader.
  7. 12191 Open the editor for any post with a lot of content in different blocks, go to the 3-dot menu > Content info, and verify you can see the correct block, word, and character count. Verify the counts match what shows on the web.
  8. 14359 Navigate to the block editor quickly after logging out and immediately back in and verify the app does not crash.

If you are able to complete the entire list above, please continue testing by looking at all the related PRs targeting WordPress-iOS 15.2 and gutenberg-mobile 1.31, 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 may not 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! ❤️

#15-2, #call-for-testing, #ios, #mobile