403s when manually refreshing screens about gh4a HOT 6 OPEN

No, pull-to-refresh just restarts the loaders, that is, triggers the same kind of data fetch as done when initially opening the respective activity.
Is this only in the home activity or also in other ones (say, issue list, issue details etc.)?

from gh4a.

Seems to happen with all of the top-level screens, including Search (whether a query has been entered or not; searches then don't go through whilst the 403 error is showing), Public Timeline and Trending Repos.

from gh4a.

I also seem to be getting frequent "API rate limit exceeded" errors whilst testing this -- may be related to #1013, if notifications can't be read with this token and they're being retried on all screen refreshes?

from gh4a.

More importantly, opening a link to a repo directly in the app also shows this 403 when the app first opens, and you can't pull-refresh or navigate around to make it load.

from gh4a.

Can you provide a stack trace from logcat including the 'Caused by...' parts?

from gh4a.

03_01-08-17-23_224.log
03_01-08-25-01_043.log

The first one is from opening the app via launcher, the second from opening a link to this repo. Both of them do seem to suggest they're trying to refresh notifications (despite Notifications being disabled in Settings, though presumably that only affects the resulting Android notifications).

from gh4a.