Fatal Exception: java.lang.SecurityException: !@Too many alarms (500) registered inside Firebase
From the firebase-talk mailing list:
We've found the cause of this bug. The FCM SDK can get stuck while syncing the (un)subscribed list of topics. The bug can happen when the device is offline during the subscribeToTopic / unsubscribeFromTopic operations and can lead to battery draining and app crashes on specific Samsung devices. The only way to exit this state is to connect the phone to the internet and open the app to allow the topics list to sync with the server.
We are close to a fix, but due to our release cycle, we won't have a new SDK in your hands for at least a few weeks. For now, you can downgrade to 9.4.0 as Mihir suggested.
android limit of notifications in alarm manager
For Alarm notifications, and based on my experience, Samsung devices have a limit of 500 scheduded alarms (no matter if I cancel the alarms or set the flag FLAG_CANCEL_CURRENT).
I don't found this limit on Nexus or other android manufacturer.
More info:
java.lang.SecurityException: !@Too many alarms (500) registered from pid 10790 uid 10206
Related Topics
Using JSON File in Android App Resources
How to Compile C into an Executable Binary File and Run It in Android from Android Shell
Rawquery(Query, Selectionargs)
Android Studio Doesn't Recognize My Device
Androidstudio - Module Dependencies in Gradle
Avoiding Content Type Issues When Downloading a File via Browser on Android
Dialogfragment with Clear Background (Not Dimmed)
How to Write Jarlist Cache File While Creating Android Project
How to Include Data Files with the App's APK
Android: How to Convert Whole Imageview to Bitmap
Programmatically Collapse a Group in Expandablelistview
How to Use Android Canvas to Draw a Rectangle with Only Topleft and Topright Corners Round
Cursorloader Not Updating After Data Change
Can't Upgrade Android Sdk Tools
How to Capture an Image in Background Without Using the Camera Application