pusher / pusher/pusher-websocket-react-native

java.lang.NullPointerException (crashed) Attempt to invoke interface method 'j9.l j9.d.a()' on a null object reference

Open
#178 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
76
Forks
64
PR merge metrics
No merged PRs in 30d

Description

Thread Name: java.lang.NullPointerException
com.pusherwebsocketreactnative.PusherWebsocketReactNativeModule.onUsersInformationReceived (SourceFile:252)
com.pusher.client.channel.impl.PresenceChannelImpl.handleSubscriptionSuccessfulMessage (SourceFile:139)
com.pusher.client.channel.impl.PresenceChannelImpl.handleEvent (SourceFile:65)
com.pusher.client.channel.impl.ChannelManager.handleEvent (SourceFile:107)
com.pusher.client.Pusher.handleEvent (SourceFile:113)
i9.Pusher.$r8$lambda$TWYdWxRCGuS7ssoOIQnuG4PN_VQ (SourceFile:1)
i9.Pusher$$ExternalSyntheticLambda0.accept (SourceFile:1)
com.pusher.client.connection.websocket.WebSocketConnection.handleEvent (SourceFile:165)
com.pusher.client.connection.websocket.WebSocketConnection.lambda$onMessage$5 (SourceFile:216)
n9.WebSocketConnection.$r8$lambda$EqRAXtDRgh8La_NaJvaG4CC7s9w (SourceFile:1)
n9.WebSocketConnection$$ExternalSyntheticLambda3.run (SourceFile:1)
com.pusher.client.util.Factory.lambda$queueOnEventThread$0 (SourceFile:140)
r9.Factory.$r8$lambda$aq1T3oNG7kKIxabI0tgUB4UDBns (SourceFile:1)
r9.Factory$$ExternalSyntheticLambda0.run (SourceFile:1)
java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1137)
java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:637)
java.lang.Thread.run (Thread.java:1012)

react-native: 0.75.4,
@pusher/pusher-websocket-react-native: 1.3.1

Device - Samsung Galaxy S20 FE 5G
OS Version - 13

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with onUsersInformationReceived at SourceFile:252 and trace the subscription-success path through PresenceChannelImpl.handleSubscriptionSuccessfulMessage. Reproduce the crash using React Native 0.75.4 and @pusher/pusher-websocket-react-native 1.3.1 on the reported Android environment, then verify that the same presence event no longer crashes.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, react-native, typescript
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.