Call for Testing: WordPress for Android 14.5

WordPress for Android version 14.5-rc-1 is available for testing on the Beta channel. You can ask to join the Beta Program at Android App Testing on Google Play. Once you have been accepted, click the “Become a Tester” button at the same link.

To test with an apk, you can download wpandroid-14.5-rc-1-universal.apk.

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” and “Crash reports” options.
  • 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. 1931 Open any post or page, add a Latest Posts Block, verify that tapping on the gear icon opens block settings, save and publish the post or page, verify the updates show on the web (mobile and desktop), re-open the post for editing from the web (mobile or desktop), change each setting, verify from another platform (mobile or desktop) that the settings were updated and are reflected on the published post and drafts as expected.
  2. 1987 Create a new page, notice there are five new starter page templates, tap each one and modify the content for each template and publish. Try from portrait and landscape mode. Does the page template behave as expected? Please be aware of known issues in 2012 and 2013 which are already in progress for a future release.
  3. 1964 Go to https://automattic.com/work-with-us/, copy the first part of the page (from Work With Us until the end of the Coming on board paragraph), paste into any post or page using the block editor, check that all blocks are created and the app does not crash. Try with the content of at least one other web page of your choice that has HTML including wrapped images.
  4. 11478 Turn on airplane mode, go to My Site > Blog Posts, create two posts and publish them, turn off airplane mode so the upload can start and then turn it on quickly before the uploads finish, wait until the upload fails and make sure the UI is not flickering a bug where failed post uploads were sometimes being retried indefinitely.
  5. 11420 Test the signup, site creation, and login flows. Watch for any visual issues or blockers.

You can find more details about all of the updates that went into this release in the related PRs listed at WordPress-Android 14.4 and gutenberg-mobile 1.24.

Where to Report

  • WordPress-Android 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 > Application log and use the copy 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 that the Application log 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-5, #android, #call-for-testing, #mobile

Call for Testing: WordPress for iOS 14.5

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

  1. 1931 Open any post or page, add a Latest Posts Block, verify that tapping on the gear icon opens block settings, save and publish the post or page, verify the updates show on the web (mobile and desktop), re-open the post for editing from the web (mobile or desktop), change each setting, verify from another platform (mobile or desktop) that the settings were updated and are reflected on the published post and drafts as expected.
  2. 1987 Create a new page, notice there are five new starter page templates, tap each one and modify the content for each template and publish. Try from portrait and landscape mode. Does the page template behave as expected? Please be aware of known issues in 2012 and 2013 which are already in progress for a future release.
  3. 1953 Add a quote block to any post or page and verify the left border is visible in Dark Mode.
  4. 1964 Go to https://automattic.com/work-with-us/, copy the first part of the page (from Work With Us until the end of the Coming on board paragraph), paste into any post or page using the block editor, check that all blocks are created and the app does not crash. Try with the content of at least one other web page of your choice that has HTML including wrapped images.
  5. 13591 Create a new draft, back date it to publish in the past, check that the status line on the Post Settings > Publish screen says the post “was” published if the date is set to something in the past and make sure the past date in Post Settings shows “Scheduled” instead of “Published”.
  6. 13668 Set your site timezone to a timezone earlier than the device timezone (i.e. site timezone PST and device timezone EST or site timezone Denver and device timezone Melbourne), create a new post go to More > Post Settings and change the publish date (including the month), verify the date at the top right on the calendar reflects the date selected in the calendar, then in the Post Settings when you leave the calendar. Publish the post and verify the publish date remains correct.
  7. Various While in Dark Mode, browse various areas of the app and make sure the UI elements look correct. Areas to pay close attention to: Login, Stats, Search, Media Picker, Reader Comments.
  8. 13645 Go to Reader, search for a post and open it, change to landscape view, verify the search bar and the toolbar at the bottom of posts both extend to the full width of the landscape view. Verify both still look correct and work properly after switching back to portrait view.
  9. 13685 Go to any comment in Notifications or Reader or the Comments section, start a comment reply, use the arrow to expand the comment to full screen, tap @ to select another user from the same site, verify the user can be selected and that they receive a push notification as expected (note: they must have notifications settings turned on).
  10. 13665 Log in and verify you see that the “Send Email” option shows a tip about checking the spam/junk folder if needed, verify the login works as expected. Log out and complete the signup flow and verify the tip is shown in that flow and that signup is working normally.
  11. 11420 Test the signup, site creation, and login flows. Watch for any visual issues or blockers.

You can find all other changes/fixes and details in the related PRs targeting WordPress-iOS 14.5 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! ❤️

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

Call for Testing: WordPress for Android 14.4

WordPress for Android version 14.4-rc-1 is available for testing on the Beta channel. You can ask to join the Beta Program at Android App Testing on Google Play. Once you have been accepted, click the “Become a Tester” button at the same link.

To test with an apk, you can download wpandroid-14.4-rc-1-universal.apk.

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” and “Crash reports” options.
  • 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. 11378 Turn on airplane mode, create a draft, add an image, click on Back, create another draft, add the same image, click on Back, turn off airplane mode, wait until uploads complete, open second post, switch to HTML mode, make sure the image is not using a local path. Test with and without the block editor turned on.

You can find more details about all of the updates that went into this release in the related PRs listed at WordPress-Android 14.4 and gutenberg-mobile 1.24.

Where to Report

  • WordPress-Android 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 > Application log and use the copy 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 that the Application log 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-4, #android, #call-for-testing, #mobile

Call for Testing: WordPress for iOS 14.4

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:

  1. 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.
  2. 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! ❤️

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

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 Android 14.3

WordPress for Android version 14.3-rc-1 is available for testing on the Beta channel. You can ask to join the Beta Program at Android App Testing on Google Play. Once you have been accepted, click the “Become a Tester” button at the same link.

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

To test with an apk, you can download wpandroid-14.3-rc-1-universal.apk.

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” and “Crash reports” options.
  • 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. 1264 Create ordered lists with 4 or less digits in both Aztec and Block Editor and check that the spacing looks good.
  2. 13482 Go to the Blog Details page and use Quick Actions buttons to access parts of a blog. Test from all site types.
  3. 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.
  4. 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.
  5. 1866 Block editor: add a button block and try to break it. Also see test cases.
  6. 1850 Block editor: add a group block and try to break it. Also see test steps and test cases.
  7. 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.
  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. 1938 Block editor: add a paragraph block with text, change alignment to right or center, verify alignment changed, tap enter, verify alignment stays set, switch to html, verify alignment is still set properly, go back to visual, verify alignment is still set properly, tap enter in the middle of the text block, verify alignment is still set properly for both blocks.
  10. 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.
  11. 13496 In iOS Settings > General > Language and Region, set a Region where the week begins on Monday (Lithuania, for example), start a new post and tap to change the Published On / Scheduled date, verify the weekday header starts the week on the correct day. Also test this after changing the WP Admin > Settings > Week Starts On option.

You can find more details about all of the updates for this release in the related PRs targeting WordPress-Android 14.2 and gutenberg-mobile 1.22.

Where to Report

  • WordPress-Android 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 > Application log and use the copy 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 that the Application log 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, #android, #call-for-testing, #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 Android 14.2

WordPress for Android version 14.2-rc-1 is available for testing on the Beta channel. You can ask to join the Beta Program at Android App Testing on Google Play. Once you have been accepted, click the “Become a Tester” button at the same link.

To test with an apk, you can download wpandroid-14.2-rc-1-universal.apk.

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:

  • If you are comfortable testing in a language other than English, please test in that language.

To test:

  1. Block editor: Long-press Inserter icon to show options to add block before/after. (#1835)
    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.
  2. Block editor: Add support for image size options in the gallery block. (#1798)
    1. Add a gallery block to your post, and add some images.
    2. With the gallery block selected, tap the settings icon and select “Images Size” to choose a size for the images in the gallery.
    3. 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.)
  3. Block editor: Retry displaying image when connectivity restores. (#1686)
    1. Add an image block to your post, and select “WordPress Media Library” as the image source.
    2. Disable your internet connection and then choose an image from the media library. Confirm the image doesn’t load.
    3. Enable your internet connection, and confirm the image eventually loads.
    4. Confirm all other editor features continue to work as expected.
  4. Block editor: Fix retry media upload action. (#11237)
    1. Add an image block to your post, and then disable your internet connection.
    2. Select “Choose from device” and select an image. Notice the upload failure message.
    3. Enable your internet connection, tap the image, and retry the image upload.
    4. Confirm the image upload is restarted and the image is successfully uploaded.
  5. Block editor: Fix blank post when sharing media from another app. (#11121)
    1. Go to My Sites > Settings and confirm “Use block editor” is enabled.
    2. Open a different app on your device that contains photos or videos.
    3. Select a photo or video and share it to the WordPress app.
    4. Confirm that WordPress opens and the photo or video was successfully uploaded and is visible in the app.
    5. Repeat the same steps, sharing links from your device web browser or from another app (e.g. YouTube, Twitter). Confirm the editor is opened and includes a clickable link.
    6. Repeat the same steps, but with the “Use block editor” setting disabled.
  6. Block editor: Fix issue that sometimes prevented merging paragraph blocks. (#1867)
    1. Add a paragraph block and add some text to it.
    2. Tap in the middle of the text and hit enter to move the right half of the text to a new block.
    3. Hit backspace and watch the new block merge back correctly with the previous block.
    4. Hit enter from the middle of the text again to create a new block.
    5. This time delete one or more characters from the beginning of the new text block.
    6. Continue to hit the backspace key and confirm the new block is merged back with the previous block.

You can find more details about all of the updates for this release in the related PRs targeting WordPress-Android 14.2 and gutenberg-mobile 1.22.

Where to Report

  • WordPress-Android 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 > Application log and use the copy 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 that the Application log 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, #android, #call-for-testing, #mobile

X-post: Get Involved Table at WordCamp Asia 2020

X-post from +make.wordpress.org/community: Get Involved Table at WordCamp Asia 2020

Call for Testing: WordPress for Android 14.1

WordPress for Android version 14.1-rc-1 is available for testing on the Beta channel. You can ask to join the Beta Program at Android App Testing on Google Play. Once you have been accepted, click the “Become a Tester” button at the same link.

To test with an apk, you can download wpandroid-14.1-rc-1-universal.apk.

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. 11098 Start with a fresh installation so there are no posts in the DB, use a WordPress.com site for testing, go to My Site > Posts (do not scroll at all), type a search query for a very old post or for a post in the trash. Verify that the same search returns the same results using WordPress.com/sites > Posts > Search.
  2. 11099 Go to My Sites > Switch Site, tap and hold a Jetpack or Atomic site, verify that the “Remove Site” dialog is not shown and instead you are able to show/hide the site instead. Repeat the steps for a WordPress.com and a Self-hosted site and verify that only the Self-hosted site gets the option to “Remove site”.
  3. 19534 Create a new post in the block editor, add any shortcode, try to break the block. Try with 5 randomly chosen shortcodes.
  4. 992 Open a post that has many blocks and verify the padding between blocks isn’t unreasonably large.
  5. 10505 Create a post with 500-1,000 paragraph blocks, quickly scroll through the post for a while, verify you cannot crash the app even after a minute or so of scrolling. (53s)
  6. There is an open-ended ask to test every area of the editor with both and without the block editor turned on. A lot of changes to the saving/uploading logic were made which basically touched everything in the editor. Please test creating a few new posts and publishing them, at least one while you are online and one while you are offline plus one that’s scheduled to publish at a later time.

You can find more details about all of the updates for this release in the related PRs targeting WordPress-Android 14.1 and gutenberg-mobile 1.21.

Where to Report

  • WordPress-Android 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 > Application log and use the copy 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 that the Application log 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, #android, #call-for-testing, #mobile