-
-
Notifications
You must be signed in to change notification settings - Fork 301
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
[Bug]: Keeps asking for my osx credentials event though I clicked always allow #742
Comments
Does the same happen when you try to pull/push from the terminal multipletimes? The plugin itself doesn't handle authentication, but delegates this to the git cli and its configuration. |
same thing happening for me. If I pull from my terminal the repo updates just fine, but this plugin keeps triggering the permissions popup. I'm also on MacOS with the latest version of the plugin. |
Nope, no problems from the terminal. Does the plugin disable git fetch by default/allow me to disable it? How should I configure my git cli to prevent this issue?Sent from my iPhoneOn 29 Jun 2024, at 7:26 PM, Vinzent ***@***.***> wrote:
Does the same happen when you try to pull/push from the terminal multipletimes? The plugin itself doesn't handle authentication, but delegates this to the git cli and its configuration.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
I don't own a mac device and haven't heard of this issue before. Nothing changed in the plugin's source code, as well. So I currently don't know how to fix that, sorry. |
Just as another data point, this started happening for me as well in the last week or so. I wonder if there was a change to macOS (or maybe the |
Im getting this issue too. I'm a recent user of Obsidian so I don't know if this was a recent problem. |
From Obsidian side I could only think of the electron update, which is low level enough to may mess things up. |
I turned off the 'Vault backup interval' aka set it to 0 and I also have 'Auto Backup after stopping file edit' turned off. Now I manually push up changes with my keyboard shortcut and haven't seen this prompt come up again. Not sure if that is helpful, but figured I would mention it. I really liked the backup interval setting, but something about it must be causing the prompt to be shown over and over. |
Yea same. I’ve turned off the interval and just manually push and it
doesn’t ask anymore. Wonder why that if it’s still trying to use the
keychain (or is it?)
…------------------------------
Jeff Scott Ward
Founder / A.I. & U.I. Engineer
*F0.ai*
------------------------------
On Mon, Jul 22, 2024 at 9:45 AM Adam Whitlock ***@***.***> wrote:
I turned off the 'Vault backup interval' aka set it to 0 and I also have
'Auto Backup after stopping file edit' turned off. Now I manually push up
changes with my keyboard shortcut and haven't seen this prompt come up
again. Not sure if that is helpful, but figured I would mention it.
I really liked the backup interval setting, but something about it must be
causing the prompt to be shown over and over.
—
Reply to this email directly, view it on GitHub
<#742 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJUO7SVE5GDPSXMGNWFBSDZNUEG7AVCNFSM6AAAAABKCZI3RKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBTGAYDEMJZHA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
That's very strange as git and the credentials access shouldn't be able to differentiate between manual and automatic. I can only think of Apple blocking the access, because you didn't type anything at that moment. |
Describe the bug
Whenever it is time to auto backup during git pull and push it asks for credentials
Relevant errors (if available) from notifications or console (
CTRL+SHIFT+I
)No response
Steps to reproduce
I set auto backup every 103 minutes
Expected Behavior
No response
Addition context
No response
Operating system
macOS
Installation Method
None
Plugin version
latest
The text was updated successfully, but these errors were encountered: