[Android][0.84.1] TouchableOpacity only receives onPress on text area after disabled-to-enabled transition
还没有人认领这个 Issue。
- 主要语言
- C++
- 星标
- 127k
- 派生
- 25.3k
- 平均合并
- 1 天 23 小时
- 30 天内合并 PR
- 4
描述
Description
TouchableOpacity only receives onPress on text area after disabled-to-enabled transition
Description
After upgrading from React Native 0.81.3 to 0.84.1, in one custom button component (TouchableOpacity enabled only when disabled is false), button becomes partially non-interactive on Android.
The button works as expected when initially disabled.
After filling inputs and the button becomes enabled, only the <Text> area inside the button is clickable.
The rest of the button area (left/right empty space / padded area) does not trigger onPress.
This did not happen in RN 0.81.3.
I could not reproduce this behavior in Expo Snack. This appears to be tied to our native app codepath in 0.84.1.
Expected behavior:
Full button area should be tappable when enabled (same as 0.81.3), not just text area.
Actual behavior:
After enabled state transition, tap target is reduced to the text node area.
Affected Platforms
Android (emulator and physical device).
Steps to reproduce
Steps to reproduce
- Render a button that conditionally renders:
- disabled/loading:
<View ...>{...button content...}</View> - enabled:
<TouchableOpacity ...>{...same content...}</TouchableOpacity>
- disabled/loading:
- Include non-text areas in content (for example
leftComponentand/orrightComponent), not only text. - Start with disabled = true.
- Enter input values so button becomes enabled.
- On Android, tap multiple times on text area and on left/right empty areas.
- Observe: only text area fires
onPress, non-text areas do not.
React Native Version
0.84.1
Affected Platforms
Runtime - Android
Output of npx @react-native-community/cli info
System:
OS: macOS 26.4.1
CPU: (11) arm64 Apple M3 Pro
Memory: 426.92 MB / 36.00 GB
Shell:
version: "5.9"
path: /bin/zsh
Binaries:
Node:
version: 25.9.0
path: ~/.nvm/versions/node/v25.9.0/bin/node
Yarn:
version: 1.22.22
path: /opt/homebrew/bin/yarn
npm:
version: 11.12.1
path: ~/.nvm/versions/node/v25.9.0/bin/npm
Watchman:
version: 2024.12.02.00
path: /opt/homebrew/bin/watchman
Managers:
CocoaPods:
version: 1.16.2
path: /Users/--/.rbenv/shims/pod
SDKs:
iOS SDK:
Platforms:
- DriverKit 25.2
- iOS 26.2
- macOS 26.2
- tvOS 26.2
- visionOS 26.2
- watchOS 26.2
Android SDK:
API Levels:
- "28"
- "31"
- "35"
- "36"
Build Tools:
- 30.0.2
- 34.0.0
- 35.0.0
- 36.0.0
System Images:
- android-33 | Google Play ARM 64 v8a
- android-35 | Google APIs ARM 64 v8a
- android-35 | Google Play ARM 64 v8a
- android-36 | Google Play ARM 64 v8a
Android NDK: Not Found
IDEs:
Android Studio: 2025.3 AI-253.32098.37.2534.15336583
Xcode:
version: 26.2/17C52
path: /usr/bin/xcodebuild
Languages:
Java:
version: 17.0.12
path: /usr/bin/javac
Ruby:
version: 2.7.5
path: /Users/--/.rbenv/shims/ruby
npmPackages:
"@react-native-community/cli":
installed: 20.1.0
wanted: 20.1.0
react:
installed: 19.2.3
wanted: 19.2.3
react-native:
installed: 0.84.1
wanted: 0.84.1
react-native-macos: Not Found
npmGlobalPackages:
"*react-native*": Not Found
Android:
hermesEnabled: true
newArchEnabled: true
iOS:
hermesEnabled: true
newArchEnabled: true
Stacktrace or Logs
No crash. No stacktrace. Pure touch/interaction issue.
MANDATORY Reproducer
https://snack.expo.dev/@zehragunes/awkward-orange-soylent
Screenshots and Videos
https://github.com/user-attachments/assets/4749df92-3ae6-4a00-abec-3022b286b8e6
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
从 TouchableOpacity 的 Android 触摸处理路径开始,使用 issue 中链接的组件模式和必需的 Expo Snack,复现从禁用到启用的转换。比较 React Native 0.81.3 和 0.84.1 之间的行为,包括点击文本以及左右带 padding 的区域;完成标准是整个启用后的按钮区域都会触发 onPress。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- android, react-native
- 领域
- mobile
- Issue 类型
- 缺陷
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 冷清
- 描述清晰度
- 基本清楚
- 新手友好度
- 45/100