pusher / pusher/pusher-websocket-react-native
axios, react-query stop working in production
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 76
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
Description
After removing the initialization of Pusher in our production React Native application, we noticed that all fetch operations are being triggered unexpectedly. Unfortunately, we are not receiving any logs in Sentry to help us identify the issue.
Interestingly, in development mode, Pusher works fine alongside Axios and React Query. Could you provide guidance on why this might be happening and how we can resolve the issue?
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
No files, tests, or entry points are identified. Start by reproducing the production React Native behavior around Pusher initialization and the fetch calls, then compare it with development mode and inspect why Sentry records no error. Done means identifying the production-only cause and confirming that Axios and React Query requests behave normally after the fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100