Getting error "Symbol not found" when adding AEPAssurance .xcframework file to app. | Community
Skip to main content
December 7, 2021
Solved

Getting error "Symbol not found" when adding AEPAssurance .xcframework file to app.

  • December 7, 2021
  • 3 replies
  • 1897 views

We are trying to add AEPAssurance framework manually to our iOS project which is mix of objective-c and swift. For that first we cloned the repo: https://github.com/adobe/aepsdk-assurance-ios
and then we ran the "Make archive" command to extract the .xcframework file and then we are trying to add that XCFramework file in our project but we are facing this error Symbol not found. we tried adding it in empty swift project also but still the error is same. Any solution for same

We raised the issue in AEPAssurance repo it self, more details could be found in this link:
https://github.com/adobe/aepsdk-assurance-ios/issues/41

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by pkpravin

Gathering more information from slack to solve the problem. Working towards resolution. Will keep you posted.

 

Thanks,

Pravin Prakash Kumar

Computer Scientist 

Adobe

3 replies

pkpravin
Adobe Employee
pkpravinAdobe EmployeeAccepted solution
Adobe Employee
December 8, 2021

Gathering more information from slack to solve the problem. Working towards resolution. Will keep you posted.

 

Thanks,

Pravin Prakash Kumar

Computer Scientist 

Adobe

SatMatAuthor
December 9, 2021

Thanks Pravin wanted to add some more details for your info.
- We are using xcode 12.4
- We are adding framework manually(not using cocoa pods or swift package manager)

SatMatAuthor
December 14, 2021

Hi Pravin,

Were you able to found any solution for same?

SatMatAuthor
December 18, 2021

@pkpravin can you please share the link to download the latest SDKs here?

pkpravin
Adobe Employee
Adobe Employee
January 6, 2022

This issue happened because of ABI incompatibility between AEPAssurance and AEPCore when using manual xcframework builds.

The solution is to create a new AEPAssurance.xcframework that is compatible with AEPCore
make archive command has been updated to create an ABI compatible version of AEPAssurance with the latest AEPCore. Make sure to run this command and generate new AEPAssurance.xcframework each time you update AEPCore

 

Thanks,
Pravin Prakash Kumar