You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While on iOS, whether the post was previously viewed or not, the message “Error Loading Post” is displayed when the user attempts to view a post through the notifications screen.
On Android the same message appears only if the user never viewed that post. The user can still successfully view a post after clicking its notification as long as the post was previously viewed.
Reproduction Rate
4/4 100%
Expected behavior
The message “Error Loading Post” should be displayed regardless of the post’s caching status.
Actual behavior
The post is displayed if it was previously viewed.
Steps to reproduce the behavior
Install WordPress 14.1
Log in to an account.
Press the “Add new” button.
Select the blog post option.
Type in any content.
Publish the post.
Press “Posts”.
View the post.
Press “More” on that post.
Select the bin option.
Navigate to the previous screen.
Select the “Notifications” tab.
Select the binned post.
Tested on the following
Samsung Galaxy S6 (7.0)
Please see the attached video for more information
Description
While on iOS, whether the post was previously viewed or not, the message “Error Loading Post” is displayed when the user attempts to view a post through the notifications screen.
On Android the same message appears only if the user never viewed that post. The user can still successfully view a post after clicking its notification as long as the post was previously viewed.
Reproduction Rate
4/4 100%
Expected behavior
The message “Error Loading Post” should be displayed regardless of the post’s caching status.
Actual behavior
The post is displayed if it was previously viewed.
Steps to reproduce the behavior
Tested on the following
Samsung Galaxy S6 (7.0)
Please see the attached video for more information
AndroidCachedBinnedPost.zip
Submitted by:
Luis Pimenta
The text was updated successfully, but these errors were encountered: