Android Question SOLVED FirebaseMessaging doesn't start on sleeping Android 7

[tigrot]

Hi everybody,
I'm testing my app. It's composed of services and activities. All services are background and none is sticky or foregound. The FirebaseMessaging service works very well on Android's up to 6. On 7, if the system is running, the message flow is regular, while after a long period of inactivity in background it refuses to receive and process messages. I cannot say if the process was aborted by system. No error is signaled by Firebase crash.
Maybe the process is not restarted when a message is in?
Thank you for help!

Best regards
Mauro

 

[Erel]

Are you sending the messages with the B4J code?

 

[tigrot]

No with B4A, between two phones. If the receiver is awake it works. I have a DB with firebase keys stored.

 

[DonManfred]

Compare your code with the b4j Code... The Json Format is important

 

[tigrot]

I have followed erroneous user's informations. HE TERMINATED THE APP instead of sendind in the background...
Never trust in beta testers! A terminated APP is not too much responsive...

 

[tigrot]

Further investigations proved that the customer swiped away the APP. Since the app is not informed of this I was not able to update customer's record on DB.
Now this is not possible any more. To get rid of App the user must choose to terminate.

 

[Erel]

Since the app is not informed of this I was not able to update customer's record on DB.

The TaskRemoved event is raised in the Starter service.

 

[tigrot]

The TaskRemoved event is raised in the Starter service.

Hi Erel,
this will give me time to update a remote DB?
I think that if the TaskRemove sub execution ends, the process is due to terminate as well. An asyncronous call is likely to fail.

Thank you for your great efforts!
Mauro

 

[Erel]

I think that if the TaskRemove sub execution ends, the process is due to terminate as well. An asyncronous call is likely to fail.

That's true.

 

[tigrot]

The FirebaseMessaging service is now sticky. The user must terminate with the appropriate button.
The whole process is restarted very well, in this case.