Fix Warnings

[goergisn]

Summary

• Checking if the compiler knows about the backported apple pay enum case
• Updating Project settings
• Adding @retroactive for extensions of foundational types

Background regarding #if compiler(>=6)

Xcode started complaining:

Extension declares a conformance of imported type 'Array' to imported protocol 'AdyenCompatible'; 
this will not behave correctly if the owners of 'Swift' introduce this conformance in the future

Issue

When adding the @retroactive tag it silences the warning but it will start failing if you build with a compiler that doesn’t know about this label. Which is the case on our CI because we need older Xcodes (with older toolchain) to get access to older Simulators to be able to test older iOS versions.

Solution

You can check for the swift or compiler version that is used to compile your project via a compiler directive.

e.g.

#if swift(>=6) // Checks for the minimum swift version
#if compiler(>=6) // Checks for the minimum compiler version

So wrapping the code in an #if compiler(>=6) block and providing the old code in the #else block silences the warnings AND allows you to build the code with older toolchains

Ticket

COIOS-000

[github-actions]

This pull request does not contain a valid label. Please add one of the following labels: ['new', 'changed', 'fixed', 'removed', 'deprecated', 'chore', 'improvement']

[github-actions]

✅ No changes detected

Comparing fix-apple-pay-warning to develop

---

Analyzed targets: Adyen, AdyenActions, AdyenCard, AdyenCashAppPay, AdyenComponents, AdyenDelegatedAuthentication, AdyenDropIn, AdyenEncryption, AdyenSession, AdyenSwiftUI, AdyenTwint, AdyenWeChatPay

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[goergisn]

Closing due to quite some changes for very little benefit