t4t5/react-native-router

undefined is not an object (evaluating 'this.refs[UNDERLAY_REF].setNativeProps')

Open

#32 opened on Jun 7, 2015

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (1,174 stars) (163 forks)batch import
help wanted

Description

Odd bug, I'm getting this error after spamming the router forward and back.

2015-06-07 15:53:43.681 [error][tid:com.facebook.React.JavaScript] "Error: Touchable cannot transition from `RESPONDER_INACTIVE_PRESS_IN` to `LONG_PRESS_DETECTED` for responder `.r[1]{TOP_LEVEL}[0].0.0.0.1.1.0.0`
 stack: 
  _receiveSignal          index.ios.bundle:32990
  _handleLongDelay        index.ios.bundle:32969
  <unknown>               index.ios.bundle:8186
  callTimer               index.ios.bundle:7974
  callTimers              index.ios.bundle:7997
  jsCall                  index.ios.bundle:7423
  _callFunction           index.ios.bundle:7686
  <unknown>               index.ios.bundle:7713
  <unknown>               index.ios.bundle:7707
  perform                 index.ios.bundle:6221
  batchedUpdates          index.ios.bundle:14065
  batchedUpdates          index.ios.bundle:4753
  <unknown>               index.ios.bundle:7706
  applyWithErrorReporter  index.ios.bundle:7458
  guardReturn             index.ios.bundle:7480
  processBatch            index.ios.bundle:7705
 URL: http://localhost:8081/index.ios.bundle
 line: 32993
 message: Touchable cannot transition from `RESPONDER_INACTIVE_PRESS_IN` to `LONG_PRESS_DETECTED` for responder `.r[1]{TOP_LEVEL}[0].0.0.0.1.1.0.0`"

is anyone else experiencing this.

Contributor guide

Tech stack
javascriptreactreact native
Domain
mobile
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Understanding of React Native touch responder systemBasic knowledge of routing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
The issue involves a crash when spamming forward/back navigation, resulting in an invalid state transition in Touchable. Investigate the touch responder logic in react native router, particularly the transition from RESPONDER INACTIVE PRESS IN to LONG PRESS DETECTED. Look at the source code for handling rapid navigation and see if there is a race condition or missing state cleanup. Consider reproducing with a minimal example and reviewing related issues or PRs.