While creating a new post / page offline and publishing it, the post / page is queued but shows up as a draft. After successfully uploading it, it still stays as a draft.

As the user intended to publish the post, retrying should also publish the post
To clarify, we should amend the error state to mention posting. Error message should say "Could not upload media. Post not published." Then its clear that retry relates to posting, not just media.
To make this work we need to differentiate the error state in publishing/saving/scheduling scenarios.
User publishes and media upload error (use case in this issue)
Error Message: "Could not upload media. Post not published."
Action and behavior: Retry. Retrying publishes the post if media uploads successfully
User schedules and media upload error (scheduling rather than publishing)
Error Message: "Could not upload media. Post not scheduled."
Action and behavior: Retry. Retrying schedules the post if media uploads successfully
User saves and media upload error (user did not intend to publish)
Error Message: "Could not upload media."
Action and behavior: Retry. Retrying only retries uploading the media as the user has not changed the post state
https://github.com/wordpress-mobile/WordPress-Android/issues/9933
@wordpress-mobile/ravenclaw @megsfulton @osullivanchris This is related to what @maxme and I agreed on https://github.com/wordpress-mobile/WordPress-Android/issues/9933.
Restating it here for discussion.
- Android: Publishing while offline and retrying will lead to the post being uploaded and published
- iOS: Publishing while offline and retrying will lead to the post being uploaded as a draft
After a user _published_ a post in the Editor but it failed because of network connectivity...
Discussion has progressed here on Android, will capture the proposal back in this ticket when we have finished resolving. Should be the same on both platforms
https://github.com/wordpress-mobile/WordPress-Android/issues/9933
Linked the wrong Android issue previously. We decided the following:
To make this work we need to differentiate the error state in publishing/saving/scheduling scenarios. Hopefully not a huge chunk of work, was quick for @maxme on Android. But writing it all down here for clarity.
1. User publishes and media upload error (use case in this issue)
Error Message: "Could not upload media. Post not published."
Action and behaviour: Retry. Retrying publishes the post if media uploads successfully
2. User schedules and media upload error (scheduling rather than publishing)
Error Message: "Could not upload media. Post not scheduled."
Action and behaviour: Retry. Retrying schedules the post if media uploads successfully
3. User saves and media upload error (user did not intend to publish)
Error Message: "Could not upload media."
Action and behaviour: Retry. Retrying only retries uploading the media as the user has not changed the post state
Closing this in favor of #12240 which should sufficiently cover this issue.
Most helpful comment
https://github.com/wordpress-mobile/WordPress-Android/issues/9933
Linked the wrong Android issue previously. We decided the following:
To make this work we need to differentiate the error state in publishing/saving/scheduling scenarios. Hopefully not a huge chunk of work, was quick for @maxme on Android. But writing it all down here for clarity.
1. User publishes and media upload error (use case in this issue)
Error Message: "Could not upload media. Post not published."
Action and behaviour: Retry. Retrying publishes the post if media uploads successfully
2. User schedules and media upload error (scheduling rather than publishing)
Error Message: "Could not upload media. Post not scheduled."
Action and behaviour: Retry. Retrying schedules the post if media uploads successfully
3. User saves and media upload error (user did not intend to publish)
Error Message: "Could not upload media."
Action and behaviour: Retry. Retrying only retries uploading the media as the user has not changed the post state