Luis Padron

This was removed in https://github.com/bazelbuild/rules_apple/pull/2670

To start, do we need `unprocessed_archive.zip`, at least going off this comment it seems related to Tulsi which is AFAIK deprecated: https://github.com/bazelbuild/rules_apple/blob/c5a3307c481c8fb5f9d8eefe53a62e1902b80410/apple/internal/processor.bzl#L570-L576

Turns out the comment saying this was for Tulsi only is incorrect, its the archive used when not using tree artifact outputs.

Yeah id love to make tree artifacts the default, theres this blocker right now: https://github.com/bazelbuild/rules_apple/pull/2545

Related to #248

~~Duplicate of #248~~, thanks for working on this @lucasmarcal-faire! edit: ah I see theres two issues tied with this one

I imagine it's when using rules_xcodeproj since that makes it a lil easier to view the external files / when viewing external sources and accidentally editing a file

I believe this should be resolved by https://github.com/cgrindel/rules_swift_package_manager/pull/1260 (it removes de-duplication of the generated attrs which is the root cause of this PR) and then https://github.com/cgrindel/rules_swift_package_manager/pull/1423 should add proper support...

Is there any update on this issue? We're seeing ld terminate with segfault from a signal and believe this could be related. Have folks found any workarounds in the meantime...

This is a pretty bad experience, +1 to fixing the undefined var