aws-amplify / amplify-ui-swift-liveness

This repository offers a UI component for Amazon Rekognition Face Liveness, enabling developers to ensure that only authentic users, and not bad actors using spoofs, can access their services.
https://ui.docs.amplify.aws/swift/connected-components/liveness
Apache License 2.0
8 stars 18 forks source link

Unable to create Carthage/Build folder #63

Closed CoderNamedHendrick closed 9 months ago

CoderNamedHendrick commented 9 months ago

I'm currently trying to get the amplify-ui-swift-liveness package via Carthage since cocoapod support doesn't seem available. Running carthage update I get a result which says *** Skipped building amplify-ui-swift-liveness due to the error: Dependency "amplify-ui-swift-liveness" has no shared framework schemes

I'm running XCode 14.3.1 Any help to resolve this? This is urgent as setting the liveness is all that's left to launch our MVP.

More context as regards the issue

CoderNamedHendrick commented 9 months ago

@phantumcode please can you help me as regards this? Getting the package via SPM causes the build to take so much time which causes Xcode to crash occassionaly

phantumcode commented 9 months ago

@CoderNamedHendrick Thanks for submitting the issue. What is the specific crash that you're running into? To clarify, you're building a Flutter app and want to include the liveness library? Have you tried cloning the repo and building it as a local SPM? The library doesn't support carthage, and you should be consuming it via XCode as an SPM package.

CoderNamedHendrick commented 9 months ago

@phantumcode I don't run into any specific crash, Xcode keeps on compiling forever which usually leads to it crashing due to the memory hog. Yes I am, I am building a Flutter app and including the liveness library, I've successfully done so on Android which I am more familiar with. Would cloning it as a local SPM package improve the build time? Oh, I got a feeling Carthage wasn't supported when I didn't see support for cocoapods.

CoderNamedHendrick commented 9 months ago

@phantumcode importing the package locally resolves this issue.

I'll close the issue now. Thank you for all your help

Robopicker commented 7 months ago

Hey @CoderNamedHendrick , glad to hear that you have solved this issue. I am also facing the same issue in one of my personal flutter project. please help me with this doubt on which project did you add the package locally in Runner or Pods? I tried adding package in Runner project but no luck. Your response will save me lot of time. please help

CoderNamedHendrick commented 7 months ago

Hello there @Robopicker. I solved the issue by forking this repository and cloning it on my local machine before importing it to my project as a local dependency.

This article helped.