Star and unstar button sometimes not working #35

Closed
opened 2025-10-31 17:04:15 -05:00 by GiteaMirror · 4 comments
Owner

Originally created by @max-hk on GitHub (Apr 4, 2020).

Pressing star and unstar button in repo page sometimes does nothing

Demo video:
https://imgur.com/a/ZHyHcs2

In the video, I press star button multiple times.
The button was expected to be replaced by unstar button, but nothing happens.

Originally created by @max-hk on GitHub (Apr 4, 2020). Pressing star and unstar button in repo page sometimes does nothing Demo video: https://imgur.com/a/ZHyHcs2 In the video, I press star button multiple times. The button was expected to be replaced by unstar button, but nothing happens.
GiteaMirror added the bug label 2025-10-31 17:04:15 -05:00
Author
Owner

@pd4d10 commented on GitHub (Apr 5, 2020):

Hi, @maxloh , thanks for the feedback!

It seems caused by GitHub's token scope policy update. The solution would depend on the login approach:

  1. Login with OAuth: Go to Me -> Switch accounts to login again. It would ask you the extra notification permission and please say yes.
  2. Login with token: Go to https://github.com/settings/tokens and find the token used in GitTouch, add notification scope and save.
@pd4d10 commented on GitHub (Apr 5, 2020): Hi, @maxloh , thanks for the feedback! It seems caused by GitHub's token scope policy update. The solution would depend on the login approach: 1. Login with OAuth: Go to **Me** -> **Switch accounts** to login again. It would ask you the extra `notification` permission and please say yes. 2. Login with token: Go to https://github.com/settings/tokens and find the token used in GitTouch, add `notification` scope and save.
Author
Owner

@max-hk commented on GitHub (Apr 5, 2020):

Hi, @maxloh , thanks for the feedback!

It seems caused by GitHub's token scope policy update. The solution would depend on the login approach:

  1. Login with OAuth: Go to Me -> Switch accounts to login again. It would ask you the extra notification permission and please say yes.
  2. Login with token: Go to https://github.com/settings/tokens and find the token used in GitTouch, add notification scope and save.

I tried the mentioned steps but the problem persists.

Clearing app data and login again cannot solve the problem too.

@max-hk commented on GitHub (Apr 5, 2020): > Hi, @maxloh , thanks for the feedback! > > It seems caused by GitHub's token scope policy update. The solution would depend on the login approach: > > 1. Login with OAuth: Go to **Me** -> **Switch accounts** to login again. It would ask you the extra `notification` permission and please say yes. > 2. Login with token: Go to https://github.com/settings/tokens and find the token used in GitTouch, add `notification` scope and save. I tried the mentioned steps but the problem persists. Clearing app data and login again cannot solve the problem too.
Author
Owner

@pd4d10 commented on GitHub (Apr 6, 2020):

Oh, there seems another problem with organization repo.

I'll try to fix this in the next release.

@pd4d10 commented on GitHub (Apr 6, 2020): Oh, there seems another problem with organization repo. I'll try to fix this in the next release.
Author
Owner

@pd4d10 commented on GitHub (Oct 5, 2020):

Should have fixed in the latest v1.5.1. Sorry for the long wait!

@pd4d10 commented on GitHub (Oct 5, 2020): Should have fixed in the latest v1.5.1. Sorry for the long wait!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/git-touch#35