GCM push notification works after app Force Stop?
Once you force-stop your app from Settings, your code will not run until something manually runs one of your components (ie the user manually launches an activity).
Therefore after force-stopping your app from Settings, you will not receive GCM messages.
If you want to get notifications you have to manually restart your app.
This is by design since Android 3.1.
Apps that are in the stopped state do not receive broadcast Intents.
Stopped state is:
- when the app is initially installed (before the user runs something in
the app) or - after a Force Stop.
You can find more about this here: http://developer.android.com/about/versions/android-3.1.html#launchcontrols
FCM push notification works after app Force Stop?
If the many posts say that it is not possible, then it's true.
If you have force stopped an app, it means you have abandoned it from doing any task by your wish and this also applies that the app will not be able to receive notifications.
Receive GCM notification even when the app is closed (slide/swiped away)
Closing the app by sliding it (more commonly known as swiping it away) doesn't totally kill the app. Check out this answer in Android Enthusiasts community for a more detailed description. You can see there that it is mentioned that:
..It won't directly causes services to stop..
Since listeners for GCM notifications are Service
s, this would actually mean that there is still a possibility that your app may still continue to receive them regardless if it is swiped away.
Though the result of swiping an app may also differ depending on the device it is running, one may kill/force stop it or other just as mentioned above, will stop background processes.
If the result is, however, the app is killed/force stopped, as mentioned in the answer from the link above:
For stop is a complete kill of the app -- all processes are killed, all services stopped, all notifications removed, all alarms removed, etc.
Which would result for the app to don't receive any kind of notifications at all, as it was designed for Android since version 3.1, as stated in this answer:
Apps that are in the stopped state do not receive broadcast Intents.
Stopped state is:
when the app is initially installed (before the user runs something in the app) or
after a Force Stop.
You can find more about this here: http://developer.android.com/about/versions/android-3.1.html#launchcontrols
Hope this helps clear some things somehow. Cheers! :D
Related Topics
Android Dialogfragment VS Dialog
How to Create a Table with Borders in Android
Differences Between Constraintlayout and Relativelayout
"Failed to Install the Following Android Sdk Packages as Some Licences Have Not Been Accepted" Error
Android: How to Periodically Send Location to a Server
Multi Flavor App Based on Multi Flavor Library in Android Gradle
Customize Android Facebook Login Button
Set Inputtype for an Edittext Programmatically
Software Keyboard Resizes Background Image on Android
Get Altitude by Longitude and Latitude in Android
Remove Icon/Logo from Action Bar on Android
How to Get Device Id for Admob