• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • 1.9.6
    • 1.9.5
    • Git
    • None
    • OSX 10.9.4

      In the latest version, the status of the files are not automatically updated after changes are made to any source file. Pressing Command-R refreshes the status.
      Command-R must be pressed even after committing changes to refresh the status.

          Form Name

            [SRCTREE-2531] Changes do not auto refresh

            swipeware added a comment -

            Thank you for great support!

            swipeware added a comment - Thank you for great support!

            Excellent, thanks for testing. This will be in the next official update!

            Steve Streeting (Inactive) added a comment - Excellent, thanks for testing. This will be in the next official update!

            swipeware added a comment -

            Yes! You've certainly tracked it down.
            I downloaded the new test-build, opened up an Xcode project and performed a number of changes that previously didn't show up. Now they did.

            Looks great!

            swipeware added a comment - Yes! You've certainly tracked it down. I downloaded the new test-build, opened up an Xcode project and performed a number of changes that previously didn't show up. Now they did. Looks great!

            I think I've tracked this down & eliminated it now. Please can you try this new test build: http://downloads.atlassian.com/software/sourcetree/SourceTree_autorefresh_log2.zip

            The logging is still on just in case this doesn't address it (in which case please attach the log again), but I'm fairly confident this will sort things out. It was down to a combination of factors in the end which the log really pointed out.

            Steve Streeting (Inactive) added a comment - I think I've tracked this down & eliminated it now. Please can you try this new test build: http://downloads.atlassian.com/software/sourcetree/SourceTree_autorefresh_log2.zip The logging is still on just in case this doesn't address it (in which case please attach the log again), but I'm fairly confident this will sort things out. It was down to a combination of factors in the end which the log really pointed out.

            Thanks for this, we'll be examining this in more detail asap.

            Steve Streeting (Inactive) added a comment - Thanks for this, we'll be examining this in more detail asap.

            swipeware added a comment -

            Thanks for the custom build. I followed the instructions, and here's what I did:

            I loaded an Xcode project called NinjaTwinz and added a new language localization for Italian. Xcode created a new folder called it.lproj with a single file InfoPlist.strings. I edited InfoPlist.strings and saved the file.
            These edits did not show up in SourceTree.

            After quitting the custom build, and re-starting the custom SourceTree build, the edits showed up. I included this restart as well in the attached log. I've separated the two logs with a "========" string and a remark.

            Hope this helps...

            swipeware added a comment - Thanks for the custom build. I followed the instructions, and here's what I did: I loaded an Xcode project called NinjaTwinz and added a new language localization for Italian. Xcode created a new folder called it.lproj with a single file InfoPlist.strings. I edited InfoPlist.strings and saved the file. These edits did not show up in SourceTree. After quitting the custom build, and re-starting the custom SourceTree build, the edits showed up. I included this restart as well in the attached log. I've separated the two logs with a "========" string and a remark. Hope this helps...

            Please can you try this test build: http://downloads.atlassian.com/software/sourcetree/SourceTree_autorefresh_log.zip

            This will log the processing of file events and their translation to auto-refreshes so we can see what's going on. It dumps a lot of messages quite fast so you don't really want to run it for long, but it should help. Please do the following:

            1. Unzip the SourceTree_autorefresh_log.app and put it anywhere you like
            2. Close any open versions of SourceTree
            3. Launch the custom build and try to reproduce the problem as quickly as you can
            4. Shut down the custom build
            5. Open Console.app
            6. Select 'All Messages' in the sidebar, then type 'AUTOREFRESH' in the search box in the top-right
            7. Select all the messages (Cmd-A) and copy them
            8. Paste into a text file and attach that here

            Please let me know which file it was that you updated in this test that you didn't see an auto refresh for. Hopefully the log will explain why that didn't translate into a refresh.

            Thanks

            Steve Streeting (Inactive) added a comment - Please can you try this test build: http://downloads.atlassian.com/software/sourcetree/SourceTree_autorefresh_log.zip This will log the processing of file events and their translation to auto-refreshes so we can see what's going on. It dumps a lot of messages quite fast so you don't really want to run it for long, but it should help. Please do the following: Unzip the SourceTree_autorefresh_log.app and put it anywhere you like Close any open versions of SourceTree Launch the custom build and try to reproduce the problem as quickly as you can Shut down the custom build Open Console.app Select 'All Messages' in the sidebar, then type 'AUTOREFRESH' in the search box in the top-right Select all the messages (Cmd-A) and copy them Paste into a text file and attach that here Please let me know which file it was that you updated in this test that you didn't see an auto refresh for. Hopefully the log will explain why that didn't translate into a refresh. Thanks

            I've set up a Git repo with the same folder structure (target/apple/ios) and created a new IOS application within that (my app.xcodeproj and associated template files). I also copy & pasted your global ignore settings into mine. I then committed everything and started modifying / adding files. Changes to .m, .mm, .h and Info.plist files were all picked up immediately by the auto-refresh.

            I think I'm going to need to give you a custom build with extra logging enabled to figure out what's going on in your case, I will post a link here when that's available.

            Steve Streeting (Inactive) added a comment - I've set up a Git repo with the same folder structure (target/apple/ios) and created a new IOS application within that (my app.xcodeproj and associated template files). I also copy & pasted your global ignore settings into mine. I then committed everything and started modifying / adding files. Changes to .m, .mm, .h and Info.plist files were all picked up immediately by the auto-refresh. I think I'm going to need to give you a custom build with extra logging enabled to figure out what's going on in your case, I will post a link here when that's available.

            Thanks. FYI you can always force a refresh with Cmd+R (or View > Refresh) - you shouldn't have to but it's a quicker workaround than restarting for the moment.

            SourceTree is itself developed with Xcode, and my settings include similar ignore entries such as xcuserdata - this is actually one of the benefits of the new suppression of refreshes for ignored folders since previously when Xcode wrote to that xcuserdata folder, which happens quite a lot, it would cause refreshes you don't care about. I'm not seeing anything obvious from your ignore list for now, but I will create a similar project with the same settings here to see if I can reproduce it.

            Steve Streeting (Inactive) added a comment - Thanks. FYI you can always force a refresh with Cmd+R (or View > Refresh) - you shouldn't have to but it's a quicker workaround than restarting for the moment. SourceTree is itself developed with Xcode, and my settings include similar ignore entries such as xcuserdata - this is actually one of the benefits of the new suppression of refreshes for ignored folders since previously when Xcode wrote to that xcuserdata folder, which happens quite a lot, it would cause refreshes you don't care about. I'm not seeing anything obvious from your ignore list for now, but I will create a similar project with the same settings here to see if I can reproduce it.

            swipeware added a comment -

            Here's the global .gitignore:
            *~
            .DS_Store
            CiderDebugger.lua
            GliderProperties.proj
            rgmeter/
            GGLibs/
            xcuserdata
            bin/
            assets/
            gen/

            There's no local .gitignore.

            I noticed that it happens with Xcode projects. After editing for example an Info.plist or an .mm file it doesn't refresh.
            The path to the files are always "target/apple/ios/", so the Info.plist would be "target/apple/ios/Info.plist".
            The path to the Xcode project is also like "target/apple/ios/myapp.xcodeproj"
            If I Quit SourceTree, and restart, the changes are reflected in SourceTree.

            swipeware added a comment - Here's the global .gitignore: *~ .DS_Store CiderDebugger.lua GliderProperties.proj rgmeter/ GGLibs/ xcuserdata bin/ assets/ gen/ There's no local .gitignore. I noticed that it happens with Xcode projects. After editing for example an Info.plist or an .mm file it doesn't refresh. The path to the files are always "target/apple/ios/", so the Info.plist would be "target/apple/ios/Info.plist". The path to the Xcode project is also like "target/apple/ios/myapp.xcodeproj" If I Quit SourceTree, and restart, the changes are reflected in SourceTree.

              Unassigned Unassigned
              bc392a12722d swipeware
              Affected customers:
              1 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: