• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • 3.4.14
    • 3.0.15
    • None
    • Windows 10 64-bit

    • Severity 2 - Major

      After updating to 3.0.15 it is no longer possible to check for updates from within Sourcetree. A message box with the following text appears:

      Invalid release entry: 7C20078B2B045E2C881187E39009FD85284F4E83 SourceTree-3.0.15-full.nupkg 23991659

      This issue has been reported to the community forum several times but has not been fixed yet. The Atlassian service engineer that responded in https://community.atlassian.com/t5/Sourcetree-questions/Error-sourcetree/qaq-p/971254 does not seem to understand the problem I'm afraid - the latest version that can be downloaded from sourcetreeapp.com is still only 3.0.12, even though 3.0.15 has been released.
       

        1. image-2019-03-15-09-25-35-302.png
          image-2019-03-15-09-25-35-302.png
          10 kB
        2. image-2019-03-15-09-13-50-944.png
          image-2019-03-15-09-13-50-944.png
          66 kB
        3. image-2019-03-14-08-48-48-772.png
          image-2019-03-14-08-48-48-772.png
          29 kB
        4. SourceTreeError.png
          SourceTreeError.png
          4 kB
        5. SourceTree.2019-01-17.log
          2 kB
        6. image-2019-01-14-16-00-42-645.png
          image-2019-01-14-16-00-42-645.png
          28 kB

            [SRCTREEWIN-11147] Error message when checking for updates

            Mukesh Kumar made changes -
            Fix Version/s New: 3.4.14 [ 105531 ]
            Mukesh Kumar made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Gathering Impact [ 12072 ] New: Closed [ 6 ]

            This issue has been already fixed. Please update to the latest version of Sourcetree.

            Mukesh Kumar added a comment - This issue has been already fixed. Please update to the latest version of Sourcetree.
            Mukesh Kumar made changes -
            Assignee New: Mukesh Kumar [ 698877135425 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: JAC Bug Workflow v3 [ 3455521 ] New: SRCTREE JAC Bug Workflow [ 3741535 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: SourceTree Bug Workflow [ 3080165 ] New: JAC Bug Workflow v3 [ 3455521 ]
            Status Original: Verified [ 10005 ] New: Gathering Impact [ 12072 ]

            John Jurisoo added a comment - - edited

            FYI: Michael Mimms, while the Squirrel.Windows update process doesn't mention updating the version number here https://github.com/Squirrel/Squirrel.Windows/blob/master/docs/using/update-process.md

            There are people that say it can work with the required parameters set.
            https://github.com/Squirrel/Squirrel.Windows/issues/986

            I was just too curious.

            Interesting.

            John Jurisoo added a comment - - edited FYI: Michael Mimms, while the Squirrel.Windows update process doesn't mention updating the version number here https://github.com/Squirrel/Squirrel.Windows/blob/master/docs/using/update-process.md There are people that say it can work with the required parameters set. https://github.com/Squirrel/Squirrel.Windows/issues/986 I was just too curious. Interesting.

            minnsey added a comment -

            Thanks for the feedback

            john.jurisoo yes we will look into that. I suspect it is a side-effect of https://github.com/Squirrel/Squirrel.Windows and the fact that there is potentially only 1 full install and from then on there are in place updates.

            minnsey added a comment - Thanks for the feedback john.jurisoo yes we will look into that. I suspect it is a side-effect of  https://github.com/Squirrel/Squirrel.Windows and the fact that there is potentially only 1 full install and from then on there are in place updates.

            I asked the three developers that had the problem last time to retry, and it worked correctly for the three of them.

            It seems fixed.

            Martin Véronneau added a comment - I asked the three developers that had the problem last time to retry, and it worked correctly for the three of them. It seems fixed.

            With version 3.1.2 out, I was able to upgrade several machines without issue.

            On a separate note, it would be nice if the version number in the Settings/Control Panel would track the current version when the application is updated.  That can be confusing for users.

             

            John Jurisoo added a comment - With version 3.1.2 out, I was able to upgrade several machines without issue. On a separate note, it would be nice if the version number in the Settings/Control Panel would track the current version when the application is updated.  That can be confusing for users.  

              698877135425 Mukesh Kumar
              5a54f3cc689b Magnus Björklund
              Affected customers:
              5 This affects my team
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: