Sync with Nextcloud Gpoddersync fails #49
Comments
|
I see. Thanks for reporting. So someone use the server-based sync. I was thinking about removing the feature of sync to servers, focusing more on wifi/instant sync. Can you give some comment on #48 ? |
|
I stripped the first "/" and a release will be out shortly. Since I don't have such a server set up, I would rely on any feedback to see if it works. |
|
This glitch has been there for ages, since the older AntennaPod. Amazing it's just surfaced. |
|
Please confirm this? |
|
Sorry, for the late reply. I've been very busy lately and F-Droid takes some time to push out your update. |
|
Glad it works. |
|
Hello, i got the Error "404" when trying to sync with gpoddersync on nextcloud. However i cant easily provide logs. Im using the newest version. AnetennaPod sync works flawless. |
|
Sorry about that. I will check what might a problem there. The thing again is I don't have a test environment for that. Can someone explain in some detail why exactly you need sync with a server like gpoddersync? |
|
In my case because I listen to podcast on my pc via nextcloud via repod addon or kasts and on my phone via podcini. In order to always have the same subscription and played Informations, it's synced with gpoddersync |
|
I see. Do you know in which recent version the sync works? |
|
The latest version I used before was the latest version 5,i believe. The latest one before you updated the packageid |
|
Do you know if it's 5.5.5, 5.5.4, ...? |
|
Seems this is broken in 5.5.1 and 6.0.0 builds on top of 5.5.2, and the most recent version 6 releases stay compatible with 5.5.5 in terms of these sync features. Since 5.5.1 and 6.0.0, three properties have been added to EpisodeActions: These improve wifi sync as well as import/export of progress, but possibly break the nextcloud and gpoddernet syncs which don't include these properties. In the coming 6.1.6 I removed these properties when syncing with either of the two servers. Let me know that helped. |
|
thanks for your fast work, but it still reports "code 404" |
|
Hum, I see. I guess @theheckwr confirmed it worked with 5.5.0 (or some version earlier but later than 5.4.0). Could you do a test on 5.5.0 and 5.5.1 and let me know if my assumption that the former works and the latter doesn't is correct? |
|
@d3ighty I think it's more likely an issue with your connection with the server. Are you sure you have specified the correct hostname and port number etc? When you start using Podcini.R (i.e. version 6), you need to redo the settings. Sure, you can import the settings from version 5, but can you verify all the settings are correct, just in cases there might be errors in the import process? |
|
5.5.0 and 5.5.1 are working, i just tested those. However i dont import settings and did a clean install, because i only need to change a few settings and and i was sure, a lot of things changed since i last updated. Hostname etc is the same for all versions. |
|
I see. That's good to know. |
|
Also, I wonder, in Settings->Synchronization, when you enter the server address in the Login dialog and then press "Proceed to login", did it succeed? |
|
It does succeed. I'm looking if I can provide any logs. |
|
And, if you don't mind, can you export and send me the preference file? it should "ac.mdiq.podcini_preferences.xml" in the exported directory. |
|
Here you go. Ive renamed to txt file. So github supports it. |
|
I just exported the preferences from 5.1.1 and imported to newest 6 version, and now the syncs seems to work. Atleast it's in my sync settings and I just imported podcasts, but the episodes status, categories or whatever wasn't synced |
|
That's interesting. can you send me the new preference file? the previous file doesn't contain relevant info, wonder why. to update your episodes status, you need to import the podcasts first, then import the progress. To get a best progress file, it's better exporting it from 5.5.5. categories and podcast settings are not available for import. |
|
New file looks identical. Which entry are you looking for? |
|
Sorry, it should be this file instead: gpodder.net.xml I wonder what are the differences between the new one and the old one, especially for prefGpodnetHostname, prefHostport |
|
Also the same entry for old and new file. |
|
Wow, that's really strange it didn't work before. |
|
I would say, that version 6 writes doesn't save the login or whatever. I'm glad it's working with the export workaround. Looking forward for future features |
|
So you said gpodder.net.xml is the same before and after you import the preferences? So before importing, it has the login etc? Can you verify that? I would like to get this right for other users. |
|
Podcini 6 before import: no gpodderxml at all, because of the 404 error. I hope that's what you meant |
|
I see. Thank you. |
|
Hey, I have the same issue trying to sync against my nextcloud. Im using the new Podcini.R version 6.6.6 from fdroid. The main thing I can contribute to this discussion is that it did and does work with the old podcini app version 5.5.2 from fdroid. |
|
@Dacid99 Thanks for the info. In discussing with @d3ighty , I had the impression that gpodder.net.xml was not saved in Podcini.R, but I'm not sure how come. He seemed to work around it by importing all the preferences (including gpodder.net.xml) from version 5 and get it work for version 6. Can you test it if it's the case? Then I will try to figure out what is happening (my difficulty on this is that I don't have such a server set up for testing). |
|
Yes I tried it and I can fully back up what has already been found. I can export the gpodder.net.xml on the old version (5.5.2), on the new version (6.6.6) it doesnt exist. When I import the preferences from the old into the new version, the sync seems to work. |
|
I've tried looking into the code but as far as I could tell all that changed from 5.5.2 to the first version 6 fdroid release was the location of the classes in charge of sync. Maybe something in the manifest or other metafiles causes the issue. I may do some debugging tomorrow in case I remain curious of this issue.. |
|
Appreciate your effort @Dacid99 |
|
I found the bug and am looking for the best fix. Ill send you a pull request probably by tomorrow |
|
I am unable to get episode played state updates from Gpoddersync. Not sure if this falls under this issue or if a new one should be opened. When syncing with nextcloud there are no errors and the podcasts I am subscribed too are synced. But not the played state. Have confirmed they are correctly stored on the server as the are synced to other players (AntennaPod). Android version: 14 |
|
Perhaps @Dacid99 is more capable of sorting this out? |
|
Ill look into it. I dont have my test phone with me right now so it may take until the weekend for me to take action |
|
Hello, Was anything further found about this? I am now using the below and all my subscriptions have disappeared including listening history. As if I just downloaded the app for the first time. Android version: 14 |
|
To confirm, does this mean there is no timeline or place on the roadmap to resolve the syncing issues? |
|
Hopefully someone can contribute on this. @Dacid99 did something on this before, not sure if he is in a position to further sort this out. Otherwise, it's a lower priority for me, not because it's not important, but because it takes more effort for me to set up the extra testing system. |
|
Hey sorry for taking so long, I can reproduve this to some extent but right now i dont have the time to dive deeper into this. |
|
No, not due to port to kotlin (that's long time ago). Didn't it work up until some recent time? must be due to some change in the recent few versions. |
Checklist
App version
5.4.0 (36e1823)
Where did you get the app from
F-Droid
Android version
LineageOS 21-24240318-NIGHLY-pstar (Android 14)
Device model
No response
First occurred
No response
Steps to reproduce
Expected behaviour
Sync successfully
Current behaviour
Sync fails, sometimes reports:
Logs
On the server's access log:
⇒ That "//" at the beginning seems to be the problem (this issue of Antenna Pod seems similar)
The text was updated successfully, but these errors were encountered: