Stream SDK 6.0.3 sending a new message with image or file attachments is not storing the message or its attachments #4973
Comments
|
Hi, sorry for the late reply - we are looking into it. |
|
Hello @SchramboVida On the logs, we can see the attachment is properly uploaded to your CDN, and a new attachment with the URL Could you provide us with the following logs after the attachment is uploaded? If you could replicate this error in our Sample App would be awesome, because it would help us to debug+fix it. I have been doing some tests with our Sample App and it seems to be working fine. |
|
Hi @JcMinarro, I've tried again using a stubbed-out uploader implementation as suggested which just returns success from the The failure occurs before any of the custom CDN uploader code executes, specifically in
Before That's strange because the
Interestingly, the failure result does not seem to propagate back to Look for the Thanks again for your help and please let me know if you have any questions! Best Regards, |
|
Hello @SchramboVida Thanks for your detailed reply. I will need more time to debug it properly and try to find why it is failing in your side. |
|
Hi @SchramboVida, One thing concerns me in your logs:
attachmentsSender
.sendAttachments(preparedMessage, channelType, channelId, isRetrying, repositoryFacade)
.also { result ->
debugger.onInterceptionStop(result)
}If |
|
Based on the logs it seems like this line does't suspend jobsMap[newMessage.id]?.join()Which makes me to believe that |
|
@SchramboVida were you able to solve the problem? |
|
Hello. I have encountered a similar trouble and conducted my own investigation and findings, so I would like to report them. (Please note that English is not my native language, so my expressions might not sound completely natural. 🙇 ) There seem to be two main issues causing this behavior. Issue 1:
|
|
@JcMinarro @kanat @DanielNovak My apologies for this very late reply, I fell ill shortly after my initial report, then once recovered was busy implementing other app features. Now that those tasks have been completed, I've had some time to continue debugging and have a much better understanding of the cause as well as a solution for your review and additional feedback. Problem SummaryAt the core of the problem we have The call to Here's our When the user sends a message with one or more attachments, a While the attachments are uploading, Here is the relevant section of our Note that the At this stage of uploading, the attachments have no SolutionTo make My ConcernsThe Can we trust that this internal Stream API and related dependencies on the Thanks! |
Hello @SchramboVida I just adapted our Sample App to use a custom Could you review this implementation and compare it with yours? |
|
This comment is very helpful for me. The problem summary is likely to be very similar to what I reported, but the solution is more appropriate and smart than my one.
I believe this is the essence of the problem. Without resolving it, even when implemented according to the documentation, it is not possible to upload files (even when using the default Stream CDN as I did). |
|
Ok. If the OfflinePlugin is not added during the configuration process, a Aren't you adding While we fix the issue when the |
|
Hi @JcMinarro, thanks for confirming what I suspected, that The documentation states this plugin is optional, and since our app does not work offline we chose to not include it. However, including it resolves the problem without my Thanks again for the help! |
The idea is |
|
I found that my problem was caused for the same reason. And I was able to solve it by using the offline plugin too. |
|
BTW. |
Describe the bug
Using Stream SDK
io.getstream:stream-chat-android-compose:6.0.3(we're upgrading from 5.17.10) we have theChatClientconfigured to use a custom CDN uploader via.fileUploader(ChatFileUploader()).Our implemention of
ChatFileUploader()which is a subclass ofio.getstream.chat.android.client.uploader.FileUploaderprovides the requiredsendImage(...)andsendFile(...)implementations and returns ags://schemed url that identifies the asset for subsequent access, for examplegs://vida-stream-attachments-test/7098a6a7-c47d-4d4c-b24e-9d6f7c8d8e7f/8e118e6f-48e8-4812-b8c0-74bcbf765ff7.quicktimeWe have custom image attachment composers that use the
gs://urls to obtain an authorization token that's needed to pull the actual image asset out of our CDN for viewing. All of this has been working perfectly up to SDK 5.17.10 but is not working at all in SDK 6.0.3 and we're a bit stumped why.SDK version
To Reproduce
Steps to reproduce the behavior:
ChatClientwith a custom uploader that returns a url-like string for the asset, e.g.io.getstream.result.Result.Success(UploadedImage(file = "gs://vida-stream-attachments-test/7098a6a7-c47d-4d4c-b24e-9d6f7c8d8e7f/8e118e6f-48e8-4812-b8c0-74bcbf765ff7.quicktime"))Expected behavior
The new message with freshly uploaded attachment should persist in the channel message list. The message should remain loadable via
chatClient.getMessage(messageId)and not return HTTP 400 not-found errors "Message with id *** doesn't exist".One thing that's a bit odd is the error string — when I search the SDK 6.0.3 sources for the error string, the closest I can find is in
io.getstream.chat.android.client.attachment.worker.UploadAttachmentsWorker.uploadAttachmentsForMessage(String)but that does not have the "doesn't" contraction visible in the error screen below, so I'm not sure this is actually the source of the error string.Device:
Screenshots
Debug log output (with comments)
The text was updated successfully, but these errors were encountered: