Issue using amazon-connect-chat-ios with amplify-swift

[gevartosky]

While trying to install amazon-connect-chat-ios in a project that uses amplify-swift I am getting this error

multiple similar targets 'AWSAPIGateway', 'AWSAutoScaling', 'AWSChimeSDKIdentity' and 30 others appear in package 'aws-sdk-ios-spm' and 'aws-sdk-swift', this may indicate that the two packages are the same and can be de-duplicated by using mirrors. if they are not duplicate consider using the `moduleAliases` parameter in manifest to provide unique names

Trying to fallback to installing the xcframework manually throws the same error as #43

Is there a recommendation to use amazon-connect-chat-ios with amplify-swift?

[mliao95]

Hi @gevartosky,

It looks like there are conflicting module names in aws-sdk-swift which is a dependency of amplify-swift and aws-sdk-ios-spm which is a dependency of amazon-connect-chat-ios.

Is your dependency on amplify-swift in the same target that you are using amazon-connect-chat-ios? For our own understanding, what is your use case of using both libraries and which modules in amplify-swift are you using?

[gevartosky]

Thanks for the help.

Is your dependency on amplify-swift in the same target that you are using amazon-connect-chat-ios?

Yes

what is your use case of using both libraries and which modules in amplify-swift are you using?

For Amplify, I'm AWSAPIPlugin and AWSCognitoAuthPlugin. Mostly for REST and GraphQL calls.

And for Amazon connect we are using it for a live chat feature.

[mliao95]

Hi @gevartosky,

I'm not finding a great way to use both libraries together outside of splitting the files that need amplify-swift in one target and the ones that need amazon-connect-chat-ios in another target.

You could build the live chat feature as a separate build target, and that should fix the dependency conflicts. Alternatively, you could try forking this project and implement new moduleAliases to avoid naming conflicts with aws-sdk-swift modules.

Let me know if either of those solutions work for you.

[gevartosky]

Thanks @mliao95

ModuleAliases was my next on the list. I'll try that

I also cloned the repo and tried to adopt aws-swift-sdk. A lot of the types match, with a couple of exceptions. I have a feeling it could be doable, but not sure there is any interest in adopting aws-swift-sdk.

[mliao95]

We will take a look into adopting aws-swift-sdk, but do not currently have a timeline for the migration effort.

[vincent-peng]

@mliao95 I think indeed a totally valid use case, this is also happening for our company which utilize quite many of AWS services in the project.