No way for Cocoapod Users

[iThink32]

• Amplify V2 is only released for SPM users. My current setup includes private pods having a dependency on Amplify-Swift. At the moment Cocoapods does not support SPM as dependencies and hence im unable to use the above framework.
• Please provide a Cocoapod for the above release as this is a major release and SPM is not mature enough at the moment for a compete overhaul

[phantumcode]

Hi @iThink32
We currently don’t have any plans to support CocoaPods for Amplify Swift version 2.x. However, we’d like to understand your use case; Could you share the reason you can’t use SPM with us?Thanks!

[github-actions]

This has been identified as a feature request. If this feature is important to you, we strongly encourage you to give a 👍 reaction on the request. This helps us prioritize new features most important to you. Thank you!

[iThink32]

@phantumcode first off given a thumbs up.

Next please consider the following situation.

1. Amplify 2.x is a major upgrade. Moreover those using Amplify 1.x have to migrate as it has been put into maintenance. So on these lines at least, cocoa pods being the most widely used build dependency, must be supported.
   At least till 2.x as a migration has to be done.

2. My use case:
   Consider the following project dependency graph

A(main app)
|
B(framework)
|
C(framework that uses amplify)

with the above graph in mind, C has a pod spec with a dependency on amplify so indirectly B and finally A gets it.

Currently with cocoa pods, there is no way to use SPM as a dependency in a podspec.So If I add Amplify in C I cannot use it in B or A. And if I add it in A I cannot use it in B or C.

SPM is not mature enough at the moment to completely migrate as well due to

1. Lack of reliable working style of local packages
2. Lack of subspec like approach.

Due to the above reasons I either have to migrate our entire project to SPM or think of letting Amplify go completely.
Please do not make me leave Amplify as I cannot migrate our project to an immature Dependency Manager.

[iThink32]

If even that is not possible can you share an XCFramework for us to use or suggest a way around for cocoa pod users.

[NewLand-Ju]

@phantumcode I am working on a project using Flutter.
I am using amplify-swift for Flutter iOS plugin, but currently Flutter does not support SPM, only supports cocoapods.

[phantumcode]

@NewLand-Ju Did you consider using Amplify Flutter?

[iThink32]

@phantumcode please consider my request as v2 has already been moved to maintenance

[phantumcode]

@iThink32 Unfortunately, we don't have any plans to add Cocoapod support for Amplify V2. You'll need to add SPM support in order fully migrate to Amplify V2. As a workaround, you could wrap Amplify V2 in an xcframework and/or host that xcframework as a podspec in your build system.

[iThink32]

Hi @phantumcode can you at-least provide the xcframework? The amplify v2 framework has a lot of dependencies and combining all of them is going to be a tough task for someone who has no context. Can i at-least expect an xcframework to be shared?

[phantumcode]

@iThink32 We'd like SPM to be our distribution method. Depending on different usages, the xcframeworks would be limited to a subset of categories as well. As a result, it is not something that can we can officially provide support for either.

[Robopicker]

@phantumcode, I am currently working on a Flutter project. I successfully installed the necessary face liveness dependencies using SPM. However, when building the app on real iPhone devices, I'm experiencing unusually long build times, which is quite perplexing. Could you please suggest a solution to address this issue? Alternatively, if you know of any workarounds for integrating face liveness into a Flutter project, your assistance would be greatly appreciated. Thank you!