André

I tried some things but couldn't make it work... ``` @swift build \ -c release \ --disable-sandbox \ --build-path "$(BUILDDIR)" \ -Xswiftc \ -emit-module-interface \ -Xswiftc \ -enable-library-evolution \ -Xswiftc...

After more digging, I did manage to enable module stability successfuly and tested the same binary with Swift 5.3.2 and Swift 5.4. Unfortunately, it was not clean. Here are the...

It's a regression in Xcode 13. Sample project here: https://github.com/andre-alves/xcode13-indexing-problem Please, provide feedback to Apple about this issue so they can prioritize it.

This attribute would be really helpful to us. I was about to start this discussion and propose a **[diff](https://github.com/andre-alves/rules_apple/commit/ac34c6a8ea641a9142cdf73f317863ff43740e86)**, but it's the same as @keith's. I'm migrating a big repo...

+1

Still missing privacy manifests for `FBSDKLoginKit` and `FBSDKShareKit`...

IMHO the fallback should be optional (maybe provide templates without it?) because it increases app size since the same text will be bundled twice (hardcoded binary and .strings file).

> Does waiting for Index Build to be finished, closing Xcode, and opening it again fix it? Unfortunately not, it's always failing. It seems that the error started in 1.7.0...

Humm, just removed this line from the `.bazelrc` and the problem no longer happens: ``` build --features="swift.vfsoverlay" ``` Seems to be related to the vfsoverlay. The background indexer is working...

Will probably add `build:rules_xcodeproj --features="-swift.vfsoverlay"` to workaround this issue :+1: _--- edit Sorry, I miss clicked and closed the issue xD._