AppStoreConnect WARNING about MinimumOSVersion

[ghost]

Report

SDK Version

6.14.0

What did you do?

Uploaded app build with AppsFlyer-Dynamic dependency to AppStoreConnect

What did you expect to happen?

Build is uploaded without warnings

What happened instead?

Got email from AppStoreConnect stated

Although delivery was successful, you may want to correct the following issues in your next delivery. Once you've corrected the issues, upload a new binary to App Store Connect.

ITMS-90747: Architecture incompatible with MinimumOSVersion. The app bundle at '***.app/Frameworks/AppsFlyerLib.framework' specifies a MinimumOSVersion of '100.0' but contains a 32-bit architecture that is unsupported on iOS 12 and later.

[bogdanmatasaru]

please fix this

[popwarfour]

Fix please

[PrakashT]

Hello, we are having the same issue, any update on this issue?

[kgaidis]

There are a bunch of other issues around this:

• https://github.com/AppsFlyerSDK/AppsFlyerFramework/issues?q=is%3Aissue+MinimumOSVersion

The only thing that worked for me was switching from "Dynamic" to "Static" (the other solutions like clearing SPM cache were unsuccessful for me):

https://github.com/AppsFlyerSDK/AppsFlyerFramework-Static

[dandreiolteanu]

Same issue here, any plans to update this?

[TheCoordinator]

This seems to be quite critical, how come we're not hearing from AppsFlyer team?

[popwarfour]

googleads/swift-package-manager-google-mobile-ads#62

The version 100 appears to be an Xcode 15.3 work around. It’s an annoying warning but seems pretty harmless for now. The dynamic lib is working for us at the moment though.

There is a separate, far worse issue, where the checksums defined in the package file are not matching the underlying binary lib. I haven’t dug into why this happened but I suspect the release was botched and not resolved properly vs a local SPM cache issue.

[ge-af]

Hi all,
Our R&D team is aware of this matter and is trying to seek resolutions with highest priority to this issue.
As we understand and also manage to reproduce on our end - this is indeed a warning and not an actual rejection of the app version submission to the App Store.

We identified that the problem appears to be related to the Dynamic variant of the framework using SPM only and it is indeed a combination of the previous workaround issue we have with Xcode archive issue and the fact that our SDK is still support ARMv7 devices due to our minimum iOS version of iOS 9.
We are currently on track with this issue and going to fix it in the upcoming releases.

In order to mitigate any possible issue from your side, we highly recommend to use the Static variant of the framework until this will fully be resolved on our side.

If you do not meet the conditions for what mentioned above (you're using CocoaPods, Carthage, etc.) nor using the Dynamic variant, please reach out to our Support team at [email protected] and we will be more than happy to assist.
Thank you!

[ge-af]

Hi all, we released iOS SDK v6.14.2 that should address the above.

Please let us know if you stumble upon any issue while upgrading to it. You can also reach out to our Support team at [email protected] and we will be more than happy to assist.