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] On the Android side, some accounts are consistently failing when calling the login interface, causing database errors. These accounts were able to log in normally previously. This issue is constantly reproducible on version 3.5.1. #541

Open
7msunshine opened this issue May 14, 2024 · 2 comments
Labels
bug Categorizes issue or PR as related to a bug.

Comments

@7msunshine
Copy link

OpenIM Server Version

3.5.1

Operating System and CPU Architecture

macOS (ARM)

Deployment Method

Source Code Deployment

Bug Description and Steps to Reproduce

Initially, with SDK version 3.2.0, the issue was recurrent with each login attempt and no unique characteristics of these problem accounts were flagged. After upgrading to version 3.5.1, the same issue persisted and the errors were consistent. It is unclear what may have caused this and how to troubleshoot it. There are tables in the cache database, but the user data is not comprehensive. What could possibly be causing this and how should I go about investigating? ErrorInfo: code:10005 error:error *errors.withStack not implement CodeError: init database ==> open_im_sdk/pkg/db.NewDataBase()@107: initDB failed /data/user/0/com.im.test/cache: index index_recv_id already exists: 10006 SdkInternalError

Screenshots Link

521715667911_ pic
531715667913_ pic

@7msunshine 7msunshine added the bug Categorizes issue or PR as related to a bug. label May 14, 2024
@kubbot
Copy link
Contributor

kubbot commented Jul 13, 2024

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@kubbot kubbot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 13, 2024
@kubbot
Copy link
Contributor

kubbot commented Jul 20, 2024

This issue was closed because it has been stalled for 7 days with no activity.

@kubbot kubbot closed this as completed Jul 20, 2024
@github-actions github-actions bot reopened this Aug 8, 2024
@mo3et mo3et removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 8, 2024
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

No branches or pull requests

3 participants