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] panic: runtime error: invalid memory address or nil pointer dereference #885

Closed
baguosiji opened this issue Mar 13, 2025 · 3 comments · Fixed by #889
Closed

[BUG] panic: runtime error: invalid memory address or nil pointer dereference #885

baguosiji opened this issue Mar 13, 2025 · 3 comments · Fixed by #889
Labels
bug Categorizes issue or PR as related to a bug.

Comments

@baguosiji
Copy link

OpenIM SDK Version

3.8.3

OpenIM Server Version

No response

SDK Platform

Electron FFI SDK

Device Model

MacBook Pro M3 pro

Operating System Version

15.3.2 (24D81

Bug Description and Steps to Reproduce

panic: runtime error: invalid memory address or nil pointer dereference

Screenshots Link

No response

@baguosiji baguosiji added the bug Categorizes issue or PR as related to a bug. label Mar 13, 2025
@baguosiji baguosiji changed the title [BUG] [BUG] panic: runtime error: invalid memory address or nil pointer dereference Mar 13, 2025
@baguosiji
Copy link
Author

Image 有人看看吗 更新了最新的macos 就出了这种问题

@OpenIM-Robot
Copy link

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


Image Does anyone have a look? This problem occurs after the latest macos is updated

@FGadvancer
Copy link
Member

Same issue, the SDK will include stricter protection logic to ensure that users are given the correct error code if they try to proceed without completing initSDK or login first. Please reference openimsdk/open-im-server#3027

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.

3 participants