Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gallery is removed after editing post from Jetpack Android app #18465

Closed
rezzap opened this issue May 18, 2023 · 3 comments
Closed

Gallery is removed after editing post from Jetpack Android app #18465

rezzap opened this issue May 18, 2023 · 3 comments

Comments

@rezzap
Copy link

rezzap commented May 18, 2023

Expected behavior

I'd expect to be able to edit a post from the app that was created on the web without losing my gallery.

Actual behavior

If I edit the post in the app that contains an image gallery, the gallery is removed.

It sounds related to the issue #17712

Steps to reproduce the behavior

  1. Create a post on a Jetpack connected site from the web browser that includes text above and bellow an image gallery
  2. Open the post from the Jetpack app
  3. Edit the text bellow the image
  4. Update the post
  5. Refresh the post in the browser, the image gallery is removed.
Tested on Samsung s9+, Android 10, JPAndroid / WPAndroid 22.3

User report: 6237950-zen

@thomashorta
Copy link
Contributor

Hi @rezzap, I believe you're right and this is related to #17712. 🙇

The fix for that issue is part of the Android Jetpack version 22.5 release which is currently being rolled out to our users and should be available to all userbase by tomorrow (pbArwn-69x-p2). I just tested 22.3, 22.4, and 22.5 and confirmed the issue is present in the previous versions but is fixed on the latest.

It would be great to get back to that user and let them confirm that the issue no longer happens on Jetpack 22.5 before closing this issue.

Let me know if you need anything, and thank you!

@rezzap
Copy link
Author

rezzap commented Jun 14, 2023

@thomashorta I've let the user know they can expect the fix in 22.5 and we can re-open the issue here if they follow up. We didn't hear back from them after the latest reply, so I wouldn't expect us to wait to close this if we're not reproducing this now.

@thomashorta
Copy link
Contributor

That makes sense to me, I will close the issue for now, since the fix for #17712, introduced in release 22.5, fixed this issue as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants