Closed Bug 821827 Opened 12 years ago Closed 12 years ago

Idle devices are not getting announcements sent to them.

Categories

(Cloud Services :: Server: Product Announcements Campaign Manager, defect)

ARM
Android
defect
Not set
blocker

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: tracy, Assigned: jrconlin)

References

Details

Using latest testing addon to ensure the client is correctly sending http://aws-campaign-manager-dev.services.mozilla.com/announce/1/android/beta/18.0/armeabi-v7a?idle=2, and having a record set to idle of 1 day.  The record is not being received by the device.
assigning to jrconlin
Assignee: nobody → jrconlin
Summary: Idle devices are not getting announcements directed to them. → Idle devices are not getting announcements sent to them.
I've pushed out a candidate fix for this bug to the production server. Note that the unit tests are currently failing for a different reason (possibly sqlite caching related). 

Idle checks should now work correctly. (Helps to use the parameter list for GET)

Once those are fixed, i will push the code and close the bug.
Excellent, this is working now.  

As promised, I'm going to give the entire feature another good once over with a few different devices.  If all looks good, I should be able to sign off by eod today.


JR, also, thanks for the many improvements to the Campaign Admin Panel! 'Tis much more intuitive to use now.
Marking as RESOLVED.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Verified, the server is sending idle specified message to appropriate clients.

rnewman and I are investing if the client is actually up-ticking it's idle timer.  (We testing the server functionality by spoofing the idle fetch with the testing add-on.  

complete sign-off is very near at hand.
Status: RESOLVED → VERIFIED
QA Contact: twalker
You need to log in before you can comment on or make changes to this bug.