-
Notifications
You must be signed in to change notification settings - Fork 341
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
Android development is not cleaning up old files #1591
Comments
Could you paste the output of I am expecting the following messages near the exit of
... followed by the actual removal of the files on the device. |
Interesting, I can see that it actually works most of the times, but not always.
I will try to find a pattern to help reproducing it. |
So the easiest way to reproduce it is sending "Ctrl + C" during add-on reload (when sources changes) or during the start.
Only difference is when I ctrl + c during the start, then it ends with this log:
|
This could also happen if the physical connection between the computer and the device is broken (i.e. the cable is unplugged). I suggest that we check the sdcard for directories with the known |
I'll mentor this bug. |
I would like to work on it. |
@onlywicked once you have started to look into it feel free to ask more details if needed (@Rob--W provided some details in #1591 (comment)) |
Fixed by @Vishalghyv in #1965 (old artifacts are detected automaticallly, an additional --adb-remove-old-artifacts cli option can be used to automatically remove them), The fix is going to be included in the next major release (web-ext v5.0.0) |
Is this a feature request or a bug?
Bug
What is the current behavior?
Each execution of:
will create new directory on the SD card and not deleting it afterwards.
After few days of development this consumed 400MB of space on my device.
What is the expected or desired behavior?
There should be some clean-up.
Version information (for bug reports)
v12.0.0
6.8.0
3.0.0
https://www.dropbox.com/s/9hvb6d6rms0fspi/Screenshot%202019-04-29%2015.50.26.png?dl=0
The text was updated successfully, but these errors were encountered: