"Go to last new" still buggy on occasion
Kris
via web
Hey man,
I'm still running into something I ran into in the beta occasionally. Most the time I load the app, it does correctly refresh and jump down on the screen to where I last left off exactly as I want. However, just today, I've already had 3-4 times that it didn't. It just started right up at the very top, and I had to scroll down about 15 tweets to try and remember where I last left off because the line that is supposed to be there wasn't there either. I'm really hoping this is a bug that can get worked out as I never ran into this with other clients like Bad Kitty. I need to rely on it accurately going to the last tweet I left off on every time. Other than this, the app is perfect for me! Just loving it! :)
Thanks,
Kris
Comments are currently closed for this discussion. You can start a new one.
Support Staff 2 Posted by Moe on 17 Apr, 2011 08:21 AM
Hey Kris,
It jumps to the oldest new tweet only if we find new tweets, if not then we remove the previous bar that divided older from newer tweets. Makes sense?
After every refresh if we find no new tweets we hide the old bar. It's not really a bug :)
Can you confirm that you're referring to Manual refresh as in tapping the refresh button? Because the auto-refresh handles the dividing bar & scrolling differently.
Thanks for posting it here. I'll be waiting for your reply.
3 Posted by Kris on 17 Apr, 2011 09:22 PM
I'm glad you were able to reproduce the bug after further talking with me. It just happened to me again about an hour ago. Here's what I think is happening. It seems to be a caching bug, like your cache isn't always working correctly because the times it does it, my whole timeline is completely blank while the little circle is spinning like it's reloading the entire timeline and has no reccollection of where it was before..
Support Staff 4 Posted by Moe on 17 Apr, 2011 09:48 PM
That's right, great observation :) found the problem with scrolling to last-new it's not cache related. But timeline loading that starts with empty timeline is related to cache, and the problem is now found too, it's the webkit DB speed, it's very slow. Looking for alternatives... Thanks again for bringing it to our attention :)
5 Posted by Kris on 10 May, 2011 03:27 AM
Yeah, I think you are right. I am now on my new Pre2 and I notice that I don't run into this quite as often as I did on the Pre Plus. However, I do still run into it so I wish you'd hurry up and submit the update :P I think you've gotten enough initial sales by now right? It won't take that long to approve..
Support Staff 6 Posted by Moe on 10 May, 2011 04:05 AM
That's right, it's about time, we put some more work on other bugs and some major bugs that we were reported, we should be updating in a day or two max...I know we kept you waiting for a long time for this fix, thanks for your patience Kris :)
7 Posted by Kris on 11 May, 2011 06:35 PM
So, today? :P
Support Staff 8 Posted by Moe on 11 May, 2011 09:57 PM
Yes :) tried to submit a few times it didn't go through, looks like there are some issues on the App site, let's see what we'll hear back, other wise we're good to go :) I'll DM you when it goes through ;)
9 Posted by Kris on 11 May, 2011 09:58 PM
Awesome! Thx Moe! You da man! :)
Moe closed this discussion on 16 Aug, 2011 09:15 PM.