iOS Build Environment Help Center

ld64.lld: error: library not found for -lswiftCompatibilityPacks

append delete brian

Windows 10
Builder Version: 3.60
iOS SDK version: 16.4

Full error log
https://pmbaty.com/paste/?4a96b8beab3036f0#DxBA7jqFTPoitWksz2Ad8k6m4evBG6fSKWrPf1WW6ZKT

I recently added OneSignal (push notifications) to the project. It looks like it's related to this asset.

There are also some shell script errors, not sure if that contributes to this problem.

I found this previous post here that is similar, but I definitely used the latest migration assistant from 3.60:
https://www.pmbaty.com/iosbuildenv/help/thread.php?path=Problem%20solving/&file=about-unity-ads-4-4-0-requiring-swift

Thanks in advance!

Reply RSS

Replies

append delete #1. brian

UPDATE: The build got further after checking "Try to fix unresolved symbols automatically", so it's possible everything is working now.

Now there is an error because I have an app extension that needs a provisioning profile so I'm doing that now.

I will update back after this. Sorry if this was a false alarm.

append delete #2. Pierre-Marie Baty

Glad to know that. Please note that provisioning profiles for app extensions require to be named "xxxxxxx-AppEx.mobileprovision" where "xxxxxxxx" is the same filename as your app's main provisioning profile.

append delete #3. brian

Thanks for the info. I was confused so I decided to remove the extension for now. I may come back to it at a later date. I had no clue how or what to do to make a new profile. That may be another question I post.

I'll still report back if I can build after I complete the removal of the extension (in progress).

append delete #4. Pierre-Marie Baty

Was this issue solved ? I'll consider it is if no reply.

Reply

(Leave this as-is, it’s a trap!)

There is no need to “register”, just enter the same name + password of your choice every time.

Pro tip: Use markup to add links, quotes and more.

Moderators: Pierre-Marie Baty