Closed Mrnofish closed 3 months ago
Thanks for reporting. I've noticed this earlier on. Though I haven't looked into it, I suspected those numbers and info are stored in the DB and so get all imported. As to the actual downloaded files, they are not imported and don't exist, so some info shown are false.
Yes, I agree this deserves some reasoning.
BTW, I suspect AP behaves the same as the part of import routines are inherited from it
by the way when I imported the antennapod backup all my downloads showed up but upon trying to play them back threw some error and marked as not downloaded.
@o0nd7ots that's normal, it's due to AP dealing with downloads as a cache: that means the files are all stored stored inside the app's private directory which is inaccessible to other apps.
For a full migration, you'll need a way to copy or move the downloaded files inside Podcini's own cache directory. adb shell
might be one.
I thought that it had something to do with the app isolation. It is not a problem to me -- I just wanted to let you know in case this was not working as intended.
Since version 4.10.0 and/or AntennaPod 3.3.2, AntennaPod's DB can not be directly imported. Possibilities need to be investigated.
Podcini.R uses Realm DB, so the SQLite DB of AntennaPod or even Podcini version 5 and below can not be imported reasonable effort.
Checklist
App version
4.4.0
Where did you get the app from
Other
Android version
LOS 20
Device model
guacamole
First occurred
Today
Steps to reproduce
Expected behaviour
I was expecting the app to behave as its cache was empty.
Current behaviour
As far as I can remember, the AP cache should be stored inside the app's own directory under Android/data, so Podcini shouldn't be able to access AP's cache.
When I checked Subs > Statistics, the app was claiming the cache was as large as AP's.
I'm not sure what the issue is here, perhaps a snapshot of the cache status is stored inside the DB and the app didn't check it against the filesystem after importing the DB ?
I would expect users switching from AP to try the same, so there may be some thinking about what's appropriate for the app to do in that situation.
Displaying a warning could be a starting point.
Logs
No response