LAN Sync stopped working v2.4.0

[8rror404]

I sync with a file on the local network. The subscription is: http://192.168.0.3:5000/calendar/filename.ics
Authentication is set, and I can see from the server logs that a connection is successful.

This works fine with v2.3.1 but the sync stopped working with v2.4.0
There are no errors or notifications - it just stopped working.

If i delete the subscription, it does not allow me to re add it, although I can restore from backup.
Note this is http - available from within the LAN.
https fails with the known certificate can't be confirmed problem.

I have reverted to v2.3.1 and all is working ok.

[sunkup]

Probably the same as #693

Tracked in #692

[8rror404]

I have just tried v2.4.1 with http and get HTTP 401 Unauthorised using the same authorisation as v2.3.1

The server logs show the connection was made.

(Also it is hard to enter the authorisation as the screen does not scroll up, and the fields are hidden by the onscreen keyboard. This does not happen when entering https)

I have tried HTTPS - Fails (crashes) after Validating Calendar Resourse... The subscription is not saved.

I have once again reverted to v2.3.1 and all works OK.

[sunkup]

(Also it is hard to enter the authorisation as the screen does not scroll up, and the fields are hidden by the onscreen keyboard. This does not happen when entering https)

True. We will address that in #710

I have just tried v2.4.1 with http and get HTTP 401 Unauthorised using the same authorisation as v2.3.1

Working fine here. With and without authentication.

I have tried HTTPS - Fails (crashes) after Validating Calendar Resourse... The subscription is not saved.

Also working fine. With and without authentication.

I tested with a local nginx instance. Would you mind telling us more about your setup so we can reproduce the issue? Also, if you can, then sharing the adb logs at time of crash showing any exceptions would be super helpful.

[8rror404]

Unfortunately the calendar link is not public (192.168.0.x) so is only available within the LAN. There is no point in sharing.

I have just installed 2.4.2 and the problem remains - Reverted back to 2.3.1 all is ok.

I do not believe there is any further information I can supply and appreciate that there is nothing more that you can do,

[8rror404]

Problem solved.

I installed v2.3.1 from GITHUB and accepted the certificate.
Google Play store then showed that an update was available.
Updated to v2.4.2-gplay (previously purchased) and all is OK.

Thank you for your help.

Edit: If it helps, I have just updated a further device. Before using the approach above, I tried installing 2.4.2 fresh and noticed the 'certificate' screen flicker up and disappear along with a notification. Both disappeared before the certificate could be accepted.

Following the approach above works ok i.e. accept the certificate in v2.3.1 then update to v2.4.2

[8rror404]

Update:

So now we go full circle. After 24 hours on v2.4.2 sync stops (on both updated devices).
Symptoms exactly as per the start of this discussion.

I have reverted back to v2.3.1 on all devices and will remain there for the time being.

[sunkup]

I am sorry to hear that. We would like to help and fix any potential problem, but without being able to reproduce it ourselves or seeing the crash log we can't do much. Rebuilding the setup you have in your LAN to reproduce the problem might become difficult, so if you are able to record the adb logs at the time of crash yourself we would be happy to continue looking into it.

[devvv4ever]

@sunkup fyi: adb logs are attached to the ticket here: https://bitfire-at.zammad.com/#ticket/zoom/11341

[devvv4ever]

The OOM issue is now seperately tracked in #716