Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fever authorization stopped working after 9.9 update #507

Closed
SoiledBrush opened this issue Jan 10, 2024 · 11 comments · Fixed by #509
Closed

fever authorization stopped working after 9.9 update #507

SoiledBrush opened this issue Jan 10, 2024 · 11 comments · Fixed by #509
Labels
bug Something isn't working

Comments

@SoiledBrush
Copy link

  • OS: [Android 13]
  • APP: [0.9.9]

My miniflux account connected through fever stopped syncing with error "Unauthorized".

And adding the same account as new one gets me error "Not valid credentials".Screenshot_20240110-085753.png

@SoiledBrush SoiledBrush added the bug Something isn't working label Jan 10, 2024
@Ashinch
Copy link
Owner

Ashinch commented Jan 10, 2024

Does it work in version 0.9.8?

@SoiledBrush
Copy link
Author

Yes, it does

@mbestavros
Copy link
Collaborator

Confirmed, I'm seeing the same issue with my saved Fever credentials. I'm testing out reverting some commits that may have introduced the bug over at #508; will report back with any results.

@mbestavros
Copy link
Collaborator

@Ashinch I have some good news, and some bad news. Good news: I found the culprit! Bad news: it's the giant refactoring you did in September 😭

More specifically, it appears to be this commit: 8f1966d

Reverting all code commits that rely on that commit (including favicon support, unfortunately) does fix it, but this seems drastic. If you're able to dig into it and figure out what's going wrong, that would be ideal, but in the meantime we should decide what to do with the release.

(My apologies for backing us into a corner by releasing 0.9.9. I'll definitely test more thoroughly next time before cutting a release...)

@zhusuner
Copy link

@Ashinch I have some good news, and some bad news. Good news: I found the culprit! Bad news: it's the giant refactoring you did in September 😭

More specifically, it appears to be this commit: 8f1966d

Reverting all code commits that rely on that commit (including favicon support, unfortunately) does fix it, but this seems drastic. If you're able to dig into it and figure out what's going wrong, that would be ideal, but in the meantime we should decide what to do with the release.

(My apologies for backing us into a corner by releasing 0.9.9. I'll definitely test more thoroughly next time before cutting a release...)

Don't beat yourself up. Let's take the test together. It will both reduce your stress and make the test more fulfilling. Let's make ReadYou better.

@mbestavros
Copy link
Collaborator

@Ashinch This keeps getting weirder...

When I test a debug build using Android Studio, everything works fine. But when I run a release build of the same commit, I get the bug...

It's late where I am, and I have to get to bed. But I'm baffled.

@kid1412621
Copy link
Contributor

@Ashinch This keeps getting weirder...

When I test a debug build using Android Studio, everything works fine. But when I run a release build of the same commit, I get the bug...

It's late where I am, and I have to get to bed. But I'm baffled.

I got into the same situation, So I doubt it's introduced by the refactor since it was basically renaming. Anyway, sleep tight.

@mbestavros
Copy link
Collaborator

Okay, final action of the night: just marked 0.9.9 as a pre-release. I don't want this bug being pushed out to stable users if we can help it.

@Ashinch Should we go further and take the release down entirely?

@Ashinch
Copy link
Owner

Ashinch commented Jan 10, 2024

More specifically, it appears to be this commit: 8f1966d

@mbestavros

I'll investigate, no need to revert more commit.

@Ashinch
Copy link
Owner

Ashinch commented Jan 10, 2024

@Ashinch Should we go further and take the release down entirely?

No, I'll fix it as soon as I can.

@mbestavros
Copy link
Collaborator

mbestavros commented Jan 10, 2024

@Ashinch To clarify, I haven't pushed any reversions to the main branch yet; only on my fork.

No, I'll fix it as soon as I can.

Awesome! If you manage to fix it up, I can help push out a 0.9.10 release with the fix, if needed.

@Ashinch Ashinch linked a pull request Jan 10, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants