Codesigning Issue

A certificate used to sign our SDK was accidentally revoked on April 5th, leading to the invalidation of previously released SDK versions. This incident has caused errors during the integration of our SDK. We sincerely apologise for any inconvenience caused.

To address this issue, we have re-signed and updated all impacted versions to address these issues.

Below are detailed instructions to help you resolve the issue if you are impacted:

For Customers Integrating via Cocoapods:

1. Begin by removing the current version of the Intercom pod. This is achieved by commenting out the Intercom pod line in your Podfile, then running pod install. The output should indicate "Removing Intercom."
2. Next, clear the cached versions of the Intercom SDK by running pod cache clean 'Intercom' --all in your repository.
3. Re-include the Intercom pod in your Podfile by uncommenting the previously commented line.
4. Finally, run pod install again. A new, valid copy of the SDK will be installed.

If any issues arise during this process, running pod repo update before reinstalling the pod may be beneficial. This ensures that you have the latest podspecs from the CocoaPods repository.

For Customers Using Swift Package Manager (SPM):

1. Begin by removing the Intercom package from your project.
2. In Terminal, execute the following commands to remove caching related to the Intercom framework, which may be causing persistent errors:

   rm ~/Library/org.swift.swiftpm/security/fingerprints/intercom-ios-sp*; rm -rf ~/Library/Caches/org.swift.swiftpm/repositories/intercom-ios-sp*
   

3. Re-add the desired version of Intercom via SPM. (Please ensure that you are using https://github.com/intercom/intercom-ios-sp instead of https://github.com/intercom/intercom-ios when integrating Intercom as a Swift Package.) Note that a "Package Resolution Failed" error might occur. If so, selecting "Add Anyway" will resolve the package correctly and address the issue.

For Customers Manually Integrating the SDK:

1. Please re-download the SDK from our GitHub page. Specific versions can be found on this page.
2. Use the newly downloaded version to replace the existing copy in your project. The updated SDK will have valid signing.