Add Support for Swift Concurrency

[Mackarous]

Summary

Currently, if using the SDK in a project that enables strict concurrency checking, Xcode will complain that the Amplitude object is not marked as Sendable and is not concurrency safe.

To circumvent these warnings (which may become errors in Swift 6), we can mark the library as @preconcurrency

@preconcurrency import AmplitudeSwift

Motivations

Swift Concurrency is becoming a large part of the Swift language, and moving into 6.0 will be important to add support. This might mean exposing a different kind of object, or migrating the Amplitude class itself to an actor.

[crleona]

Hi @Mackarous - this is planned but we do not yet have an ETA.

[tareksabry1337]

@crleona Xcode 16 is around the corner, any plans to get this done?

[klioop]

please support it
It is frustrating add unchecked and sendable every time ampli pull
please

[Mackarous]

@klioop I looked into originally trying to support this when I needed it last year.

There's no way they'll end up doing this. It would require a thorough understanding of Swift Concurrency throughout the codebase and almost an entire rewrite of how things are architected at the moment as they utilize a lot of APIs that Apple has marked as @MainActor isolated, as well as a ton of singletons all over the place.

You are better off just using @preconcurrency import

[tegui]

What can we do if
@preconcurrency import AmplitudeSwift
is not working and we are getting a crash at the Mediator.execute(event) method after update to the latest SDK version?

With 1.0.0 we did not get that issue, with 1.12.0 we have that.