openimsdk / openimsdk/open-im-sdk-reactnative
[BUG] Application crash
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 58
- Forks
- 69
- PR merge metrics
- No merged PRs in 30d
Description
OpenIM Server Version
3.8.2
Operating System and CPU Architecture
Linux (ARM)
Deployment Method
Docker Deployment
Bug Description and Steps to Reproduce
Last Exception Backtrace:
0 CoreFoundation 0x1804ae0ec __exceptionPreprocess + 160
1 libobjc.A.dylib 0x180087db4 objc_exception_throw + 56
2 Foundation 0x180d1718c -[NSMutableDictionary(NSMutableDictionary) classForCoder] + 0
3 myAPP.debug.dylib 0x10bb47e38 -[RCTEventEmitter sendEventWithName:body:] + 372 (RCTEventEmitter.m:45)
4 myAPP.debug.dylib 0x10c34b1a8 -[OpenIMSDKRN pushEvent:data:] + 96 (OpenImSdkRn.m:125)
5 myAPP.debug.dylib 0x10c357c1c -[OpenIMSDKRN onConnecting] + 44 (OpenImSdkRn.m:1248)
调用路径：
OpenIMSDKRN onConnecting 触发
调用 pushEvent:data:
最终传递到 RCTEventEmitter sendEventWithName:body:
发生崩溃
Screenshots Link
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with OpenImSdkRn.m at pushEvent:data: (line 125) and onConnecting (line 1248), then inspect React Native's RCTEventEmitter sendEventWithName:body: at RCTEventEmitter.m:45. Reproduce the onConnecting path on the reported environment and determine what input causes the crash; done means this path no longer crashes and the relevant behavior is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- objective-c, react-native
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100