-
Notifications
You must be signed in to change notification settings - Fork 58
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
Unable to add/upload images if Don't keep activities
is ON
#582
Comments
Just making sure, is this a Gutenberg only issue or does it happen in Aztec too @daniloercoli ? |
It does work without any problem on Aztec. (Tested on alpha-150 - versionCode 674) |
Don't keep activities
is ONDon't keep activities
is ON
@mchowning is this still happening on Android? |
I am still seeing this issue, although it presents slightly differently now. After selecting to upload the image, I see the in progress upload icon in the notification bar and the upload does complete successfully, but the image block never gets updated and still has the image placeholder. |
Noting that I'm going to be taking a dive into this issue. :) I'm still seeing the same behaviour that Matt detailed with image.movThe above video comes from testing on the latest Related issues: |
I chatted with @hypest about this issue a bit yesterday, he let me know that the fix for this issue is likely not simple, possibly requiring larger architectural considerations that are a bit beyond the scope of what we're currently trying to achieve. I time-boxed some explorations and confirmed I wasn't able to make progress on a fix. Given that, and the fact this issue isn't impacting a large number of users, I'm un-assigning myself for now. While researching this issue, I came across this work from other developers that may be helpful for people looking into this in the future:
|
In my testing, with |
Image uploading isn't work fine on Android if
Don't keep activities
is turned ON.To reproduce this problem
(Not sure if the upload is going on under the hood or not).
The text was updated successfully, but these errors were encountered: