search

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

crash due to aws_event_stream_rpc_server_continuation_send_message #111

Closed MRJYL closed 3 months ago

MRJYL commented 4 months ago

Describe the bug

We found some crashs when trying to start vefirication, but there don't have detailed information @phantumcode

screenshot-20240301-114537

phantumcode commented 4 months ago

@MRJYL Thanks for submitting the issue. Can you provide any details on how to reproduce the crash or how the crash was captured to help us reproduce and troubleshoot the issue?

MRJYL commented 4 months ago

The crash occurred when the user reported an error in the SDK callback and tried to retry the process。 I can't reproduce it reliably

thisisabhash commented 3 months ago

We have added some improvements in this branch fix/avcapture-session Could you please check out the branch to see if it helps with your issue?

MRJYL commented 3 months ago

I can't reproduce the crash stably. Maybe you could merge this fix to a new stable tag as soon as possible ,I will observe the online data @thisisabhash

phantumcode commented 3 months ago

@MRJYL Can you provide more context here. Based on the crash log, the crash is occurring in AWSLivenessSDK which is not our code. Did you create a wrapper around the Liveness library and called it AWSLivenessSDK? what exactly is happening in the wrapper that's calling aws_event_stream_rpc_server_continuation_send_message ? This seems to be calling into the AWS Common Runtime, which our library does not call.

phantumcode commented 3 months ago

Closing this issue as the crash is occurring outside of Liveness library code.

github-actions[bot] commented 3 months ago

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see. If you need more assistance, please open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.