App Store Connect upload fails when using Fyber 8.2.7.0

[Calabash-Boy]

MAX Plugin Version 6.4.3 Xcode 15.2 Device/Platform Info iOS Current Behavior Currently facing this problem when trying to upload a production build to Testflight.

Invalid Bundle. The bundle XXX.app/Frameworks/IASDKCore.framework does not support the minimum OS Version specified in the Info.plist.

It is ok if I downgrade Fyber's SDK to 8.2.6

When I try to fix this, I find this: https://forums.developer.apple.com/forums/thread/705297 there is the reason: the binary is MinimumOSVersion 12.0, but info.plist is 11.0, can you fix this?

[2energycell]

Hi, when you use Xcode 15.2, the min iOS version is 12.0. Our SDK per se supports iOS 11, but it will not under Xcode 15.2, since Xcode itself supports at the minimum the iOS 12. Also you can override the info.plist settings and define iOS 12 as min supported version. Also our next release which is 8.3.0 supports min iOS version 12.0. Thanks.

[icywire]

@Calabash-Boy When you use 8.2.7 or 8.2.8 make sure you don't have IASDKCore.xcframework linked directly to application target in Xcode. If it's there, try to remove that manually.

Other option - update DT Exchange dependency in AppLovin dependency manager in Unity. Changing versions in Podfile only (without updating Unity plugins) may cause integration issues.

[Calabash-Boy]

Hi, when you use Xcode 15.2, the min iOS version is 12.0. Our SDK per se supports iOS 11, but it will not under Xcode 15.2, since Xcode itself supports at the minimum the iOS 12. Also you can override the info.plist settings and define iOS 12 as min supported version. Also our next release which is 8.3.0 supports min iOS version 12.0. Thanks.

I had tried to override the info.plist settings, but it cause signature error about IASDKCore.framework. Am i right?

[Calabash-Boy]

@Calabash-Boy When you use 8.2.7 or 8.2.8 make sure you don't have IASDKCore.xcframework linked directly to application target in Xcode. If it's there, try to remove that manually.

Other option - update DT Exchange dependency in AppLovin dependency manager in Unity. Changing versions in Podfile only (without updating Unity plugins) may cause integration issues.

Yes, I don't have IASDKCore.xcframework linked directly to application target. as @2energycell said, Fyber 8.3.0 will fix this.

[Calabash-Boy]

@2energycell I have one more question: Xcode 15.2 Fyber 8.2.6 works well! Fyber 8.2.7 upload fails? Both in Xcode 15.2, why is that? when I run the "vtool -show " commond to check binary file, here is 8.2.6, version 11.0, but there is no minos

Load command 8 cmd LC_VERSION_MIN_IPHONEOS cmdsize 16 version 11.0 sdk 16.1 Load command 9 cmd LC_SOURCE_VERSION cmdsize 16 version 0.0

here is 8.2.7, minos is 12

Load command 7 cmd LC_BUILD_VERSION cmdsize 32 platform IOS minos 12.0 sdk 17.2 ntools 1 tool LD version 1022.1 Load command 8 cmd LC_SOURCE_VERSION cmdsize 16 version 0.0

Maybe this is the reason?

[icywire]

8.2.6 is dynamic framework, 8.2.7 is static framework.

This is Xcode issue, Apple is working on it, check this thread https://developer.apple.com/forums/thread/749554 For some developers downgrading Xcode to 15.1 or 15.0 helped.

[elena-krakhmalova]

Hi @Calabash-Boy ! If you change SDK’s Info.plist manually - yes, it will cause code signature failure. As a temporary workaround to prevent signature checks you can try to remove whole _CodeSignature folder.