iOS 27 SDK: tab titles and icons land on the wrong tabs when one tab has role "search"
まだ誰も着手していません。
評価
- 難易度
- 3/5
- 見積もり時間
- 1〜2日
- 初心者へのやさしさ
- 72/100
- issue の種類
- バグ
- 明瞭さ
- 明確に書かれている
- 活発さ
- 活発
- 技術スタック
- ios, react-native, swift, typescript
- 領域
- mobile
調査の方向性
Start in ios/TabViewImpl.swift, at configureTabBarItemImages, and compare the tab bar item's display order with the declared tab order under the iOS 27 SDK. The issue suggests matching items by identity and falling back to position when tabs are unavailable. Reproduce with four tabs, with Search second and role search; done when labels, icons, and selected screens correspond on iOS 27 while the existing fallback remains.
索引モデルが issue の本文から書いたものです。
説明
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
When the app is built with Xcode 27 (iOS 27 SDK), every tab after a tab with role: "search" shows the title and icon of its neighbour. Selection still works by index, so the bar looks plausible, but pressing a tab opens a different screen than its label says. The same source built with Xcode 26 is fine.
In my case with four tabs declared as Home, Search (role: "search"), Favorites, Library, the bar shows Home, Favorites, Library, Search. Pressing "Library" opens Search and pressing "Search" opens Favorites.
Cause
Linked against the iOS 27 SDK, UITabBar.items is returned in display order, and a tab with the search role is displayed last. UITabBarController.tabs keeps the declaration order.
configureTabBarItemImages in ios/TabViewImpl.swift assigns title and image by the item's position:
for (tabBarIndex, item) in items.enumerated() {
guard let tabData = props.filteredItems[safe: tabBarIndex] else { continue }
So the item at display position 1 (Favorites) receives the data of declared tab 1 (Search), and so on. This is still the case on main (b044dbd5).
Suggested fix
Match the item to its tab by identity instead of by position, and fall back to the position where tabs is not available:
private func declarationIndex(of item: UITabBarItem, at tabBarIndex: Int, in tabBar: UITabBar) -> Int {
if #available(iOS 18.0, tvOS 18.0, visionOS 2.0, *),
let tabController = tabBar.delegate as? UITabBarController,
let index = tabController.tabs.firstIndex(where: { $0.viewController?.tabBarItem === item })
{
return index
}
return tabBarIndex
}
We run this as a patch on 1.4.0 and it restores the right labels: https://github.com/streamyfin/streamyfin/pull/2196. Happy to open a PR here.
Related: #590 and #588 touch the same function.
Library version
1.4.0
Environment info
System:
OS: macOS 26.6.2
CPU: (11) arm64 Apple M3 Pro
SDKs:
iOS SDK:
Platforms:
- iOS 27.0
- tvOS 27.0
IDEs:
Xcode:
version: 27.0/27A266a
Languages:
Swift: 6.4
npmPackages:
react:
installed: 19.2.3
react-native-tvos:
installed: 0.86.0-2
react-native-bottom-tabs: 1.4.0
"@bottom-tabs/react-navigation": 1.4.0
"@react-navigation/native": 7.3.17
expo: 57.0.25
iOS:
hermesEnabled: true
newArchEnabled: true
Steps to reproduce
iOS only. Seen on a physical iPhone 17 Pro and on the iOS 27.0 simulator (iPhone 18 Pro).
- Declare four tabs, the second one with
role: "search"(sample below). - Build and run with Xcode 27.0 (iOS 27 SDK).
- Look at the tab bar: it reads Home, Favorites, Library, Search.
- Press "Library": the Search screen opens. Press "Search": the Favorites screen opens.
- Build the same source with Xcode 26: labels and screens match.
Reproducible sample code
// Mirrors the tab setup in our app (https://github.com/streamyfin/streamyfin).
// Not run standalone: the bug was observed in the app itself.
import * as React from 'react';
import { Text, View } from 'react-native';
import { NavigationContainer } from '@react-navigation/native';
import { createNativeBottomTabNavigator } from '@bottom-tabs/react-navigation';
const Tab = createNativeBottomTabNavigator();
const screen = (label) => () => (
<View style={{ flex: 1, justifyContent: 'center', alignItems: 'center' }}>
<Text>{label}</Text>
</View>
);
const Home = screen('Home screen');
const Search = screen('Search screen');
const Favorites = screen('Favorites screen');
const Library = screen('Library screen');
export default function App() {
return (
<NavigationContainer>
<Tab.Navigator>
<Tab.Screen
name="Home"
component={Home}
options={{ tabBarIcon: () => ({ sfSymbol: 'house.fill' }) }}
/>
<Tab.Screen
name="Search"
component={Search}
options={{
role: 'search',
tabBarIcon: () => ({ sfSymbol: 'magnifyingglass' }),
}}
/>
<Tab.Screen
name="Favorites"
component={Favorites}
options={{ tabBarIcon: () => ({ sfSymbol: 'heart.fill' }) }}
/>
<Tab.Screen
name="Library"
component={Library}
options={{ tabBarIcon: () => ({ sfSymbol: 'rectangle.stack.fill' }) }}
/>
</Tab.Navigator>
</NavigationContainer>
);
}
- 主要言語
- TypeScript
- スター
- 1.5k
- フォーク
- 110
- 平均マージ
- 2日 18時間
- マージ済み PR(30日)
- 2
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
callstack/react-native-bottom-tabs のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 75/100
-
[iOS] Fabric: SIGABRT on tab press when tab key contains non-ASCII characters (kCFStringEncodingUTF8 passed to -cStringUsingEncoding:)対応中かも @thiagobrez が 50 日前に担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 75/100
-
難易度 4/5 3〜5日 初心者へのやさしさ 48/100
-
難易度 4/5 3〜5日 初心者へのやさしさ 68/100
callstack/react-native-bottom-tabs#591 · コメント 1 件 ·
-
難易度 4/5 3〜5日 初心者へのやさしさ 58/100
callstack/react-native-bottom-tabs の issue をすべて見る
似ている issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
wormhole-foundation/wormhole#5062 ·
メンテナーはふだん 1 日以内に返信
-
internal os specific
難易度 2/5 1〜3時間 初心者へのやさしさ 65/100
frostney/GocciaScript#1688 ·
メンテナーはふだん 1 日以内に返信
-
integration:hermes
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100
vectorize-io/hindsight#5592 ·
メンテナーはふだん 1 日以内に返信
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
vercel/streamdown#673 · リアクション 1 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 74/100
apache/rocketmq-dashboard#6712 ·
メンテナーはふだん 3 日以内に返信