Uploaded image for project: 'Sourcetree For Mac'
  1. Sourcetree For Mac
  2. SRCTREE-2422

Prompts for permission to access keychain on new https clones

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • 1.9.3.1
    • 1.9.3
    • Git
    • None

      A number of people are reporting that with 1.9.3 they're getting repeated requests to authorise git-credential-helper for keychain access, and that despite clicking 'Always allow' it carries on prompting.

      I couldn't reproduce this with an existing HTTPS clone of a private repository but when cloning a new one I can reproduce it.

        1. prompt.png
          prompt.png
          46 kB

          Form Name

            [SRCTREE-2422] Prompts for permission to access keychain on new https clones

            Steve Streeting (Inactive) added a comment -

            Fixed in 1.9.3.1.

            Steve Streeting (Inactive) added a comment - Fixed in 1.9.3.1.

            designatednerd added a comment -

            Awesome! Thanks for the quick work.

            designatednerd added a comment - Awesome! Thanks for the quick work.

            Steve Streeting (Inactive) added a comment -

            No, I've tracked it down to a fight between the standard git-credential-osxkeychain and SourceTree's own git-credential-sourcetree; the former re-creates the item then the latter has to ask permission to it again. I'm rolling back the changes in 1.9.3 (which fixed another edge case condition) and issuing a hotfix in a few minutes.

            Steve Streeting (Inactive) added a comment - No, I've tracked it down to a fight between the standard git-credential-osxkeychain and SourceTree's own git-credential-sourcetree; the former re-creates the item then the latter has to ask permission to it again. I'm rolling back the changes in 1.9.3 (which fixed another edge case condition) and issuing a hotfix in a few minutes.

            designatednerd added a comment -

            I'm seeing this as well on an existing HTTPS repo. I have GitHub 2FA enabled, maybe that's part of it?

            designatednerd added a comment - I'm seeing this as well on an existing HTTPS repo. I have GitHub 2FA enabled, maybe that's part of it?

            Steve Streeting (Inactive) added a comment -

            Steve Streeting (Inactive) added a comment -

              Unassigned Unassigned
              sstreeting Steve Streeting (Inactive)
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: