Android client: if only I could unread the sdk

[nikkelitous]

Before the update a few weeks ago, I had easy one touch access to the "mark unread" button and while I know it's bad to use it, sometimes there are articles that just aren't good to read on a mobile device so I used it for those. With the update a few weeks ago, it was made harder and moved to the menu. This was annoying but still usable. However, the latest version, 1.77 update removed even that.

I would like to request that the "mark unread" option be brought back.

Ideally, I'd like it "one touch" but even in the menu would be good enough for me.

[fox]

personally i'd love if people read at least a few posts before trying to enlighten us all with their wisdom but then again we have people like you

i guess we both want something we can never have

[aurelieng]

I just noted a problem with basic auth handling.

My android client was working perfectly before I decided to turn on Basic Auth on my HTTP server, As expected, after that, I could not login anymore (401 Unauthorized), and had to put the username/password in the settings, Now that username/password are set correctly, the 401 Unauthorized error is gone, but instead I have: "Error: please enable external API access in tt-rss Settings- Advanced". I did not change this setting, it was enable before and it still is.

Any idea?

[fox]

one idea would be to post logs

[aurelieng]

Sure.

Apache2 doesn't complain about anything. If the basic auth username/password were wrong, I would see "auth_basic:error, user not found." Here, I only see a POST request to //api/, with a 200 reply. So far so good.

Are there specific logs for tt-rss on android, or for the tt-rss installation (the logs in web interface are empty)?

[fox]

google logcat

[aurelieng]

Here it is:

D/HeadlinesFragment(17843): scroll hack
D/HeadlinesFragment(17843): allowForceUpdate=false userInitiated=true
D/HeadlinesFragment(17843): [HP] request more headlines...
D/ (17843): >>> ({"limit":"30","sid":"dlnia3q145o3oe2gq2u13qlb45","op":"getHeadlines","include_nested":"true","
D/ (17843): Using HTTP Basic authentication.
D/ (17843): <<< {"seq":null,"status":1,"content":{"error":"API_DISABLED"}}

[fox]

if your http auth username is different from your actual tt-rss username it might take priority based on the order of auth plugins in config.php

i'm more or less sure it's something like that

[aurelieng]

I changed the basic auth to match the tt-rss username and password, it still replies API_DISABLED.
Changing the order of auth plugins - auth_remote came before auth_internal, so I swapped them -, and still the same symptoms.

What else could it be? What kind of debug would be useful?

[fox]

i just ran a quick test enabling http auth on my instance (with a different user/pass combo) and it worked just fine. not sure how i can help you tbh.

[aurelieng]

Nevermind, it's working now, without any change except the username/password set in http auth to match those of tt-rss. It was probably due to some fancy cache stuff. Thanks a lot!

[pafnucy]

I have the same widget problem as described in viewtopic.php?f=1&t=920&start=60#p16133 with stock kitkat 4.4.4

The bug is intermittent. On a freshly restarted phone, tapping the widget opens ttrss as expected. Over time, however, tapping on the widget stops doing anything. You need to open ttrss from a regular apps shortcut to make it work again. I will try to come up with a reliable way to replicate it but it may not be easy.

[fox]

i'll tell u even more

sometimes if u click on a launcher icon, it restarts the app i.e. it receives oncreate/onresume/etc
sometimes it doesn't and it just brings it on top

pretty much the same w/ shortcuts

why? who knows, android is shit

[fox]

widgets are some arcane stuff, good news is that its going to work a lot better in next market update. at least i hope so, device reboot shouldn't now make widget disfunctional until you re-add it or launch ttrss app manually.

[Latimer]

There is something weird going on with the latest client. It refuses to work with a few of my feeds.

Can't open an article -- nothing happens:
- open a feed, click on an article, nothing happens.
- affected feed: http://navalny.com/blog/post.rss

Can't open an article -- client "closes":
- open a feed, click on an article, the client disappears from the screen. When recalled from a list of the recent apps, the client logs in and behaves as if it was just started.
- affected feed: http://slon.ru/rss/xml/all.xml

Can't back out of an article -- client "closes":
- open a feed, click on an article (it opens), press Back button, the client disappears from the screen. When recalled from a list of the recent apps, the client logs in and behaves as if it was just started.
- affected feeds: http://fivethirtyeight.com/datalab/feed/, http://mediazavod.ru/shorties.rss

I cannot reliably reproduce it. For example, the feed from fivethirtyeight.com behaved correctly the next time I tried it, so I had to mention the URL of another feed.

Environment: Nexus 5, Android 5.0.1, apk 1.88 (309), Tiny Tiny RSS 1.15.3 (I haven't switched to git yet)