Closed Bug 818093 Opened 13 years ago Closed 13 years ago

Client can't handle multiple announcements

Categories

(Android Background Services Graveyard :: Product Announcements, defect)

Product:
Android Background Services Graveyard
Component:
Product Announcements
Platform:
ARM
All
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
VERIFIED INVALID

People

(Reporter: tracy, Unassigned)

Details

Disable product announcements on the device. Create a couple new records. Then enable announcements on the device. If there are two or more active records on the server, the client will display only the first one it receives. In this case, I think it's the most recently created record that the server gives out first. The client does get the additional announcement, but skips displaying it as reported in the logs. Once skipped, the announcement is lost.
QA Contact: twalker
This is by design. It's the responsibility of the campaign author to eliminate overlap. We don't want to spam our users!
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
ok, PMM needs to carefully manage announcement overlap.
Status: RESOLVED → VERIFIED
Component: Android: Product Announcements → Product Announcements
Product: Mozilla Services → Android Background Services
QA Contact: twalker
You need to log in before you can comment on or make changes to this bug.