desktop / desktop

Focus on what matters instead of fighting with Git.
https://desktop.github.com
MIT License
19.57k stars 9.35k forks source link

Does not remember login information #18635

Closed henrypp closed 1 day ago

henrypp commented 3 months ago

The problem

Everyday i need to relogin, what is this? It is feature?

Release version

windows (any)

Operating system

ANY

Steps to reproduce the behavior

No response

Log files

No response

Screenshots

No response

Additional context

No response

sergiou87 commented 3 months ago

Thank you for your report and sorry for the inconvenience. We're working on this issue as we speak, you can follow our progress in https://github.com/desktop/desktop/issues/18586

henrypp commented 3 months ago

@sergiou87 but i did not have auth failures, i success auth everyday, but same i need to relogin in next day

sergiou87 commented 3 months ago

@henrypp Could you upload your log files from GitHub Desktop so that I could get some more information about this error? To access the log files go to the file menu in GitHub Desktop and select Help > Show Logs. The log files are created daily -- please upload a log files as attachments from a days where you experienced the issue.

Do you have multiple repos on the same host but using different credentials?

henrypp commented 3 months ago

@sergiou87

there is no " Show Logs" menu, only "Show all commands" (ctrl+shift+p) sshot-003

what exactly?

sergiou87 commented 3 months ago

@henrypp What is the app from that screenshot? Is it VS Code?

henrypp commented 3 months ago

@sergiou87 oh shi, my misstake, i made vs code screenshot, here is github app logs:

2024-05-20.desktop.production.log

sergiou87 commented 3 months ago

Hello 👋

Please, try the latest beta (3.3.19-beta2) from https://desktop.github.com/beta which includes support for multiple git credentials on the same host based on different repository paths and let us know if it works.

After updating, you might need to re-enter your credentials for your Azure DevOps repositories.

For hosts other than dev.azure.com, you might need to set useHttpPath to true for whatever domain your repos are hosted on. For example, for gitlab:

git config --global credential.https://gitlab.com.useHttpPath true

Thank you for your patience 🙏

henrypp commented 3 months ago

@sergiou87 it remembered login for 3.5 hours, not soo much, ur devs is complete out of mind, over9000 another same issues with the same

sergiou87 commented 3 months ago

That's weird 😞 Could you share your logs again with this new version so we can get more context about the problem? 🤞

henrypp commented 3 months ago

2024-05-25.desktop.beta.log

sergiou87 commented 3 months ago

For some reason that log is super short. Did you experience the issue on that day (25-May) before you sent me the log?

You might need to send a new one…since the log files are created daily, please upload a log file as an attachment from a day where you experienced the issue.

Thanks for your patience 🙏

henrypp commented 2 months ago

same for 3.4.0

niik commented 2 months ago

:wave: we just shipped GitHub Desktop 3.4.2-beta2 to our beta channel. This includes support for using Git Credential Manager. It's currently off by default but you can enable it in Settings under the advanced tab. We believe this will address the authentication problems outlined in this issue.

Screenshot of Desktop's advanced preferences section with a highlight around the new option to enable Git Credential Manager

When Git Credential Manager (GCM) is enabled all credentials for third-party (i.e. Azure Devops, BitBucket, GitLab etc) will be handled, and stored, outside of GitHub Desktop. GCM supports browser-sign in to many popular services and will avoid the need to create personal access tokens (PATs).

Please download our beta version from https://desktop.github.com/beta/ to give this a go and please report back with your experience. We'll be collecting feedback in our beta channel which will inform when we make this available to all users. Installing the beta version will not clear your preferences or tracked repositories and you can switch to the production version by simply downloading the latest version from https://desktop.github.com.

henrypp commented 2 months ago

@niik same shit. do you really think it happens because of GCM?

henrypp commented 2 months ago

@niik or maybe where auth cookie will saved and cant be readed?

steveward commented 2 months ago

@henrypp can you confirm what type of hosting service you are using? Is it GitHub, or a different service like GitLab? Any details about your setup and the specific issues you are experiencing would be helpful.

henrypp commented 2 months ago

@steveward github app and github setvice

henrypp commented 1 month ago

even "use Git Credential Manager" (and others) option does not remembered, what it is so stupid blyad'?

steveward commented 1 month ago

If you're getting logged out of your GitHub account, then that sounds like a local storage issue with the app. You can try resetting things to see if that gets it working again. Here's how to do that:

  1. Close GitHub Desktop
  2. Remove all of the files in %APPDATA%\GitHub Desktop\
  3. Restart GitHub Desktop

You will need to log in and add your repositories again, which can be done quickly in bulk by drag-and-drop.

henrypp commented 1 month ago

@steveward i removed %APPDATA%\GitHub Desktop\ login again and today is the same i need to auth again and settings are reseted, idiotic

steveward commented 1 month ago

I think there must be some information we're missing here, as we haven't seen any other cases of the app logging out users. Can you confirm when this happens that if you go to File > Options > Accounts it shows you as logged out? Any information or screenshots you can share would be helpful.

henrypp commented 1 month ago

@steveward it popup login screen on startup, dont see setings which does not remembered

steveward commented 1 week ago

Can you confirm if it shows you as logged out when you go to File > Options > Accounts? Please share a screenshot or a video of the behavior. Without more information it is difficult for us to assist further.

github-actions[bot] commented 1 day ago

Thank you for your issue! We haven’t gotten a response to our questions above. With only the information that is currently in the issue, we don’t have enough information to take action. We’re going to close this but don’t hesitate to reach out if you have or find the answers we need. If you answer our questions above, this issue will automatically reopen.