[iOS] Archive build fails with signature-collection error for MolocoSDK.xcframework

[shnktt]

Hello,

I am integrating the Moloco SDK via the MAX mediation adapter, but I am encountering a build error related to signature collection.

Environment:

• Xcode 26.1.1
• AppLovinSDK 13.5.1
• AppLovinMediationMolocoAdapter 4.1.0.0

The error occurs during the build/Archive process, and the output is as follows:

SignatureCollection
builtin-collectSignature --input MolocoSDK.xcframework --output MolocoSDK.xcframework-ios.signature --info platform ios --info library MolocoSDK.framework

error: signature-collection failed: The operation couldn’t be completed. (SWBUtil.CodeSignatureInfo.Error error 0.)

The Moloco SDK had been integrated previously and builds succeeded without any issues,
but this error suddenly began occurring even though the SDK version has not been changed.

Could you please advise what might be causing this issue or how to resolve it?

If GitHub is not the appropriate place to report this issue, please let me know the correct support channel.

Thank you in advance.

[1111tekila]

Same here

[betulcetinkaya]

Same issue here. It started happening a few hours ago

[chribbe]

Same here when trying to build just now!

[ajithvl]

Hello everyone,

We have identified the issue affecting the Moloco iOS SDK. This problem has now been resolved in Moloco SDK version 4.1.1.

📝 Details

The issue was caused by an expired signing certificate that was not updated in our release pipeline.
As a result, Moloco iOS SDK build was distributed with an outdated certificate, which caused Xcode’s validation step to fail during signature collection.

Please note:

• This does not affect any applications already distributed through the App Store.
• It only affects developers integrating or updating the SDK during the affected window.
• Updating to SDK version 4.1.1 should fully resolves the issue.

If you attempted to update the SDK before the fix was released CocoaPods may have cached the previous build of the SDK.
To ensure the correct version is used, please clear your local pod cache and reinstall:

# Remove existing pods, clear cache for MolocoSDKiOS, and reinstall
rm -rf Pods/MolocoSDKiOS Podfile.lock && pod cache clean 'MolocoSDKiOS' && pod install

⚠️ Important:
When cleaning the cache, please ensure CocoaPods resolves to Moloco SDK 4.1.1.

🛠 After running the above steps

Rebuild your project, and the signature-collection step should succeed without issues.

We apologize for the inconvenience this caused and appreciate your patience while we worked to resolve it.
If you continue to experience problems or have additional questions, please let us know.

Thank you again for your support!

[steven-taehyeon-hwang]

Hi Moloco Team,
Thanks for the quick fix on the certificate issue!
We're currently using MolocoSDK 3.13.0 and would prefer to stay on this version to minimize potential side effects from upgrading, as 4.1.0+ bumps the Google Mobile Ads SDK dependency to 12.14.0.
Could you please re-sign and re-release version 3.13.0 with a valid certificate as well?
Thanks!

[shnktt]

Thanks for the quick fix!

Updating to Moloco SDK 4.1.1 and clearing the pod cache solved the issue.
Everything builds correctly now.

Really appreciate the support!

[ajithvl]

We have released MolocoSDK 4.1.2, which will not require clearing local pod cache. Please note that this version is still pending certification from mediation partners.

@steven-taehyeon-hwang In parallel, and based on your request to remain on the 3.x line, we have also released MolocoSDK 3.13.1, which has been re-signed with a valid certificate.
However, this version is not yet certified by mediation, so it will need to be integrated manually.

🔧 How to install MolocoSDK 3.13.1 manually in Xcode

- Download the re-signed SDK from the link above
- Unzip the archive to obtain MolocoSDK.xcframework.
- In Xcode, open your project and remove the existing MolocoSDK.xcframework from your project
- Drag and drop the new MolocoSDK.xcframework into your project’s Frameworks folder. Ensure "Copy items if needed" is checked and add it to your app target(s). Clean and rebuild your project.

[steven-taehyeon-hwang]

@ajithvl Thanks for getting 3.13.1 out so quickly! Really appreciate it 🙏

[ahmadrazagd]

@ajithvl Can you please confirm whether this version 4.1.2 has been certified by the mediation partners or not?

[yifriday]

why I encounter this on 3.9.1 also?

[namquang93]

We're having a problem with the MolocoSDK version 3.10.0. Can you provide a signed one for 3.10.0 please? The project is running already so we don't want to upgrade the SDK.