What steps will reproduce the problem?
1. Update a channel that has some existing new articles.
2. Kill the connection mid-update to simulate poor data reception (cellular
reality)
3. Switch to another app.
What is the expected output? What do you see instead?
RESULT: reader notifies me of new articles, despite update failing.
DESIRED: reader doesn't notify me of "existing" new articles if update fails.
Perhaps instead it
could include failure info with an option to retry; similar to the existing
Retry functionality, but
instead as a notification.
What version of the product are you using? On what operating system?
Latest.
Please provide any additional information below.
The app is likely doing what it is told here, just makes for a slightly wonky
user experience. User:
"Oh there are new articles, great!" Then on realizing the truth: "Oh, it's the
same old articles that
I chose not to read... bleh!"
Original issue reported on code.google.com by case...@gmail.com on 11 Jan 2009 at 5:38
Original issue reported on code.google.com by
case...@gmail.comon 11 Jan 2009 at 5:38