
MEbling322309 (Community Member) asked a question.

MEbling322309 (Community Member) asked a question.
By clicking “Accept All Cookies”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts.
.png)
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Thank you for your response.
As for the "outside the scope of Veracode documentation", I disagree. The main Veracode documentation for iOS gives explicit instructions for turning on Bitcode for Cocoapods. It seems reasonable to expect that similar instructions (even pointers to external sites) could be expected to appear in the Veracode Help Center.
Hi @MEbling322309 (Community Member) ,
Sorry I missed a sentence in my original response, I've fixed it and reposted it below.
Unfortunately, maintaining documentation for Carthage is outside of our scope at this moment. If you would like to request documentation support for Carthage please consider proposing a Veracode Community Idea: https://community.veracode.com/s/ideas .
Thank you,
Boy Baukema
Hi @MEbling322309 (Community Member) - our engineering team looked into this a bit. Bitcode is enabled as a default setting in Carthage, see this reference in the Carthage documentation:
https://github.com/Carthage/Carthage#if-youre-building-for-ios-tvos-or-watchos
You shouldn't need to change any defaults, unless the framework pulled in by Carthage is dependent on a prebuilt framework that is not compiled with bitcode enabled. If that is the case, you would need to obtain a bitcode build of that framework from the framework distributor (or compile one yourself) in order for the full application to compile with bitcode enabled.
I hope that this helps clarify. Thanks!
Hi @MEbling322309 (Community Member) ,
Carthage uses xcodebuild to build referenced libraries. If those libraries have BITCODE_ENABLED=NO then no Bitcode will be produced. I would recommend reaching out to the respective library authors to ensure they include Bitcode in their build process. If they do not, you can look into manually modifying the build process for these libraries to produce bitcode, something like this may help: https://stackoverflow.com/questions/47431964/bitcode-disabled-on-carthage-dependencies . Though it may not be possible to generate bitcode for these libraries without further modifications.
Please note that while Veracode Static Analysis requires that iOS apps are built with Bitcode, ensuring that (Carthage managed) libraries are built with Bitcode is outside of the scope of Veracode documentation.
Instead I would recommend contacting the library authors and/or the general development community.
However, if anyone else has tips or recommendations for getting Carthage libraries built with Bitcode please do feel free to mention them here!
Thank you,
Boy Baukema