Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Intermittent: Completion handler not called in getTemporaryContentUrlsForAttachedMedia #57

Open
kuchmiyalex opened this issue Mar 17, 2024 · 4 comments
Assignees
Labels
category:bug disposition:triage The bug requires triage

Comments

@kuchmiyalex
Copy link

SDK version

4.0.3

Device model

iPhone 14 Pro Max

OS version

17.4

Issue description

Description

Problem:

The getTemporaryContentUrlsForAttachedMedia function in the TwilioConversationsClient library intermittently fails to call the completion handler as expected. This issue persists even after attempting to retry the function. It seems that only reconnecting the TwilioConversationsClient resolves this issue.

Function Signature:

- (nullable TCHCancellationToken *)getTemporaryContentUrlsForAttachedMediaWithCompletion:(nonnull TCHMediaSidsCompletion)completion NS_SWIFT_NAME(getTemporaryContentUrlsForAttachedMedia(completion:));

Expected Behavior:

The completion handler should be called upon the successful execution of the getTemporaryContentUrlsForAttachedMedia function, providing the necessary temporary content URLs for attached media.

Actual Behavior:

The completion handler is not being called intermittently, leaving the user without the expected temporary content URLs. Additionally, no error is received, which is part of the TCHMediaSidsCompletion definition. This intermittent issue results in infinite loading of attachments.

Debug Logs:

Debug logs are unavailable due to the rare scenario of this issue.

@berkus
Copy link
Contributor

berkus commented Apr 3, 2024

Thanks, will take a look at this.

Are you sure the client itself is not shutdown/disconnected while you're waiting for this response? I believe the callbacks might get dropped and not invoked if the client was shut down.

@kuchmiyalex
Copy link
Author

@berkus thank you.
Yes, I'm sure that the client is still connected state and even responds to fetching messages in the same conversation.

@kuchmiyalex
Copy link
Author

@berkus hey, is there any update regarding this issue?

@berkus
Copy link
Contributor

berkus commented May 14, 2024

@kuchmiyalex not really, I'm not in Twilio anymore, but @AlejandroOrozco should be able to assist.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:bug disposition:triage The bug requires triage
Projects
None yet
Development

No branches or pull requests

2 participants