Open brentleyjones opened 4 years ago
Any ideas how to put up a fix for this other than revert? @nglevin
We’ve just hit an error because of this. We renewed our certificate recently, and the imported frameworks weren’t resigned with the new certificate. It makes it an invalid build because the app and the frameworks were signed with different certificates. This seems like a rare case, but it would be nice to be able to opt out of this feature.
@Keith This should stay open. I'll update it to say the first part is fixed.
Sorry it auto closed
@brentleyjones How are you dealing with the third issue?
@thii We stopped stripping symbols as part of our IPA Post Processor. We now strip the symbols before they are imported by Bazel.
I see. I have a patch here that while it does not fix the above ipa_post_processor
issue, it can eliminate the need of doing bitcode stripping in ipa_post_processor
.
Neat. We also did Swift symbols stripping as part of the ipa_post_processor
, so that would need to be done (as well, in a different change).
4ec36b79fd35633581f5e1eb51c0bc7aac3f6031 regressed
apple_dynamic_framework_import
in a couple ways:ImportedDynamicFrameworkProcessor
~ Fixed with #856ImportedDynamicFrameworkProcessor
needsexecution_requirements = {"no-sandbox": "1"}
when there is a provisioning profile otherwise the sandbox blocks it~ Fixed with #862ipa_processor
a framework that is stripped of its code signature is no longer re-signed (in particular for us, when we strip bitcode and Swift symbols from a framework)