Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SamsungAlarmManager: !@Too many alarms (500) registered from uid #1753

Open
echonox opened this issue Feb 17, 2019 · 1 comment

Comments

Projects
None yet
2 participants
@echonox
Copy link

commented Feb 17, 2019

WARNING: IF YOU IGNORE THIS TEMPLATE, WE'LL IGNORE YOUR ISSUE. YOU MUST FILL THIS IN!

Provide a general summary of the issue.
I know there are tickets opened in past and solved by catching the exception, but the issue isn't completely solved, because after this exception is catched we can no longer schedule notifications, after long googling some developers suggest that we use FLAG_UPDATE_CURRENT instead of the FLAG_CANCEL_CURRENT when getting a Broadcast, as suggested here:

https://stackoverflow.com/questions/29344971/java-lang-securityexception-too-many-alarms-500-registered-from-pid-10790-u

Your Environment

  • Plugin version: 0.9.0-beta.3
  • Platform: Android
  • OS version: 6.0
  • Device manufacturer / model: Galaxy S5
  • Cordova version (cordova -v): 8.12
  • Cordova platform version (cordova platform ls): 8.0

Expected Behavior

Alarm should be scheduled unlimited amount of times on Samsung Devices

Actual Behavior

After some time the App introduces A limit exception by the Samsung Alarm Manager

Steps to Reproduce

No Specific Repro

Context

Schedule/Update/Cancel Notifications

Debug logs

019-02-16 12:22:06.520 3663-10680/? W/SamsungAlarmManager: !@too many alarms (500) registered from uid 10285
2019-02-16 12:22:06.584 3663-4992/? W/SamsungAlarmManager: !@too many alarms (500) registered from uid 10285
2019-02-16 12:22:07.211 3663-4486/? W/SamsungAlarmManager: !@too many alarms (500) registered from uid 10285
2019-02-16 12:22:07.258 3663-7502/? W/SamsungAlarmManager: !@too many alarms (500) registered from uid 10285
2019-02-16 12:22:07.289 3663-4992/? W/SamsungAlarmManager: !@too many alarms (500) registered from uid 10285
2019-02-16 12:22:07.328 3663-10680/? W/SamsungAlarmManager: !@too many alarms (500) registered from uid 10285
2019-02-16 12:22:07.350 3663-3679/? W/SamsungAlarmManager: !@too many alarms (500) registered from uid 10285
2019-02-16 12:22:07.409 3663-5573/? W/SamsungAlarmManager: !@too many alarms (500) registered from uid 10285
2019-02-16 12:22:07.479 3663-4486/? W/SamsungAlarmManager: !@too many alarms (500) registered from uid 10285
2019-02-16 12:22:07.533 3663-10680/? W/SamsungAlarmManager: !@too many alarms (500) registered from uid 10285
2019-02-16 12:22:07.553 3663-3680/? W/SamsungAlarmManager: !@too many alarms (500) registered from uid 10285
2019-02-16 12:22:07.638 3663-7502/? W/SamsungAlarmManager: !@too many alarms (500) registered from uid 10285
2019-02-16 12:22:07.653 3663-4992/? W/SamsungAlarmManager: !@too many alarms (500) registered from uid 10285
2019-02-16 12:22:07.734 3663-11255/? W/SamsungAlarmManager: !@too many alarms (500) registered from uid 10285

@GitToTheHub

This comment has been minimized.

Copy link
Contributor

commented Apr 17, 2019

Duplicates #1701 but this issue gives additional Infos

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.