Closed chrisstonedev closed 9 years ago
This issue is blocking #12. Analysis incomplete. Rolling over to Sprint 6.
This issue has now been fixed. A seemingly arbitrary attribute was only being sent a common value, but this resulted in Android disregarding new ContentIntent values, assuming that the first one created was being requested again. This attribute is now taking in the WorkoutItem ID as a unique value.
Bug found in demonstration during Sprint 5 planning.
Reproduce: Create new workout via Calorie Negation. Ignore initial notification. Create new workout via Calorie Negation (preferably with different name). Tap on new notification with name of new workout. Name of workout in the completion activity to complete is actually the first notification.