But in those cases, the developers had installed hacked versions of Xcode itself. There have been instances of developers distributing malware-laden builds. It will restrict itself to scanning just those handful of important places and not get in your way. The only one I would recommend is MalwareBytes. You could try installing some other AV product to satisfy your IT department.
#SOPHOS OR AVAST FOR MAC ARCHIVE#
And even if it weren't, you wouldn't have to worry because Xcode doesn't use that folder when making archive builds. Reproducting themselves by infecting your Derived data folder is far beyond their capabilities.
#SOPHOS OR AVAST FOR MAC FOR FREE#
If you go searching for free movie downloads and **** long enough, you might be able to get yourself infected with some adware. You aren't going to get infected by a Mac virus because no such thing exists.
#SOPHOS OR AVAST FOR MAC FULL#
Your Mac could be chock full of malware and if there wasn't any mechanism to get it running and keep it running, it would be absolutely harmless. There are only a handful of folders that even matter for such purposes in the first place.
There aren't any magic folders you need to exclude. Scanning the disk like that is a pathetic waste of time. Your IT department has no idea how Macs work. In all seriousness, get your resume in order and start looking for a job.
Lastly, any other advice about solving this problem is appreciated. But am I being cavalier about the risk of a built product getting infected and distributed before it's replaced by a new build? So even if by unlikely chance a virus was able to get onto my Mac and infect the DerivedData folder without being detected anywhere else, the build products in DerivedData are frequently updated from new builds which should overwrite and replace any infected files every new build, so there should be almost no risk. Secondly, I believe that DerivedData is safe to exclude, because it's built from source, and both the source and XCode (and it's tools) will be AV scanned. But am I right, is there any other directories where a lot of writing occurs during builds that I should consider? So I'm lookin for advice from anyone who has thought about or done this.įirst, I believe that all of the writing XCode does when building/compiling is within the DerivedData directory, so that's the obvious target to exclude from AV scanning. So it's on me to figure out what files to exclude that will help restore my compile times, without introducing a dangerous vector onto my machine. I have noticed that building a small IPA takes 10 minutes on my top of the line 2017 MBP, and that definitely seems way slower (spends forever generating bitcode). Since we've done that it appears my compile times have increased, but I didn't benchmark so I don't know by how much. Now at my new company we've installed the same AV solution, Sophos. Unfortunately I wasn't part of the process with IT so I don't know which files were excluded.
At a previous job where we had very slow build times (like way slower than you even expect Swift code to build :), we found that excluding certain files from AV scanning substantially reduced build times.
0 kommentar(er)
