carp-dk / carp-dk/carp_study_app
No notification banner for all surveys not triggered initially with ImmediateTrigger()
- Dominant language
- Dart
- Stars
- 10
- Forks
- 5
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 13
Description
## Device Hardware / Emulator and OS
- **Hardware:** Motorola moto g play - 2023
- **SDK:** Android API level 31
- **App version:** 2.0
- **App deployment mode:** local
## Describe the bug
I have multiple survey tasks in the protocol, and most of them utilize either the RecurrentScheduledTrigger() or the RandomRecurrentTrigger(). While the surveys are triggered, there are no notification banners for them. The only trigger that gives me a notification banner is the ImmediateTrigger(). I have all notifications allowed and each of the RPAppTasks has the notification parameter set to true.
## To Reproduce
1. Create a LocalStudyProtocolManager that implements the StudyProtocolManager (I based this off of the code from the CARP's Pulmonary App's study_protocol_manager.dart file).
2. In the LocalStudyProtocolManager, add a task (ours is in the form of a survey) that is triggered by an ImmediateTrigger().
3. Do the same as step 2, but with RandomRecurrentTrigger() and RecurrentScheduledTrigger().
4. In /blocs/sensing.dart, on line 112, change "LocalResourceManager()" to "LocalStudyProtocolManager()"
5. Run locally.
## Expected behavior
I expected all three tasks to produce a notification banner.
## Actual behavior
Only the task triggered by ImmediateTrigger() gives me a notification banner. The rest of the tasks are triggered but do not notify me.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at /blocs/sensing.dart line 112 and reproduce the protocol with ImmediateTrigger(), RandomRecurrentTrigger(), and RecurrentScheduledTrigger() on Android API 31. Compare the notification behavior for each RPAppTask with notifications enabled and notification set to true; done means all three triggered surveys display a notification banner.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, dart
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100