I'd like to follow up on this thread which unfortunately is closed. After I've talked to internal app developers and investigates the issue with 3CX app not being launched when being called I'd like to add a piece of information that might be helpful:
Case 1: Not receiving push notifications after “force closing” the app.
This is by design starting from Android 3.1. StackOverflow has a nice post on this. So force closing the app is not a valid test scenario for 3CX push notifications. The behavior is also the same for all applications such as WhatsApp, Signal etc.
Case 2: Not receiving push notifications after restarting the phone
This behaves differently for 3CX and other messaging apps like WhatsApp, Signal etc. While 3CX does not receive push / open on call until the app has been started once, other messengers are able to receive messages after a phone restart without opening the app. Going through the phone's service list (developer tools) after a restart, I can see that other apps are automatically starting a background service on boot, 3CX does not. After launching the app once there is a 3CX service in background. So maybe there is something wrong with the service registration on boot? Also there is a post on StackOverflow on this issue.
Maybe this information helps to make a step forward with this issue. If not, feel free to close this thread.
Best regards,
Matthias
Case 1: Not receiving push notifications after “force closing” the app.
This is by design starting from Android 3.1. StackOverflow has a nice post on this. So force closing the app is not a valid test scenario for 3CX push notifications. The behavior is also the same for all applications such as WhatsApp, Signal etc.
Case 2: Not receiving push notifications after restarting the phone
This behaves differently for 3CX and other messaging apps like WhatsApp, Signal etc. While 3CX does not receive push / open on call until the app has been started once, other messengers are able to receive messages after a phone restart without opening the app. Going through the phone's service list (developer tools) after a restart, I can see that other apps are automatically starting a background service on boot, 3CX does not. After launching the app once there is a 3CX service in background. So maybe there is something wrong with the service registration on boot? Also there is a post on StackOverflow on this issue.
Maybe this information helps to make a step forward with this issue. If not, feel free to close this thread.
Best regards,
Matthias
