Closed GoogleCodeExporter closed 9 years ago
* Also please include if you are adding from search or recommendations ! *
Thank you.
Original comment by OlliTech
on 7 Apr 2010 at 6:15
Timezone: EST
Time issue occurred: 8:51 AM
Carrier: Verizon
Android Version: 2.1
Device: Droid
Added from Search
Original comment by jon.me...@gmail.com
on 8 Apr 2010 at 12:52
http://code.google.com/p/queueman/source/diff?spec=svn150&r=136&format=side&path
=/trunk/QueueMan/src/edwardawebb/queueman/classes/NetFlix.java&old_path=/trunk/Q
ueueMan/src/edwardawebb/queueman/classes/NetFlix.java&old=125
Original comment by OlliTech
on 8 Apr 2010 at 1:41
From David Perez:
Time Zone: eastern
Carrier: Verizon
OS: 2.1 update 1 (but it was happening on the latest build of 2.0 also)
Device: Motorola Droid
9:05 am Big Trouble in Little China bottom of the DVD que from search
9:13 am Battlestar Galactica season 1 DVD Top of que from recommendations
9:13 am The Office season 1 Instant from recommendations
Original comment by OlliTech
on 8 Apr 2010 at 1:42
I have temporarily rolledbackk to version 0.9.9.1 (r138).
This version was tested on my g1 and nexus one to successfully add titles and
rate
titles.
Please visit the Market and update QueueMan ( Market > Menu > Downloads)
Original comment by OlliTech
on 10 Apr 2010 at 1:32
Timezone: EDT
Carrier: Verizon
Android Version: 2.1 (but it was happening with
2.0.1 too)
Device: Motorola Droid
Adding from Search (haven't tried from
Recommendation)
Just did the downgrade to 0.9.9.1 and I'm glad to
report that it's working on my end. Just out of
curiosity, what features of the last version are not
present in the temporary rollback?
Original comment by gcon...@gmail.com
on 10 Apr 2010 at 3:24
You can see the change log here, anything after Jan 30. will be missing, or
still an
issue.
http://code.google.com/p/queueman/issues/list?can=7&q=&sort=-modified&colspec=ID
%20Type%20Status%20Priority%20Milestone%20Owner%20Summary%20Modified
Original comment by OlliTech
on 10 Apr 2010 at 4:04
Just an idea... you said that this problem appeared sometime in March and you
also
mentioned the possibility that all this could be caused by a timestamp issue.
In March 14, DST kicked in. It might be that Netflix API is not handling well
the new DST
transition dates.
Perhaps it might help you if people affected by this problem would also tell
you if they are
living in a DST area. I am.
Original comment by gcon...@gmail.com
on 10 Apr 2010 at 11:38
Original issue reported on code.google.com by
OlliTech
on 6 Apr 2010 at 5:02