"Go to First New" after refresh preference not working

SmartFah's Avatar

SmartFah

03 Feb, 2011 08:03 AM via web

This preference does not seem to work. The first day I downloaded the beta, it only worked when I opened the app through notification. If I opened the app through the launcher, it would take me to the top of my time line, whether I had new tweets or not.

After I updated the app, this feature doesn't seem to work at all. Regardless of if I open the app through notifications, or the launcher, it wont take me to my first new tweet, only the last new one.

  1. Support Staff 2 Posted by Moe on 03 Feb, 2011 08:23 AM

    Moe's Avatar

    It works fine, just tested over and over, are you sure you have the "After Refresh" preference set to "First New"? Note that we've made "Last New" as the default choice as of v.1.0.11...

  2. 3 Posted by treorock on 03 Feb, 2011 08:28 AM

    treorock's Avatar

    I'm having the same exact problem.

  3. 4 Posted by osullivanj2000 on 03 Feb, 2011 09:10 AM

    osullivanj2000's Avatar

    I have set the preference to Last New, but it only seems to work sporadically, whereas it worked fine in the private beta. (I just checked)

  4. Support Staff 5 Posted by Moe on 03 Feb, 2011 09:25 AM

    Moe's Avatar

    For Last New, it depends on how the refresh is done, we've made it in a very logical way and what you see is not a bug.

    We have 3 states of refresh and for each way of refreshing we deal with the marker differently.

    On Manual refresh, since you are looking at your timeline while refreshing, it does make sense to udpate the Marker and move it to the Last New and scroll your timeline there.

    On Auto Refresh though, it is assumed that you're not looking at your screen and you don't remember where the last tweet that you read is, so what we do is, we keep on updating the timeline with auto refresh but at the same time we don't move or scroll the list nor we move the Marker any higher, that way once you go back to your timeline, you start from where you left of when you minimized the card or opened another app.

    On Background refreshes we deal with markers exactly as the manual refresh, the only issue(BUG) that there is is for the time of launching the app. That's when we lose the Marker position. I've flagged that and we'll get it fixed ASAP.

  5. Moe closed this discussion on 03 Feb, 2011 09:25 AM.

  6. Moe re-opened this discussion on 03 Feb, 2011 09:25 AM

  7. 6 Posted by volcom45 on 03 Feb, 2011 04:25 PM

    volcom45's Avatar

    I think they are probably all referring to after closing the app and re-opening it which we all desperately want/need it to do. It makes no sense to go to the top upon re-opening the app with that jump to last new setting enabled. It sounds like you'll be adding an option for this in future builds but it definitely should be a stock option in the first app catalog release as many need it or its a deal breaker.

  8. Support Staff 7 Posted by Moe on 03 Feb, 2011 04:42 PM

    Moe's Avatar

    It'll be definitely set by default...we took another look at it, n' it's annoying to have it go to the top...we'll fix it...

  9. 8 Posted by volcom45 on 03 Feb, 2011 04:58 PM

    volcom45's Avatar

    Thanks alot man! That is my only issue with the current build. When you follow someone like JohnnyPre who can drop 50 new RT's all at once, it can be so hard to scroll all the way down and recall where you last were. :) Loving the rest of the app!

  10. Support Staff 9 Posted by Moe on 03 Feb, 2011 05:14 PM

    Moe's Avatar

    You got it!

  11. 10 Posted by nachob70 on 05 Feb, 2011 01:21 PM

    nachob70's Avatar

    Experiencing the same behavior when launching the app, after refreshing it goes to last new and I have to scroll down and find where I left off in the timeline. I have it set to First New.

  12. Support Staff 11 Posted by Moe on 13 Feb, 2011 04:46 PM

    Moe's Avatar

    Which version of Carbon are you using? All these have been solved since 1.1.0...check back and confirm it here. Thanks.

  13. 12 Posted by nachob70 on 13 Feb, 2011 05:01 PM

    nachob70's Avatar

    I'm on 1.1.0 and it's working now. Still waiting for 1.1.1 to become available :-)

  14. 13 Posted by volcom45 on 13 Feb, 2011 05:48 PM

    volcom45's Avatar

    1.1.0 seemed to correct this issue for the most part. It seems like about 20% of the time, it'll refresh down to older tweets rather than where it's supposed to have left off and I'll have to scroll back up, but the other 80% of the time, it goes exactly where it is supposed to go..

  15. Support Staff 14 Posted by Moe on 14 Feb, 2011 06:33 AM

    Moe's Avatar

    Are you referring to auto-refresh? Because on auto-refresh we keep the timeline untouched so that you come back and find your timeline the way you left it. Kindly confirm your refresh method.

  16. 15 Posted by volcom45 on 14 Feb, 2011 05:17 PM

    volcom45's Avatar

    Nope, at least a couple times, I've opened the app up after it had been closed for hours, and it jumped me back down to older tweets than where I'd left off at the top when closing the app. This same behavior has also happened when the app was left open and it auto refreshed after 15 minutes. It seems to be a bug of some sort because most the time it doesn't happen, but it definitely happens on occasion.

  17. 16 Posted by volcom45 on 16 Feb, 2011 04:35 AM

    volcom45's Avatar

    Ok, I updated to 1.1.1 earlier this evening and several times already this evening, I'm seeing duplicates.. Anyone else seeing this? Maybe this is what I've been running into before when I think it's taking back to older tweets, but look at these 2 images:
    http://www.flickr.com/photos/***@N08/5449527755
    http://www.flickr.com/photos/***@N08/5449528957
    You clearly see it is showing the HP tweet twice as well as the RT above it.
    Bug?

  18. 17 Posted by volcom45 on 16 Feb, 2011 05:34 AM

    volcom45's Avatar
  19. Support Staff 18 Posted by Moe on 16 Feb, 2011 05:11 PM

    Moe's Avatar

    Try sharing Flickr URLs in shortened form flic.kr/lkjljlkjlkj something like that...

    I get the error, looks like what we've fixed didn't work for all the cases of duplicates, we'll fix it ASAP...

  20. 19 Posted by volcom45 on 16 Feb, 2011 05:15 PM

    volcom45's Avatar
  21. Moe closed this discussion on 16 Aug, 2011 09:21 PM.

Comments are currently closed for this discussion. You can start a new one.

Recent Discussions

09 Sep, 2011 09:37 PM
09 Sep, 2011 09:01 PM
08 Sep, 2011 06:03 AM
08 Sep, 2011 06:13 AM
31 Aug, 2011 06:48 PM