You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
videoEndTimestamp ends up being the start time of the last video chunk containing data. This last video chunk could range from 0-1 seconds of content, resulting in the timestamp being off. This value is only used for metrics, and does not impact the challenge, as the actual end is determined by sending the empty video event.
For metric purposes, we should look to adjust this timestamp to be the proper end time.
Reproduction steps (if applicable)
No response
Code Snippet
// Put your code below this line.
Log output
// Put your logs below this line
amplifyconfiguration.json
No response
Additional information and screenshots
No response
The text was updated successfully, but these errors were encountered:
This issue was opened by a maintainer of this repository; updates will be posted here. If you are also experiencing this issue, please comment here with any relevant information so that we're aware and can prioritize accordingly.
Before creating a new issue, please confirm:
Which UI component?
Liveness
Gradle script dependencies
n/a
Environment information
n/a
Please include any relevant guides or documentation you're referencing
No response
Describe the bug
https://github.com/aws-amplify/amplify-android/blob/6bbb8c466e274caee8dca674d1acb6e8cbe5e372/aws-predictions/src/main/java/com/amplifyframework/predictions/aws/http/LivenessWebSocket.kt#L475
videoEndTimestamp
ends up being the start time of the last video chunk containing data. This last video chunk could range from 0-1 seconds of content, resulting in the timestamp being off. This value is only used for metrics, and does not impact the challenge, as the actual end is determined by sending the empty video event.For metric purposes, we should look to adjust this timestamp to be the proper end time.
Reproduction steps (if applicable)
No response
Code Snippet
// Put your code below this line.
Log output
amplifyconfiguration.json
No response
Additional information and screenshots
No response
The text was updated successfully, but these errors were encountered: