[question]: ...xcframework is not signed with the expected identity and may have been compromised

[jward8]

How can we help?

I'm currently trying to resolve some build issues with our iOS app and when adding the following

into the frameworks and libraries of our OneSignalNotificationSerivceExtension, I've been getting the following errors:

“OneSignalExtension.xcframework” is not signed with the expected identity and may have been compromised. “OneSignalCore.xcframework” is not signed with the expected identity and may have been compromised. “OneSignalOutcomes.xcframework” is not signed with the expected identity and may have been compromised.

When looking and inspecting each framework in XCode I see that each framework is missing a signature and is unsigned.

Is there a way that I can resolve this? I haven't been able to find any documentation on how to fix this so far.

Any help would be appreciated!

EDIT: XCode Version is 15.4 (15F31d)

Code of Conduct

• I agree to follow this project's Code of Conduct

[obyadur-rahman-tsc]

Having the same issue here in Xcode Version 15.4 (15F31d)

[stefandbd]

Same issue here on Xcode Version 15.4 (15F31d)

[josancamon19]

Same issue here Version 15.3 (15E204a)

[emawby]

@jward8 Thank you for reaching out are you getting this issue on the latest SDK version? Does downgrading to an older version fix the issue? The team can potentially attach new binaries that are properly signed to the affected release versions.

[jward8]

@emawby I was on 3.12.3. I ended up updating to the most recent version of OneSignal (5.1.3). It resolved the issue, however now I get a different issue related one of the frameworks. I added in the OneSignal.xcframework and now I get this error:
error: There is no XCFramework found at '/Users/distiller/project/Pods/OneSignal/iOS_SDK/OneSignalSDK/OneSignal_XCFramework/OneSignal.xcframework'. (in target 'OneSignalNotificationServiceExtension' from project

[emawby]

@jward8 Good to hear that upgrading resolved it. It seems like the new issue is related to your NotificationServiceExtension and you are using cocoapods. If you have previously had it working then you could trying clearing derived data and your cocoapods cache then reinstalling pods. If it has never worked then if you could share your Podfile and target settings that would be helpful!