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

[BUG] Android setMessageLocalEx Success, But Message.ex is null #878

Closed
wzJun1 opened this issue Mar 5, 2025 · 3 comments · Fixed by openimsdk/open-im-sdk-android#84
Closed
Labels
bug Categorizes issue or PR as related to a bug.

Comments

@wzJun1
Copy link

wzJun1 commented Mar 5, 2025

OpenIM SDK Version

3.8.3

OpenIM Server Version

3.8.3

SDK Platform

Android SDK

Device Model

ALL

Operating System Version

ALL

Bug Description and Steps to Reproduce

My message is a local message, which was inserted using insertSingleMessageToLocalStorage. Then I called setMessageLocalEx to modify ex, and the callback method indicated success. However, when I retrieved the Message from getAdvancedHistoryMessageList, I couldn't obtain this ex. I downloaded the SQLite DB and found that the chat record data table contains both ex and local_ex. The setMessageLocalEx method successfully set local_ex, but I couldn't find a way to get local_ex in the Android OpenIM SDK. I can only get ex, but it's null.

Screenshots Link

No response

@wzJun1 wzJun1 added the bug Categorizes issue or PR as related to a bug. label Mar 5, 2025
@wzJun1
Copy link
Author

wzJun1 commented Mar 5, 2025

I reviewed the source code of openim-sdk-core and found that the message structure includes localEx. So, I pulled down the source code of open-im-sdk-android, added localEx to the Message object, recompiled the aar, and placed it in the project. Now, I can obtain localEx. This should be considered a minor bug.

@FGadvancer
Copy link
Member

Based on your description, it seems that the Android SDK is missing this field, which is causing the retrieval to not work correctly. If confirmed, could you please submit a PR to this repository? Thank you for your contribution.

@wzJun1
Copy link
Author

wzJun1 commented Mar 6, 2025

PR #84

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants