renderBottomAccessoryView crashes on iOS 26: RCTBottomAccessoryComponentView does not initialize _props in its constructor
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 1/5
- Tempo stimato
- Meno di un'ora
- Idoneità per principianti
- 92/100
- Tipo di issue
- Bug
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- ios, objective-c, react-native
Direzione di ricerca
Inizia da ios/RCTBottomAccessoryComponentView.mm e confronta la configurazione di initWithFrame: con RCTTabViewComponentView.mm, che l’issue indica come esempio funzionante. Assegna i defaultProps esistenti a _props, quindi compila ed esegui l’esempio fornito su iOS 26 in modalità Debug con renderBottomAccessoryView; il lavoro è concluso quando l’accessorio viene montato senza assertion e appare sopra la barra delle schede.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Before submitting a new issue
- I tested using the latest version of the library, as the bug might be already fixed.
- I tested using a supported version of react native.
- I checked for possible duplicate issues, with possible answers.
Bug summary
Description
Using the iOS 26 bottom accessory feature (renderBottomAccessoryView) crashes the app
immediately on first render:
Thread 1: "`RCTViewComponentView` subclasses (and `RCTBottomAccessoryComponentView`
particularly) must setup `_props` instance variable with a default value in the constructor."
Removing renderBottomAccessoryView makes the app run normally, so the crash is specific to
the accessory component view.
Library version
1.5.0
Environment info
info Fetching system and libraries information...
System:
OS: macOS 26.5.2
CPU: (10) arm64 Apple M4
Memory: 87.67 MB / 24.00 GB
Shell:
version: "5.9"
path: /bin/zsh
Binaries:
Node:
version: 24.18.0
path: /var/folders/lt/t4vyv6s110d1p6mg8_fwsd9h0000gn/T/yarn--1793087516853-0.2936365526559257/node
Yarn:
version: 1.22.22
path: /var/folders/lt/t4vyv6s110d1p6mg8_fwsd9h0000gn/T/yarn--1793087516853-0.2936365526559257/yarn
npm:
version: 11.16.0
path: /Users/munitcat/.vfox/sdks/nodejs/bin/npm
Watchman:
version: 2026.07.20.00
path: /opt/homebrew/bin/watchman
Managers:
CocoaPods:
version: 1.17.0
path: /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms:
- DriverKit 25.5
- iOS 26.5
- macOS 26.5
- tvOS 26.5
- visionOS 26.5
- watchOS 26.5
Android SDK: Not Found
IDEs:
Android Studio: 2026.1 AI-261.25134.95.2612.15822958
Xcode:
version: 26.6/17F113
path: /usr/bin/xcodebuild
Languages:
Java:
version: 17.0.18
path: /usr/bin/javac
Ruby:
version: 4.0.6
path: /opt/homebrew/bin/ruby
npmPackages:
"@react-native-community/cli":
installed: 20.2.0
wanted: 20.2.0
react:
installed: 19.3.0
wanted: 19.3.0
react-native:
installed: 0.88.0
wanted: 0.88.0
react-native-macos: Not Found
npmGlobalPackages:
"*react-native*": Not Found
Android:
hermesEnabled: true
newArchEnabled: true
iOS:
hermesEnabled: true
newArchEnabled: true
Steps to reproduce
Root cause
ios/RCTBottomAccessoryComponentView.mm — initWithFrame: creates defaultProps but never
assigns it to the _props ivar:
- (instancetype)initWithFrame:(CGRect)frame
{
if (self = [super initWithFrame:frame]) {
static const auto defaultProps = std::make_shared<const BottomAccessoryViewProps>();
if (@available(iOS 26.0, *)) { // <-- defaultProps is never used
bottomAccessoryProvider = [[BottomAccessoryProvider alloc] initWithDelegate:self];
}
}
return self;
}
RCTViewComponentView (react-native 0.88.0,
React/Fabric/Mounting/ComponentViews/View/RCTViewComponentView.mm:137) initializes the ivar
with plain ViewProps:
_props = ViewShadowNode::defaultSharedProps();
and then asserts in updateProps:oldProps: (line 333–346) that every subclass replaces it with
its own props type:
RCTAssert(
propsRawPtr &&
([self class] == [RCTViewComponentView class] ||
typeid(*propsRawPtr).hash_code() != typeid(const ViewProps).hash_code()),
@"`RCTViewComponentView` subclasses (and `%@` particularly) must setup `_props`"
" instance variable with a default value in the constructor.",
NSStringFromClass([self class]));
Because RCTBottomAccessoryComponentView never overrides _props, typeid(*_props) is still
ViewProps and the assertion fires.
For comparison, RCTTabViewComponentView.mm does it correctly in the same constructor:
static const auto defaultProps = std::make_shared<const RNCTabViewProps>();
...
self.contentView = _tabViewProvider;
_props = defaultProps; // <-- this line is missing in the accessory view
Fix
One line, in ios/RCTBottomAccessoryComponentView.mm:
if (self = [super initWithFrame:frame]) {
static const auto defaultProps = std::make_shared<const BottomAccessoryViewProps>();
+ _props = defaultProps;
if (@available(iOS 26.0, *)) {
This also silences the unused variable 'defaultProps' compiler warning.
Scope / notes
- Only affects builds with the New Architecture, as the file is wrapped in
#ifdef RCT_NEW_ARCH_ENABLED. - Only triggered when
renderBottomAccessoryViewis provided and
Platform.Version >= 26— that is the only path whereBottomAccessoryViewis mounted
(src/TabView.tsx, around line 522). - Debug only. The assertion sits inside
#ifndef NS_BLOCK_ASSERTIONS, so it is compiled
out in Release. Release builds don't crash, but the component view keeps running on the
baseViewPropsinstead of its own props type.
Workaround
Until a release with the fix is out, apply the patch through patch-package:
npm i -D patch-package
npx patch-package react-native-bottom-tabs
and add "postinstall": "patch-package" to package.json.
The generated patch is attached below.
diff --git a/node_modules/react-native-bottom-tabs/ios/RCTBottomAccessoryComponentView.mm b/node_modules/react-native-bottom-tabs/ios/RCTBottomAccessoryComponentView.mm
--- a/node_modules/react-native-bottom-tabs/ios/RCTBottomAccessoryComponentView.mm
+++ b/node_modules/react-native-bottom-tabs/ios/RCTBottomAccessoryComponentView.mm
@@ -40,6 +40,7 @@ - (instancetype)initWithFrame:(CGRect)frame
{
if (self = [super initWithFrame:frame]) {
static const auto defaultProps = std::make_shared<const BottomAccessoryViewProps>();
+ _props = defaultProps;
if (@available(iOS 26.0, *)) {
#if SWIFT_PACKAGE
bottomAccessoryProvider = RNCCreateBottomAccessoryProvider(self);
Alternatively, simply do not pass renderBottomAccessoryView — the tab bar itself works fine
without it.
Reproducible sample code
## Steps to reproduce
import TabView from 'react-native-bottom-tabs';
const routes = [
{ key: 'home', title: 'Home', focusedIcon: { sfSymbol: 'house.fill' } },
];
<TabView
navigationState={{ index: 0, routes }}
renderScene={() => <View />}
onIndexChange={() => {}}
renderBottomAccessoryView={() => <View style={{ height: 44 }} />}
/>
Run on an **iOS 26** device or simulator in **Debug**. The app crashes while mounting the
`BottomAccessoryView` component.Expected
The bottom accessory renders above the tab bar.
- Lingua principale
- TypeScript
- Stelle
- 1.5k
- Fork
- 111
- Merge medio
- 2g 1h
- PR unite (30g)
- 6
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di callstack/react-native-bottom-tabs
-
[iOS] Fabric: SIGABRT on tab press when tab key contains non-ASCII characters (kCFStringEncodingUTF8 passed to -cStringUsingEncoding:)Forse già presa @thiagobrez l’ha presa 64 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
callstack/react-native-bottom-tabs#560 ·
I maintainer di solito rispondono entro 1 giorno
-
[iOS] Tabs don't fire tabLongPress event on iOS 26Forse già presa @thiagobrez l’ha presa 38 giorni fa. Apertabug
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
callstack/react-native-bottom-tabs#573 ·
I maintainer di solito rispondono entro 1 giorno
-
iOS: allow opting out of the private-CoreSVG SVG decoder (exclude_files by default, or an opt-in flag)Forse già presa @oleksandrzavarzin-callstack l’ha presa 5 giorni fa. Aperta
Difficoltà 3/5 1-2 giorni Idoneità per principianti 68/100
callstack/react-native-bottom-tabs#565 ·
I maintainer di solito rispondono entro 1 giorno
-
Tab icon size is hard-coded to 27x27pt with no way to override itForse già presa @thiagobrez l’ha presa 65 giorni fa. Aperta
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
callstack/react-native-bottom-tabs#561 · 1 commento · 2 reazioni ·
I maintainer di solito rispondono entro 1 giorno
-
[Android] Content doesn't resize when tab bar visibility changes (tabBarHidden)Forse già presa @JJalit l’ha presa 98 giorni fa. Aperta
Difficoltà 3/5 1-2 giorni Idoneità per principianti 35/100
callstack/react-native-bottom-tabs#557 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di callstack/react-native-bottom-tabs
Issue simili
-
e2e-failure ready-to-code
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 82/100
redhat-developer/rhdh-plugin-export-overlays#4616 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
I maintainer di solito rispondono entro 1 giorno
-
ai-handle
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
nextlevelbuilder/dewee-web-v2#73 ·
I maintainer di solito rispondono entro 1 giorno
-
backend bug good first issue
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
PoCInnovation/Distribox#255 ·
I maintainer di solito rispondono entro 1 giorno