Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

App/WebSocket does not restart automatically after update #421

Open
1 task done
ColorfulRhino opened this issue Jan 14, 2025 · 0 comments
Open
1 task done

App/WebSocket does not restart automatically after update #421

ColorfulRhino opened this issue Jan 14, 2025 · 0 comments
Labels
bug Probable bug

Comments

@ColorfulRhino
Copy link

ColorfulRhino commented Jan 14, 2025

Guidelines

  • Yes, I have searched for existing issues

Bug Description

Steps to reproduce:

  1. Have a Molly version older than the latest one installed
  2. Have the app's WebSocket running in the background to receive notifications
  3. Update Molly (manual or automatic) by your preferred app store (e.g. through Molly's F-Droid repo or Accrescent or Obtainium)
  4. Do not open Molly manually

Expected behaviour:

  • Molly starts itself and its WebSocket service right after it has been updated (like many other apps do)
  • Notifications and calls can be received like normal

Actual behaviour:

  • Molly does not start after it has been updated, thus its WebSocket is not running in the background anymore
  • New messages or calls are not received since Molly is not running in the background
  • Molly has to be started manually by opening the app, only then are messages received and notifications shown

Notes

I have observed this issue by updating Molly-FOSS to version v7.29.3-1, running on Android 15.
Molly has unresticted battery usage in background enabled.

This issue is especially bad when you use auto-updates for Molly since maybe you are waiting for an important text or call, but in the meantime Molly gets auto-updated. If you don't open Molly manually, you will miss those important message or call.

Screenshots

No response

Device Model

No response

Android Version

Android 15

App Version

v7.29.3-1-FOSS

Link to Debug Log

No response

@valldrac valldrac added the bug Probable bug label Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Probable bug
Development

No branches or pull requests

2 participants