The signature of cannot be validated and may have been compromised

I'm currently developing a Unity game for iPad and have run into a critical issue that's completely blocking me from building the project. The project uses the Mapbox SDK for Unity.

Everything was working fine during today test build on the iPad. I made minor changes - just four scripts, then attempted another build. However, Xcode began showing the following error:

The signature of “MapboxCommon.xcframework” cannot be validated and may have been compromised. Validation Error: The signing certificate has been revoked (CSSMERR_TP_CERT_REVOKED)

This error now occurs consistently. I've tried building on a different MacBook and with a different Apple account, but the result is the same. I haven't made any changes to the Mapbox framework, nor have I updated it recently.

I'm trying to determine the root cause:

  • Is this something I've done on my end? Or is it an issue with the Mapbox framework or their signing certificate?
  • Is there a temporary workaround that would allow me to proceed with development builds while I investigate a proper fix?

Any insights or suggestions would be greatly appreciated.

Answered by DTS Engineer in 848864022

It’s hard to offer help in situations like this, where your development environment is so heavily dependent on third-party tooling. My general advice is run a quick test with just Apple tools (more on that below). If that works, you know that the Apple side of this is working correctly, and you can escalate your real question via the support channel for the third-party tools you’re using.

My proposed test is pretty simple:

  1. Create a new test project from Xcode’s build-in iOS > App template.
  2. Give it the same bundle ID as your main app.
  3. Build and run it on your test device.

If that works, we know that your basic code signing setup is valid.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

It’s hard to offer help in situations like this, where your development environment is so heavily dependent on third-party tooling. My general advice is run a quick test with just Apple tools (more on that below). If that works, you know that the Apple side of this is working correctly, and you can escalate your real question via the support channel for the third-party tools you’re using.

My proposed test is pretty simple:

  1. Create a new test project from Xcode’s build-in iOS > App template.
  2. Give it the same bundle ID as your main app.
  3. Build and run it on your test device.

If that works, we know that your basic code signing setup is valid.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

The signature of cannot be validated and may have been compromised
 
 
Q