Android version 3.5

  • 15
  • Problem
  • Updated 6 years ago
Thanks for the update! However, I'm having problems with it on both my devices (one Jellybean, one Kitkat):

1. After reading all articles in a feed/folder, returning to its screen (via the back button or "breadcrumb") results in a blank screen save for an unending "Loading..." message

2. Text view seems to be working much more inconsistently. Sometimes attempting to use it results in nothing happening at all, other times I end up with a completely blank screen (and a need to manually kill the app).

I've had to return to using 3.0.1 for now.
Photo of Bill Waldron

Bill Waldron

  • 51 Posts
  • 14 Reply Likes

Posted 6 years ago

  • 15
Photo of Stefan Constantinescu

Stefan Constantinescu

  • 66 Posts
  • 3 Reply Likes
In full agreement, I'm not a fan of the latest version of the Android app at all. Old version worked perfectly, at least for me.
Photo of Rick Hensley

Rick Hensley

  • 9 Posts
  • 0 Reply Likes
Similar to as reported, when I get to the next to last unread article the screen app goes blank and I can not advance to the next item in the feed; if I try to return via swipe to the previous it loads the listing of unread articles, namely the last in the original list. As a result of this, I am unable to read the next to last item in my unread feed until I show all items and locate the one I hadn't yet read.
Photo of Stefan Constantinescu

Stefan Constantinescu

  • 66 Posts
  • 3 Reply Likes
What sucks is that CES kicks off in just a few days. This new version is a *serious* downgrade. Pinging Samuel.
Photo of Destry Fronck

Destry Fronck

  • 6 Posts
  • 0 Reply Likes
I've noticed the same issue as Rick.

"when I get to the next to last unread article the screen app goes blank and I can not advance to the next item in the feed; if I try to return via swipe to the previous it loads the listing of unread articles, namely the last in the original list. As a result of this, I am unable to read the next to last item in my unread feed until I show all items and locate the one I hadn't yet read."
Photo of jenbooks

jenbooks

  • 13 Posts
  • 16 Reply Likes
Add me to this.
Photo of wurdmen

wurdmen

  • 1 Post
  • 0 Reply Likes
Same here. It happens almost every time I open the last item in a feed with the read filter set to "Unread Only."
Photo of RedSonja

RedSonja

  • 8 Posts
  • 0 Reply Likes
Also here.
Photo of A Abelev

A Abelev

  • 2 Posts
  • 0 Reply Likes
so, is it possible to downgrade?
Photo of deezil

deezil

  • 16 Posts
  • 1 Reply Like
+1 to all issues in OP. Bonus: if you hit the three-dot-menu button when the screen blanks, then the app will crash out.
Photo of Samuel Clay

Samuel Clay, Official Rep

  • 6514 Posts
  • 1474 Reply Likes
We're working on getting this issue addressed. We need reproducible steps and so far we can't make the above happen with any regularity. But we'll get a fix out on Monday after working on it today and tomorrow.
Photo of Rick Hensley

Rick Hensley

  • 9 Posts
  • 0 Reply Likes
I can send a screen recording of this happening if it would help you isolate or identify the problem.
Photo of Stefan Constantinescu

Stefan Constantinescu

  • 66 Posts
  • 3 Reply Likes
Just this morning, same thing again, but this time, when I was near the end of a folder, the dreaded "Loading" screen appeared and then everything was somehow marked as read.

Officially giving up using NewsBlur on my Android phone until this gets fixed. At least the website is bulletproof.

Can you "downgrade" the version of NewsBlur in the Play Store to version 3? That worked beautifully.
Photo of Marc Ordinas i Llopis

Marc Ordinas i Llopis

  • 2 Posts
  • 0 Reply Likes
I think the problem is due to the reading list being refreshed while the user is reading an article. The article is marked as read, removed from the reading list and immediately goes to a blank page (as the horizontal scroller doesn't have a correct position any more). If I'm right in this, an easy fix would be not to modify the current reading list while the user is viewing an article.
Photo of Stefan Constantinescu

Stefan Constantinescu

  • 66 Posts
  • 3 Reply Likes
Whatever it is, I'm pulling my hair out. Sometimes I can read 50+ article in one go before the app goes bonkers on me, sometimes it takes just three articles. Replicating the bug is hard, and I'm sorry I can't help you out, Samuel, but man, version 3.5 really is a horrific regression from version 3.0.
Photo of Ross

Ross

  • 37 Posts
  • 3 Reply Likes
Exactly the same for me. If I noticed a pattern I'd post the steps I took, but as of now I'm afraid to use the app because it will auto-mark everything as read.
Photo of Samuel Clay

Samuel Clay, Official Rep

  • 6514 Posts
  • 1474 Reply Likes
There are several issues we've found and are working on correcting. Part of this is due to a massive rewrite of the network stack. But part of this is because we move so fast and have so few resources that we just expect to release and patch bugs immediately afterwards. I should have released this as a controlled beta, but after not catching any bugs in testing, I figured the bugs were marginalized.

As far as I can tell, it's only the All Site Stories view that's clearly messed up. The other folders and feeds are more subtly broken. All of it will be fixed tomorrow when I release 3.5.1. And anything lingering will be fixed a couple days after that with 3.5.2.

If I had to choose between fast releases and slow releases, I'll take the fast strategy, especially as it means that new features and improvements are constantly coming out. It's a trade off and sometimes it bites us in the butt like it did today, but most of the time you get improvements and bug fixes out in a matter of hours or days.
Photo of Ross

Ross

  • 37 Posts
  • 3 Reply Likes
Appreciate the update, Samuel. Thanks for the explanation and look forward to the release.
Photo of altonius

altonius

  • 4 Posts
  • 0 Reply Likes
happy for the fast releases if they're followed up with fast fixes as you're doing here.

Keep up the good work.
Photo of Stefan Constantinescu

Stefan Constantinescu

  • 66 Posts
  • 3 Reply Likes
Looking forward to the release as well, it's just *super* bad timing for this buggy release to go out with CES and all. At least it'll be fixed before MWC.
Photo of Bill Waldron

Bill Waldron

  • 51 Posts
  • 14 Reply Likes
Thanks, Sam.

A beta process for the Android app would be welcomed.
Photo of Samuel Clay

Samuel Clay, Official Rep

  • 6514 Posts
  • 1474 Reply Likes
OK, I just uploaded v3.5.1, which addresses a couple of the issues. Unfortunately, the swiping issue is not yet fixed and won't be until about Wednesday. I'll try to get fixes out earlier, but Wednesday is the earliest I can get out a rewrite for that part of the stack.

If 3.5.1 doesn't address enough of the issues, I'll downgrade the released version to 3.0.1 while we work out the kinks.
Photo of Nrbelex

Nrbelex

  • 52 Posts
  • 2 Reply Likes
Still having the screen blank out on 3.5.1 at the end of my feeds and experiencing some other buginess.
(Edited)
Photo of mokelly

mokelly

  • 35 Posts
  • 3 Reply Likes
In 3.5.1, pressing the menu button while viewing a story now usually crashes the app.
Photo of Stefan Constantinescu

Stefan Constantinescu

  • 66 Posts
  • 3 Reply Likes
"If 3.5.1 doesn't address enough of the issues, I'll downgrade the released version to 3.0.1 while we work out the kinks."

This. Please.
Photo of Bill Waldron

Bill Waldron

  • 51 Posts
  • 14 Reply Likes
I think a downgrade might be best. After playing around with it for just a brief time, 3.5.1 still looks pretty wonky on my phone.
Photo of jason

jason

  • 76 Posts
  • 7 Reply Likes
This might be related to the general problem with people getting to the end of feeds...and also, it doesnt happen with 100% consistency so i cant call it perfectly reproducible, but the way i read feeds is to scroll down to the oldest entry and then work my way back to current...when i click the oldest entry it opens up, and then it just disappears and goes back to the feed...sometimes it happens on its own, and sometimes it happens if i put my finger to the screen about to swipe. also, a couple times its done this, i kick back to the main screen and the feed says it has some weird unread count, but a refresh brings it back to the real unread count. this is happening on the updated 3.5.1 as well as 3.5
Photo of jason

jason

  • 76 Posts
  • 7 Reply Likes
that was improperly phrased...it doesnt go back to the feed, it goes to a blank screen...also though, i can then swipe from left to right and continue reading the feed as normal, i just lose the one oldest entry that i wanted to start with. also, when swiping from this blank screen, it doesnt just gracefully slide in the next entry like it usually does...the second i start to swipe the next oldest entry just drops in
Photo of A Abelev

A Abelev

  • 2 Posts
  • 0 Reply Likes
So, how does one downgrade to the previous version?
Photo of ooobo

ooobo

  • 29 Posts
  • 15 Reply Likes
https://f-droid.org/repository/browse...

Not sure how/if you can on Google Play, but on F-Droid you can find the old apk's, last is 3.0 though.
Photo of Samuel Clay

Samuel Clay, Official Rep

  • 6514 Posts
  • 1474 Reply Likes
Good news, I just uploaded 3.5.2, which should fix the majority of issues. If you have new issues after using 3.5.2, let me know in this thread.
Photo of Samuel Clay

Samuel Clay, Official Rep

  • 6514 Posts
  • 1474 Reply Likes
By the way, the flashing of "No stories to read" after the feed loads is going to be fixed in another release on Wednesday. As will a couple other small bugs. But I want to know what else you find that's wonky. This patch release should fix the big issues, and still be a huge improvement in terms of speed.
Photo of jason

jason

  • 76 Posts
  • 7 Reply Likes
Not sure if this is the same as/related to what you're referencing with no stories to read but opening the oldest new entry of a feed still results with a white screen (after the entry is momentarily displayed) in 3.5.2