yuvipanda / WPSignpost

Wikipedia Signpost Android Application
8 stars 5 forks source link

app does not update with the new issue #41

Closed ragesoss closed 12 years ago

ragesoss commented 12 years ago

The new Signpost (August 20 edition) isn't showing up. The app still shows the August 13 issue, which was the newest one when I installed the latest Beta1 apk.

ragesoss commented 12 years ago

After multiple times of opening and closing the app, it finally decided to update to the new issue. I'm not sure why it did that, or how to force it to update next time, though.

yuvipanda commented 12 years ago

Sure? I see the latest issue all right On Aug 22, 2012 1:19 AM, "Sage Ross" notifications@github.com wrote:

The new Signpost (August 20 edition) isn't showing up. The app still shows the August 13 issue, which was the newest one when I installed the latest Beta1 apk.

— Reply to this email directly or view it on GitHubhttps://github.com/yuvipanda/WPSignpost/issues/41.

ragesoss commented 12 years ago

Under what circumstances does the app search for new content? A refresh button would be good, I think, for when users are anxiously awaiting the new issue and can't bring themselves to do anything but check over and over if it's ready yet.

yuvipanda commented 12 years ago

The app currently checks only on initial start - so a single force kill should've done it. I'll add a 'Latest issue' button someplace

ragesoss commented 12 years ago

Okay. It must have been that the app was still hanging around in memory for a long time without being killed. Probably a common situation for newer phones.

(sent from my phone) On Aug 22, 2012 8:09 AM, "Yuvi Panda" notifications@github.com wrote:

The app currently checks only on initial start - so a single force kill should've done it. I'll add a 'Latest issue' button someplace

— Reply to this email directly or view it on GitHubhttps://github.com/yuvipanda/WPSignpost/issues/41#issuecomment-7932106.

yuvipanda commented 12 years ago

In this case it was also the case that I had forgotten to run the cronjob that updates the issues (haven't set it up yet), and ran it manually only when I saw this issue :P That explains the extra delays.

ragesoss commented 12 years ago

So it phones home to the toolserver or something for new issues?

(sent from my phone) On Aug 22, 2012 8:14 AM, "Yuvi Panda" notifications@github.com wrote:

In this case it was also the case that I had forgotten to run the cronjob that updates the issues (haven't set it up yet), and ran it manually only when I saw this issue :P That explains the extra delays.

— Reply to this email directly or view it on GitHubhttps://github.com/yuvipanda/WPSignpost/issues/41#issuecomment-7932198.

yuvipanda commented 12 years ago

It hits my server (at yuvi.in/signpost). See the api/ folder here to see the code that runs there

yuvipanda commented 12 years ago

Fixed. Added a menu item 'See latest Issue'. Suggestions for better wording welcome!