Call for Testing: WordPress for iOS 14.3

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

Please note that 14.3 will have an extremely short development cycle!

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 (Me icon) > App Settings > Privacy Settings and turn on the Collect information option.
  • Go to Account (Me icon) > 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. 11269 Go to My Site > Site Pages > More (3 dots) > Set Parent, try several different searches, verify the search function works as expected and that you can set a parent page after searching. Also see test cases.
  2. 1904 Block editor: add an image block, tap the gear to change to different image sizes, verify the image size changes, verify the image size is preserved if you update the post, leave, return, etc.
  3. 1610 Block editor: add a gallery block and try adding new images to the gallery with all the available options provided. Test from all site types.
  4. 1866 Block editor: add a button block and try to break it. Also see test cases.
  5. 1850 Block editor: add a group block and try to break it. Also see test steps and test cases.
  6. 18574 Block editor: try adding a block from a smaller device or in horizontal mode, verify you can scroll through and add all blocks. Also check that you can scroll the BottomSheet in the image block settings.
  7. 1895 Block editor: check for incorrect image previews using the testing steps at WordPress-Android/11239#issue-560256478.
  8. 1930 Block editor: create a new post, add a title with any emoji, switch to HTML mode, verify no extra strong elements are added to the title.
  9. 1802 Block editor: check that active blocks have a full solid border and a floating toolbar, verify the floating toolbar works as expected. See test steps.
  10. Reader Information Architecture updates:
    1. Saving and restoring subfilter to/from shared prefs #10925
    2. Site not removed from subfilter when unfollowed #11155
    3. New design reader bottom sheet – step 1 #11183
    4. New design reader bottom sheet – step 2 #11184
    5. New design reader bottom sheet – step3 #11193
    6. IA Reader self-hosted improvements #11270
    7. Add historical searches list to the Reader initial search screen #11293
    8. Add follow/unfollow button to the Followed Sites tab on Reader’s management section #11219

You can find all other changes/fixes and details in the related PRs targeting WordPress-Android 14.3 and gutenberg-mobile 1.23.

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

#14-3, #call-for-testing, #ios, #mobile

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

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

Call for Testing: WordPress for iOS 14.1

WordPress for iOS version 14.1 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.
  • Go to My Site > Settings and turn on the Use Block Editor setting to enable the block editor for new posts.
  • If you are comfortable testing in a language other than English, please feel free to test in that language.

To test:

  1. 19534 Create a new post in the block editor, add any shortcode, try to break the block. Try with at least 5 randomly chosen shortcodes.
  2. 13242 In the app, open a site that has some traffic registered in the Stats section, and go to Stats > Widgets > Use this site. On the device, add the WordPress This Week widget to your Today view. Verify the widget works as expected and that the numbers match what you see when you check stats for the same site from WordPress.com using a web browser.
  3. 13236 In the app, follow any private blog that requires login to view the post. Go to the Reader and find a post from that blog, tap Visit for that post, and verify the post is displayed properly when authenticated (no on-screen error, no errors in the console). Test using all three site types: WordPress.com, Jetpack, Self-hosted.
  4. 13236 Using a WordPress.com account with a site that has an upgrade or plan, go to My Site > Settings > Advanced > Delete Site > Show Purchases, and verify that the “Show Purchases” page is displayed properly. Complete the process to delete a site and verify it worked.

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

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

#14-1, #call-for-testing, #ios, #mobile

Call for Testing: WordPress for iOS 14.0

WordPress for iOS version 14.0 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 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. 13112 Enter any comment flow (reader, notification, comments), add some text, tap the full screen toggle button, add more text, tap the exit full screen button, enter more text, tap reply/save button.
  2. 13195 On the device, add the Today and/or the All-Time widget to the Today view. In the app, Go to Stats > Widgets > Use this site, switch to a different site, go to Stats, close the app, return to the Today view and tap a widget, tap Done to close the modal, verify the Stats view then displays the Stats for the selected site (not the widget site).
  3. 13196 On a site with high traffic, go to Stats > Widgets > Use this site, add the Today and All-Time widgets to the Today view, verify the widget numbers are abbreviated as they are in the app.
  4. 13131 With a site you haven’t accessed before or modified insights, check that the default insights list is: Latest Post Summary, Today, All-Time, Follower Totals. Tap Add stats card and check that the view is presented modally and functions as expected. Also test on iPad.
  5. 13158 Trigger some notifications and tap on them. The app should be opened correctly and should not crash.
  6. 13128 Set the Site Time Zone to a different Time Zone than the device, schedule a post, check that the displayed scheduled time matches the site’s time zone and is published on that date.
  7. 13173 Rename an image saved on your device or iCloud Drive. In the app, go to Media > + and add a new image, select ‘Other Apps’, select the renamed image, after it uploads click on the image and verify the original file name was kept (lowercased and without extension).
  8. 1669 In the block editor in the app, add an image via link, add a second image from the Media Library, close and reopen the post, verify the Image Sizes option is displayed for the image inserted from the Media Library and not for the image added via link.
  9. 1701 In the block editor in the app, add a paragraph block, type some characters, undo changes until the block is removed. Repeat if necessary. App should not crash.
  10. 1631 On the web, create a draft with aligned images. In the app, open an empty post (to load the js from the metro bundler), go to Blog Posts > Drafts, turn on airplane mode, open the draft, make sure images have placeholder images.

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

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.

Thanks for testing! ❤️

#14-0, #call-for-testing, #ios, #mobile

Call for Testing: WordPress for iOS 13.9

WordPress for iOS version 13.9 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 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. 13043 Swipe right over the Home or Lock screen, scroll down, tap Edit, add the All Time widget, verify the unconfigured view is displayed, go to Stats > Widgets Use this site and verify the widget displays data for the selected site and matches what is displayed in the app.
  2. 1498 Add a gallery block to a post or page and try to break it: add images, remove images, change the number of columns, crop images, add captions, rotate the device while interacting with the block
  3. 1628 Add an image blog, open image settings, rotate the device, dismiss the settings sheet, the app should not crash.
  4. 1619 Add a list block, change it to an ordered list (numbered), change the start value of the list and make the numbering go in reverse order.
  5. 1601 Add a video block, tap on the settings icon (cog), change each one of the video settings, save changes, and verify the settings are each working as expected.
  6. 13092 On a site that has Quick Start available, go to Next Steps > Grow Your Audience > Follow other sites, complete the “Tap < Reader to continue” step and verify the hint goes away after that.

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

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.

Thanks for testing! ❤️

#13-9, #call-for-testing, #ios, #mobile

Call for Testing: WordPress for iOS 13.8

WordPress for iOS version 13.8 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 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. 10817 Add a spacer block to any post. Try to break it. View results on various screen sizes, including desktop, and make sure the block works as expected.
  2. 1597 Double tap on an image in the image block to preview it full screen. Try zooming. Try with two or more images added in different ways (inserted from URL, Choose from device, Take a Photo, WordPress Media Library, Free Photo Library, Other Apps).
  3. 12947 On the web, open an existing post, make a change, and wait for it to autosave. On the app, open the post and you should see a conflict resolution dialog. Select the more recent changes and make sure they are reflected in the app and on the web.
  4. 13013 Sign in with Apple using a linked WordPress account that has 2FA enabled.
  5. 13005 Sign in with Google using a Google account that has 2FA enabled on the WordPress account with the same email address.
  6. 12980 Go to Profile > Help & Support > Activity Logs > Current and copy the contents. Go to Profile > Help & Support > Contact Us and send the copied logs to support in a new message with an explanation above. Verify you do not see the ‘Message failed to send’ error when using the Contact Us form. Try changing your email on the Support screen and repeat the steps above.
  7. 12980 Log in and check that the Me screen is not blank. Quit the app and relaunch, and check the Me screen isn’t blank. Quit the app, turn on airplane mode, relaunch the app and check the Me screen isn’t blank. Try with a self-hosted only login as well as a WordPress.com login.

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

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.

Thanks for testing! ❤️

#13-8, #call-for-testing, #ios, #mobile

Call for Testing: WordPress for iOS 13.7

WordPress for iOS version 13.7 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 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. 12858 Block editor: insert images from the “Free Photo Library” and “Other Apps”. Try using different alignments. Try closing and re-opening the post. Try editing while offline.
  2. 1489 Block editor: create and publish a long post with different alignments for some of the paragraphs.
  3. 1442 Block editor: try to break the preformatted block, try copying and pasting text into that block from the web or other apps.
  4. 1552 Block editor: when you tap on an Innerblock, such as the paragraph inside the Media & Text block, the first character should be capitalized when you start typing.
  5. 12893 12946 Swipe right over the Home or Lock screen, scroll down, tap Edit, add the Stats Today widget and make sure the stats are accurate and you can expand it to see Likes and Comments.
  6. 12910 Switch to a self-hosted site, go to My Sites > Comments, tap Approve on a pending comment and make sure the action works on the first try.

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

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.

Thanks for testing! ❤️

#13-7, #call-for-tesitng, #ios, #mobile

Call for Testing: WordPress for iOS 13.6

WordPress for iOS version 13.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 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. Offline Support Check that posts created while offline are updated when you go back online. Test with WordPress.com, Jetpack, and Self-hosted sites.
  2. Offline Support Edit a published post while offline and check that the changes are synced properly when you go back online. Test with WordPress.com, Jetpack, and Self-hosted sites.
  3. Offline Support Edit and existing draft and publish it while offline and make sure the changes are visible in the published post when you go back online. Test with WordPress.com, Jetpack, and Self-hosted sites.
  4. Offline Support In general, if you make changes to a post or page while offline, do the changes get uploaded or published as expected when you go back online? Try to break autosave or auto-uploads.
  5. Offline Support Try changing post settings for any post while offline and check that the changes are updated or published as expected when you go back online.
  6. 12814 Log out of the app.. Add a self-hosted site. Go to the Profile page (Me) and verify it is not blank.
  7. 12670 While offline, edit an existing pending for review or scheduled post, make some changes, tap X and update the post. Verify the post is still pending or scheduled and was not published.
  8. 1460 Add several images in different ways to a post and pick different alignments. Check that image alignments made in the editor on mobile are reflected on the web from a laptop and vice versa.

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

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.

Thanks for testing! ❤️

#13-6, #call-for-testing, #ios, #mobile

Call for Testing: WordPress for iOS 13.5

WordPress for iOS version 13.5 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 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. 12286 Block editor: Long-press/3D touch on the app icon, select the “New Photo Post” option to add an image to a new post.
  2. 1394 Block editor: Add an image link that opens in a new tab.
  3. 1415 Block editor: Switch to light mode, add a List block, write some text on it, switch to dark mode, delete the text and write new text, check that the text color is white.
  4. 1439 Block editor: try adding and removing the Media & Text block. Try to break it.
  5. Various Pick any dark mode update from here and test it to make sure it’s working as expected.
  6. 12243 Go to Stats > Insights and rearrange the cards. Look through the stats to make sure everything looks okay. Close and re-open the app and make sure the custom order is preserved.
  7. 12711 On a slow network connection, check that Stats Insights loads reasonably fast.

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

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.

Thanks for testing! ❤️

#13-5, #call-for-testing, #ios, #mobile

Call for Testing: WordPress for iOS 13.4

WordPress for iOS version 13.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 My Site > Settings > Use Block Editor to enable the block editor for new posts.
  • If your native language is not English or if you are comfortable testing in another language you are proficient in, please test in that language.

To test:

  1. Block Editor: create and publish post several available blocks—get creative, think like a user, try to break the editor. For example, try adding several images at once while offline then go online.
  2. Test that you can receive push notifications, notifications in-app, and email notifications for likes, comments, and follows.
  3. 12552 Sign In With Apple: log in with SIWA, open app switcher (double tap home button), select iOS settings, disconnect Apple account(Settings > Password & Security > Apps Using your Apple ID > WordPress > Stop Using Apple ID), go back to the WordPress app—verify you are logged out and the following message appears in app logs “Apple credentialRevokedNotification received. User signed out.”
  4. 12585 Sign In With Apple: log in with SIWA, background the app, disconnect your Apple account on the device (Settings > Password & Security > Apps Using your Apple ID > WordPress > Stop Using Apple ID), open the app—verify you get logged out.
  5. 12606 Sign In With Apple: login/signup with SIWA using an email that matches a WP account, log out and log in with SIWA again, verify the email address is displayed on the password entry view.
  6. 12637 Like some posts in the Reader using dark and light mode.
  7. 12616 Check that popup menus for headings and lists have a dark background in Aztec.
  8. 12610 Log out and when you log back in make sure the spinner at bottom right is visible while logging in.
  9. 12590 Open an individual post in the Reader, minimize the app, and verify the app doesn’t crash.
  10. 12590 Put the app in the background and switch from light to dark mode (or vice versa), re-open the app, make sure the colors look correct and that buttons and content is generally readable.
  11. 12560 Browse comments, pending comments, edit a comment, resize/crop your Gravatar, and view the country map in stats to make sure all of those things look good in dark mode.
  12. 12560 Share content from Safari to the WordPress app, add enough content so it goes behind the keyboard, try to scroll.
  13. 12575 Create a document in iA Writer, tap the share icon at the bottom, select “New Draft on WordPress” (a custom iA Writer action, NOT the WP sharing extension), verify the link opens in Safari.
  14. 1382 Block editor: check if links in content are tappable without opening a Safari instance on iOS 13.
  15. 14270 Block editor: select text, tap Link button, exit without adding a link, check that no link was added. Check that adding a link right after that still works.

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

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.

Thanks for testing! ❤️

#13-4, #call-for-testing, #ios, #mobile