Auto-refresh: Unable to resolve host “...”: No address associated with hostname

[Telos]

Yes. Updated and space available. Not every sync fails. I’m not sure the source, but in Android 10 I have excluded the app from battery optimization. I’ll see in a few days, If not connection issues, I will return app to battery optimization to see if connections fails reoccur. Thank you.

[AllesAufHorst]

@AllesAufHorst said in Public Google calendar refuses to auto-refresh:

I think I suffer from the same problem as in the latest comment.

I’m trying to sync a calendar with the following address:

https://www.google.com/calendar/ical/smh0j8o8blctcl01jdbahutp8c%40group.calendar.google.com/public/basic.ics
(from this website: https://www.fussball-spielplan.de/spielplan-preussen-munster-ical/)

However, for a couple of days now, I receive the following error message once per day (which is my sync interval):

Unable to resolve host “calendar.google.com”: No address associated with hostname

I noticed that the associated web address is depicted a little bit different than what I entered in the first place? It reads

https://calendar.google.com/calendar/ical/smh0j8o8blctcl01jdbahutp8c%40group.calendar.google.com/public/basic.ics

Manual syncronisation appears to work, though.

Apologies for bumping, but I think this never drew any attention, did it? The problem persists to this day.

[AllesAufHorst]

May I ask the developers if they acknowledge this bug? Did you ever try to reproduce it?

[rfc2822]

@allesaufhorst There are several reports about this problem. I have now pointed them all to this thread for following up.

Unfortunately, I still don’t know why Android sometimes seem to start ICSx5 synchronization when Internet is not ready yet; nor could I reproduce the problem myself.

Any further information welcome.

[devvv4ever]

@AllesAufHorst @Telos @Augustin What I would like to know: does the error occur only over night when the device is in sleep mode (and you see the error message then in the morning), or does it also occur over daytime when the device is in actual use.

[Telos]

@devvv4ever said in Auto-refresh: Unable to resolve host “...”: No address associated with hostname:

@AllesAufHorst @Telos @Augustin What I would like to know: does the error occur only over night when the device is in sleep mode (and you see the error message then in the morning), or does it also occur over daytime when the device is in actual use.

Removing the app from battery optimization solved my issues. As I recall, the issue happened during the day. Since posting my Android version updated, so I don’t know if it remains an issue when battery optimization is allowed. Sorry to be of little help.

[Oclair]

1. Yea I’m having the same problem with google calendar feeds once every two days,

2. even though the app is set to refresh every week…

This is on a different phone than the one I reported back a few months ago…

3. I get a seperat error per feed, it links to the specific feed instead of the list of feeds

Be safe everyone!

[AllesAufHorst]

@devvv4ever As far as I can tell, this always occurs during daytime. Perhaps more importantly, it often happens in the very moment when I plug in my charger, with the screen unlocked.

[devvv4ever]

@allesaufhorst said in Auto-refresh: Unable to resolve host “...”: No address associated with hostname:

@devvv4ever As far as I can tell, this always occurs during daytime. Perhaps more importantly, it often happens in the very moment when I plug in my charger, with the screen unlocked.

interesting, thanks! When Android device get into charging state they can use as much power as they want, which measns that syncs are immideately scheduled and performed - but maybe the network was not ready by that time or somehow blocked because other system processes locked it for a very short period.

[AllesAufHorst]

@devvv4ever If it helps, I might try to grab logs next time?
Out of curiosity, have you tried to reproduce the problem yourself?

[devvv4ever]

@allesaufhorst yes, I was affected myself on my production device about a year ago, however when I excluded it from battery saving of Samsung the problem started to disappear, and now I can’t reproduce it anymore…

I think adb logs would maybe help a little bit. Personally I think this is a bug in Android, but maybe we can workaround it by putting a hard-coded “wait” time before every sync is processed - however that would be very dirty…