Background polling notifications not working

[EchedelleLR]

Describe the bug

Background polling notifications, old default as suggested by 1.1.0.495 release notes, are not working anymore being the app fully killed in background and make one to open it to receive new messages and notifications.

As I use microG in my device, I also could check, that, for some strange reason, from the upgrade, Session was registered on FCM by default in my device even without choosing the option (my friend uses stock with all Firebase services).

To reproduce

Upgrade to the 1.1.0.495 version and choose background polling as default notifications receiver.

Screenshots or logs

Confirmation of 1.1.0.495 and info on release notes telling that background polling was default before (which is incredible for me):

The confirmation about Session being registered in microG:

Smartphone (please complete the following information):

• Device: BQ Aquaris U Plus (me), BQ Aquaris U2 (my friend)
• OS: LineageOS 14.1 from microG (me), Android 8.1.0 from stock (my friend)
• Version of Loki Messenger: 1.1.0.495 for both

Additional context Nothing by now.

An additional comment would be that this seems like a way to force new users to choose FCM (if its working) instead of background polling...

[KeeJef]

I dont think there has been any changes to background polling for messages maybe @Mikunj knows. The reality is its just really unreliable because the Android OS limits the tasks Session is allowed to do in the background to cut down on battery usage, we dont really get any visibility into how the Android OS manages background tasks either.

[EchedelleLR]

It was working until the last release... I am sure its related with the option to enable FCM or maintain polling background. I have been using LineageOS 14.1 in this device with battery optimizations disabled and working as espected with other apps using a similar system (and without permanent notification).

[EchedelleLR]

@KeeJef just thinking. Does https://dontkillmyapp.com not help with that a bit?

[lrq3000]

This paper (although from a predatory publisher) can be of interest: Push Attack: Binding Virtual and Real Identities Using Mobile Push Notifications

[realjench]

+1

Please fix this.

Expose ip AND DEVICE token ID is a real exposure with FCM

Thanks

[realjench]

+1

Please fix this.

Expose ip AND DEVICE token ID is a real exposure with FCM

Thanks

Why not waiting for the fix, add Tor usage for FCM?