Wild stab in the dark, but I'm guessing it's possible that there is an xcscmblueprint file that retains a pointer to the growl source tree.
I had a load of these a few weeks ago when a team member who uses SourceTree, not Xcode kept ignoring the xcscmblueprint file and as we switched branches, some of these triggered a "phone home" to Robbie Hanson's logging repo on github.
Update this path to that of your project and see if there is a link to the growl framework repo and if it's SVN
Just replace "Laurent" with your project name.
Laurent.xcodeproj/project.xcworkspace/xcshareddata/Laurent.xcscmblueprint
You might see stuff like this inside it but pointing to the growl repo:
"DVTSourceControlWorkspaceBlueprintRemoteRepositoryURLKey" : "https:\/\/
github.com\/CocoaLumberjack\/CocoaLumberjack.git",
"DVTSourceControlWorkspaceBlueprintRemoteRepositorySystemKey" : "com.apple.dt.Xcode.sourcecontrol.Git",
"DVTSourceControlWorkspaceBlueprintRemoteRepositoryIdentifierKey" : "35B5C9A93714EC9BEB56BAE809C5551E5C66E52D"
Hope this helps,
Alex Zavatone
On Oct 11, 2016, at 1:51 PM, Laurent Daudelin wrote:
I’m getting a bunch of SVN warnings all of a sudden for the Growl framework I’m using in my app. Thing is, I looked in the directory that Xcode 8 says where the error is but there is no .svn directory there. In the entire Growl framework package, I didn’t find a single .svn directly.
Any idea how I can get rid of those? I looked in the build settings but there doesn’t seem to be something about turning off those SCM warnings.
Thanks.
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden