XCode 12 Archive Fails

[jehartzog]

Related issues #86 #119.

Since this is blocking us, we're going to open a CSM ticket in parallel to reporting here.

Reproduction

1. With fresh app, follow Iterable docs to setup library

Expected

1. Dev builds work, archive works

Actual

1. Dev build works, archive fails with Use of undeclared identifier 'IterableAPI'.

Troubleshooting steps taken

• Have @import IterableSDK; at the top of AppDelegate.m
• Added blank swift bridging header
• Play with different Library Search Paths per this comment
• Set Always Embed Swift Standard Libraries to no

Env

1. App boilerplate created with ignite cli v6.5
2. XCode v12.4
3. React Native 0.64
4. Cocoapods 1.10.1

[jehartzog]

At Michael's (CSM) request, here is our AppDelegate.m.

[jehartzog]

We finally figured this out. There were two issues going on:

1. The original error posted here was due to my error, you can see in the listed AppDelegate.m that I had inadvertently nested @import IterableSDK; inside the flipper #ifdef statement. This was quickly identified by the Iterable CSM and corrected.

2. We hit new errors exactly as listed in Unable to archive on XCode 12 #86. For whatever reason, the setting that required config to edit was not in our application target, but in our project configuration. Once we realized the documentation was leading us to look at the incorrect place, we were finally able to archive the build. Attaching screenshot since it's XCode.

[1280103995]

Hi jehartzog,
The troubleshooting steps are complete, but it not work for me.

I added "$(TOOLCHAIN_DIR)/usr/lib/swift-5.0/$(PLATFORM_NAME)" and "$(inherited)" to Library Search Paths, but it didn’t work. (It’s worth noting that it was originally empty here)

XCode v12.5
React Native 0.64.2
Cocoapods 1.10.1

Could you give me some suggestions? Thanks!

[jehartzog]

@1280103995 I don't have much for you. After removing the $(TOOLCHAIN_DIR)/usr/lib/swift-5.0/$(PLATFORM_NAME) entry, we actually had to add it back when we added the iterable message extension to enable rich iOS pushes. Already spent way too much time trying to configure swift-5.0 vs not, and still not sure exactly where we ended up.

[1280103995]

I read the first point carefully and after adjusting the import position, it worked. Cheers!