sleep one second before websocket reconnect

[mahibi]

otherwise it's an endless loop without delay which may stress the devices...

🏁 Checklist

• ⛑️ Tests (unit and/or integration) are included or not needed
• 🔖 Capability is checked or not needed
• 🔙 Backport requests are created or not needed: /backport to stable-xx.x
• 📅 Milestone is set
• 🌸 PR title is meaningful (if it should be in the changelog: is it meaningful to users?)

[mahibi]

/backport to stable-20.0

[SystemKeeper]

otherwise it's an endless loop

Which would raise the question if there should be an error at some point? But yes, we are doing something similar in ios and increase the timeout up to a certain threshold:
https://github.com/nextcloud/talk-ios/blob/83bed85d475e2c38fb63db1caa3eb4e040fcb2ce/NextcloudTalk/NCExternalSignalingController.m#L225-L239

[github-actions]

Codacy

Lint

Type	master	PR
Warnings	86	92
Errors	131	131

SpotBugs

Category	Base	New
Bad practice	6	6
Correctness	11	11
Dodgy code	78	78
Internationalization	3	3
Malicious code vulnerability	3	3
Performance	6	6
Security	1	1
Total	108	108

Lint increased!

[github-actions]

APK file: https://www.kaminsky.me/nc-dev/android-artifacts/4194-talk.apk



To test this change/fix you can simply download above APK file and install and test it in parallel to your existing Nextcloud Talk app.

[mahibi]

otherwise it's an endless loop

Which would raise the question if there should be an error at some point? But yes, we are doing something similar in ios and increase the timeout up to a certain threshold: https://github.com/nextcloud/talk-ios/blob/83bed85d475e2c38fb63db1caa3eb4e040fcb2ce/NextcloudTalk/NCExternalSignalingController.m#L225-L239

If internet connection itself is lost then the user is informed. You suggest to still inform about if the websocket reconnect fails (maybe also for other reasons than lost internet?).

Increase the timeout will also be done 👍