Badge count and Forum Runner 1.3.0

[Morac]

It's nice that the new version of Forum Runner checks for the badge count when resumed, but I have an issue with how it checks when it's running.

It only checks if I go to the home screen. So say I have 3 new subscribed threads in a forum and I read all 3 and go back to the subscribed tab. At this point I have no new threads, but if I exit the app it still lists 3 unless I go to the home page before exiting.

It seems like the app should know that there were 3 unread items on the home screen originally and 3 unread subscribed threads in the forum. If I read all 3 unsubscribed threads I would think the app would update the badge count to 0. Basically subtract read threads/messages from the badge count.

Is there anything that can be done about this?

[ClemsonJeeper]

Yes. I'll put it on the (long) list. :)

[bruce73]

It only checks if I go to the home screen. So say I have 3 new subscribed threads in a forum and I read all 3 and go back to the subscribed tab. At this point I have no new threads, but if I exit the app it still lists 3 unless I go to the home page before exiting.

I'm seeing the same thing, but can't get rid of the counter even if I go the list of forums and mark all posts read (is this what you mean by the "home page"?).

So the "3" never goes away. Even uninstalling/reinstalling the app doesn't work. <grrrr>

[ClemsonJeeper]

I'm seeing the same thing, but can't get rid of the counter even if I go the list of forums and mark all posts read (is this what you mean by the "home page"?).

So the "3" never goes away. Even uninstalling/reinstalling the app doesn't work. <grrrr>

Are you sure you have:

1) Updated to the latest version of Forum Runner (1.3.1)
2) Have *no* private messages or new thread subscriptions
3) Have visited the "Home" page (eg: The page with "Forum Browser", "Forum Runner Support", etc) on the full version of Forum Runner?

[Morac]

1) Updated to the latest version of Forum Runner (1.3.1)


AVSForum 1.3.1 hasn't been released yet. At least the app store still shows 1.3.0.1 from Aug 30th.

Speaking of 1.3.1, which I'm beta testing, push notifications still have a tendency to be way off with respect to the badge count. The server side count only appears to reset once a day.

[bruce73]

Are you sure you have:

1) Updated to the latest version of Forum Runner (1.3.1)
2) Have *no* private messages or new thread subscriptions
3) Have visited the "Home" page (eg: The page with "Forum Browser", "Forum Runner Support", etc) on the full version of Forum Runner?

My bad, I'm referring to the AVS Forum specific app, so sorry if I'm in the wrong thread. But, FWIW, yes, I'm on the latest version (1.3.0.1) and the badge count remains static regardless if all posts/messages are read and if the app is completely closed, uninstalled, whatever. Looks as if Morac has a handle on the problem, so I'll just sit back and read. ;)

BTW, I did tryout the ForumRunner app, but searching for AVS Forum yielded no results. :confused:

[ClemsonJeeper]

My bad, I'm referring to the AVS Forum specific app, so sorry if I'm in the wrong thread. But, FWIW, yes, I'm on the latest version (1.3.0.1) and the badge count remains static regardless if all posts/messages are read and if the app is completely closed, uninstalled, whatever. Looks as if Morac has a handle on the problem, so I'll just sit back and read. ;)

BTW, I did tryout the ForumRunner app, but searching for AVS Forum yielded no results. :confused:

Yes, that is the way the admins of AVS Forum wanted it.

Morac and I determined that the 1.3.0.1 (which is actually 1.3.1, I know... fun) didn't have the fix in it, but the new one 1.3.2 which is still being reviewed by Apple does.

So once 1.3.2 comes out, and you upgrade, and if you still have the problem, then I quit!! (haha, just kidding)

[bruce73]

Yes, that is the way the admins of AVS Forum wanted it.

Morac and I determined that the 1.3.0.1 (which is actually 1.3.1, I know... fun) didn't have the fix in it, but the new one 1.3.2 which is still being reviewed by Apple does.

So once 1.3.2 comes out, and you upgrade, and if you still have the problem, then I quit!! (haha, just kidding)
Sounds good to me (not that you quit, that the problem disappears ;)). Thanks, bud.

EDIT: Just grabbed the 1.3.2 version and it seems to have resolved the problem. Thx!

[gongloo]

Yes, that is the way the admins of AVS Forum wanted it.

Morac and I determined that the 1.3.0.1 (which is actually 1.3.1, I know... fun) didn't have the fix in it, but the new one 1.3.2 which is still being reviewed by Apple does.

So once 1.3.2 comes out, and you upgrade, and if you still have the problem, then I quit!! (haha, just kidding)

I'm having the same issue with the NASIOC branded app (1.3.0.1), FYI. Has that been re-submitted as 1.3.2 as well?

Update 9/17/2010: Fixed in the latest 1.3.2 release of the NASIOC branded app.

[ClemsonJeeper]

Yep, when I submit versions for update, they usually go out at the exact same time. However that doesn't necessarily mean Apple approves them all at once... :)

So 1.3.2 fixes the issue?

Nice. Please leave 5 star reviews and comments on the App Store... helps out. ;-)

[gongloo]

So 1.3.2 fixes the issue?

Yes.

Please leave 5 star reviews and comments on the App Store... helps out. ;-)

Will do!

[bruce73]

Ermmm ... it fixed the badge counter itself, but now when you open the app (say there are 5 new messages), the new message button on those particular threads in the subscribed threads list gets erased along with the counter number. Which means, with a list of subscribed threads, you don't know (unless you look *very* quickly, and then only with the ones showing) which threads have new posts.

EDIT: OK, I just realized that the date of the last post is there, so that helps a bit, but it would be better if the new post button didn't erase until actually reading the new post(s). Also, what's the paperclip icon mean -- threads that I've replied to?

[ClemsonJeeper]

Ermmm ... it fixed the badge counter itself, but now when you open the app (say there are 5 new messages), the new message button on those particular threads in the subscribed threads list gets erased along with the counter number. Which means, with a list of subscribed threads, you don't know (unless you look *very* quickly, and then only with the ones showing) which threads have new posts.

Sorry, I'm confused what you mean.

What is the "new message button"? Are you talking about the blue dot next to threads with unread posts? Those are fetched directly from the forum so if the forum thinks the threads are read, they won't show up. If that's not what you meant, can you please let me know exactly what you are referring to?



EDIT: OK, I just realized that the date of the last post is there, so that helps a bit, but it would be better if the new post button didn't erase until actually reading the new post(s). Also, what's the paperclip icon mean -- threads that I've replied to?

paper clip is a thread with attachments.

[bruce73]

What is the "new message button"? Are you talking about the blue dot next to threads with unread posts? Those are fetched directly from the forum so if the forum thinks the threads are read, they won't show up. If that's not what you meant, can you please let me know exactly what you are referring to?

Yes, sorry, I'm referring to the blue button, indicating a thread with new messages. Shouldn't the button be visible until you actually go into the thread? That's not what's happening. It vanishes (along with the numbered counter) when the app is opened. If there are unread messages on multiple threads, it makes it harder to ascertain which threads to read.

Also, one more thing -- I just checked, and the counter said I had '8' new messages. But when I opened the app, there was, in fact, only one new message in all my subscribed threads. I don't know where the '8' came from.

[ClemsonJeeper]

Yes, sorry, I'm referring to the blue button, indicating a thread with new messages. Shouldn't the button be visible until you actually go into the thread? That's not what's happening. It vanishes (along with the numbered counter) when the app is opened. If there are unread messages on multiple threads, it makes it harder to ascertain which threads to read.

Also, one more thing -- I just checked, and the counter said I had '8' new messages. But when I opened the app, there was, in fact, only one new message in all my subscribed threads. I don't know where the '8' came from.

Yes. But like I said, the blue dot is only there if the forum reports that it should be there. There are any number of things that contribute to a thread being marked as "read" when in reality you have never gone into it. The main reason is that the forum you are on doesn't use database backed thread marking. Which means they are stored in cookies which don't transfer between the app and your desktop browser. Also many forums mark threads read after a certain period.

Incidentally which forum are you talking about? And are you talking about the main forum runner app or a branded version?

The 8 likely came from a Push notification. The app syncs up with the push notification servers when you launch it. If you read pms or subscribed threads from a browser, the push notification server has no idea you did, so its count will be off if a new notification is sent until you launch the app again.

[Morac]

Yes. But like I said, the blue dot is only there if the forum reports that it should be there. There are any number of things that contribute to a thread being marked as "read" when in reality you have never gone into it. The main reason is that the forum you are on doesn't use database backed thread marking. Which means they are stored in cookies which don't transfer between the app and your desktop browser. Also many forums mark threads read after a certain period.

I think in this instance he's saying that the blue dot does appear, but then immediately disappears. I've seen that occasionally as well. The blue dots will blink off and on and then either stay on or disappear. It doesn't happen all the time though. This is with the AVSForum 1.3.2 app.

I do notice that the AVSForum app makes a number of outbound connections at startup so maybe it's accidentally triggering the forum to mark the threads as read or something.

The other issue I have is that the badge count from push notifications, rarely if ever matches that actual number of new threads/messages. Reading messages in the app, doesn't reset the push servers message count. So if I get a push notification that changes the badge count to "1" the next push notification will change it to "2" when only 1 thread was updated. This corrects itself periodically, but it's normally wrong.

[bruce73]

I'm referring to the AVS Forum branded app. Morac states the problem better than I (thanks ;)).

The blue dot appears for a fraction of second then disappears. As Morac mentions, the app seems to be updating from the AVS Forum when opened, which looks to be triggering this.

Also, the mis-numbered push notification occurs even if I do not go the Forum via a browser since last checked.

[ClemsonJeeper]

I'm referring to the AVS Forum branded app. Morac states the problem better than I (thanks ;)).

The blue dot appears for a fraction of second then disappears. As Morac mentions, the app seems to be updating from the AVS Forum when opened, which looks to be triggering this.

Also, the mis-numbered push notification occurs even if I do not go the Forum via a browser since last checked.

I'm going to need exact reproduction steps to track this down. I'm using the most recent version of avsforum and it seems to be working the way I think it should.

Are you logged into the forum? And push notification? Which tab are you talking about? Current? Forums? Subscribed?

Thanks for the help!

[bruce73]

I'm going to need exact reproduction steps to track this down. I'm using the most recent version of avsforum and it seems to be working the way I think it should.

Are you logged into the forum? And push notification? Which tab are you talking about? Current? Forums? Subscribed?

Thanks for the help!
The problem is this thing doesn't behave the same way all the time. I am logged into the forum and push notification (BTW, didn't there used to be a way to log out of push? Was that eliminated in 1.3.2?).

Basically, if the badge counter is ON, new posts will trigger its display (the actual number, though, is inaccurate). When I open the app (from a multi-tasking state), the (correct, I believe) number is on the Subscribed tab -- it flashes for a moment then it's gone. If I've left it on another tab from the last time, when I go to Subscribed there are no blue dots. If I'm already on Subscribed, the blue dots vanish when the badge counter resets. This, I suspect, is the result of the sync it does with the forum.

The only time I've seen the blue dots stick is if I do a manual refresh (likewise with Current, but not always). Also, although I have not really tested this too much, I believe the blue dots are more likely to stick if the app is opened from a completely closed down status, rather than re-opened from the multi-tasking bar.

It's confusing to describe because there are so many parameters. Which, I know, makes it confusing for you.

[ClemsonJeeper]

No, this is better because at least I know you are talking about the Subscribed tab. I'll take a look at it.

[bruce73]

No, this is better because at least I know you are talking about the Subscribed tab. I'll take a look at it.
Here's another bit: I enabled Alert only. Just got a notice about a new post. Opened up the app, it behaves fine (the number '1' and the dot remain until I go into the thread). So wondering if all this is centered around how the badge counter is implimented. :confused:

[Morac]

I noticed that the push notification badge count for AVSForum branded only resets back to zero if I actually go to the avsforum.com web site. Reading subscribed threads in the app doesn't result in the push server being notified that the unread count is now 0. It's likely a plugin problem or something.

On a related note reading the web site also seems to correct the blinking unread dots, at least temporarily.

[bruce73]

I noticed that the push notification badge count for AVSForum branded only resets back to zero if I actually go to the avsforum.com web site. Reading subscribed threads in the app doesn't result in the push server being notified that the unread count is now 0. It's likely a plugin problem or something.

On a related note reading the web site also seems to correct the blinking unread dots, at least temporarily.
There really seems to be no rhyme or reason about the notifications. It's hard to pinpoint an actual cause & effect scenario, your discovery about actually going to the website notwithstanding. I haven't been using the website to read new posts lately or the badge counter, just alerts, and that, too, is messed up.

The blinking unread dots thing randomly goes from blinking and sticking, then blinking and not sticking. If they do stick, going into a thread to read a post and then returning to subscriptions sometimes erases the remaining dots. But then sometimes not, and when existing the app, the badge counter will indicate the remaining unread posts.

I've learned to rely on the date of the last post for the current status of a thread, but I'm also spending time needlessly going into threads already caught up with. But, that being said, I really like this app; when things get straightened out, I'll consider it 5-stars.

[ClemsonJeeper]

Are these subscribed threads where when you read them it goes to the first unread (or what the forum reports as the first unread), but you still are not on the last page of the thread?

Because a thread will not be marked as fully "read" until you read the last page of it. This might explain the blinking blue dot issue...

If you go into the app and read the last page of a subscribed thread, does the blue dot reappear?

[bruce73]

Are these subscribed threads where when you read them it goes to the first unread (or what the forum reports as the first unread), but you still are not on the last page of the thread?

Because a thread will not be marked as fully "read" until you read the last page of it. This might explain the blinking blue dot issue...

If you go into the app and read the last page of a subscribed thread, does the blue dot reappear?
Honestly, I don't know, I'll have to look into that (I usually keep up on unread posts, so I'm typically on the last page).

Here's what I experienced right now (with only Alerts/Sound enabled):

1) an alert appeared on my lock screen
2) I unlocked, opened the app (I leave it on the subscription tab)
3) two blue icons and subscription badge "2" flashed a couple of times, then disappeared (other times they will stick, why, I dunno)
4) I go into the first thread (just realized the unread threads migrate to the top of the list, which helps), the app goes to the last post of the last page of the thread (there were three posts above that I hadn't read yet).
5) same with the other thread (it always seems to go the last post of the thread).

Now, for the times where the blue icons stick: going into one thread, reading the last post, and going back to the subscriptions tab, will cause the other icons to disappear immediately.

This is what I've been seeing consistently. HTH.

[ClemsonJeeper]

Okay that helped a LOT!

I just sent Morac another debug version (since he has helped with this in the past). I can send you a debug version too, but I will need your UDID from your iPhone.

To get it:

Connect it to your computer and launch iTunes. Click on the iPhone in the left, and then on the info pane, click on "Serial Number" and it will change to a hexadecimal string of characters. Copy this and PM it to me, and I'll build you a copy you can test with.

Thanks again!

[Morac]

Okay that helped a LOT!

I just sent Morac another debug version (since he has helped with this in the past). I can send you a debug version too, but I will need your UDID from your iPhone.

To get it:

Connect it to your computer and launch iTunes. Click on the iPhone in the left, and then on the info pane, click on "Serial Number" and it will change to a hexadecimal string of characters. Copy this and PM it to me, and I'll build you a copy you can test with.

Thanks again!

You should probably send it to him. I haven't seen the flashing unread dots for a while now.

I do see the wrong badge count on push notifications all the time. Does the beta version fix that?

[ClemsonJeeper]

I fixed an issue with regard to coming into the foreground in certain screens, so hopefully it should improve that.

[Morac]

I'm seeing the disappearing unread dots in the official (non-branded) Forum Runner app. It only happens if I exit the app while in a subscribed thread or in the thread with the screen locked. Then if I go into the app and go back to the subscribed threads page all the blue dots vanish.

If I start off on the home screen when entering the app this isn't a problem.

I'm assuming that's the same bug as with the AVSForum app?

[ClemsonJeeper]

Yep. Let me send you a beta Forum Runner (full) version.

[ClemsonJeeper]

Unfortunately, the way AVSForum and other large forums have their Forum Thread Marking setting configured, it will never be perfect. I've written up a FAQ entry explaining how it works:

http://www.forumrunner.net/forum/faq.php?faq=fr_iphone#faq_threadmarking