Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[iOS] Focused TextInput keeps focus and keyboard after switching pages (v9)

Abierto
  • ¿Algo no está bien?
#1,192 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@TaduJR ya está trabajando en esto.

Desde el 19/10/2026.

  • #1193 de @TaduJR — abierto

Evaluación

Dificultad
4/5
Tiempo estimado
1-2 días
Aptitud para principiantes
69/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
ios, react-native, swift, typescript
Área
frontend, mobile

Línea de trabajo

Start at the iOS PagerViewProvider path that forwards onPageSelected and inspect how it handles focus when the selected page changes. Compare with the Android fix in #1155, which clears focus outside the selected page and hides the keyboard. Reproduce with the provided two-page TextInput example using setPage and a swipe; done when leaving a page blurs its input and the keyboard follows.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Environment

  • react-native-pager-view: 9.0.9 (also present in 9.0.8)
  • React Native: 0.88, New Architecture
  • Xcode 27, iOS 27.0 simulator (iPhone 18 Pro)
  • iOS only. The Android half of this was fixed in #1155 and shipped in 9.0.8.

Description

This is the iOS half of #1154, which was fixed for Android only.

A TextInput that's focused on one page stays focused after you switch to another page, whether with setPage or a swipe. The keyboard stays open, nothing on the page you land on is focused, and typing still goes into the input that's now off-screen, so the user edits a field they can't see.

The iOS implementation never touches focus. PagerViewProvider forwards onPageSelected and leaves the first responder alone, and SwiftUI's paged TabView keeps the neighbouring pages in the view hierarchy, so the input that was left behind holds the first responder and the keyboard with it.

keyboardDismissMode doesn't cover this. It defaults to none, and even on-drag only reacts to a drag, so setPage never dismisses. Dismissing the keyboard is also not the same as blurring, which is what leaves keystrokes going into the off-screen field.

Android behaved the same way until #1155, which clears focus held outside the selected page when a page is selected, and hides the keyboard explicitly. The two platforms disagree today: the same code blurs on Android 9.0.8 and keeps focus on iOS.

Expected: leaving a page blurs an input focused on it and the keyboard follows, as it now does on Android.
Actual: the input keeps focus, the keyboard stays open, and keystrokes go to the off-screen page.

Here is the moment it goes wrong, with a status line showing the selected page, the focused input and the keyboard: the pager is on page 0, while page 1's input still holds focus and the keyboard.

Image

Found in Expensify/App#101157, where a pager hosts a form on each tab.

Reproducible Demo

import { useRef } from 'react';
import { Button, StyleSheet, TextInput, View } from 'react-native';
import PagerView from 'react-native-pager-view';

export function Repro() {
  const ref = useRef<PagerView>(null);

  return (
    <PagerView ref={ref} style={StyleSheet.absoluteFill} initialPage={0}>
      {[0, 1].map((page) => (
        <View key={page} style={{ flex: 1, padding: 24, gap: 12 }}>
          <TextInput placeholder={`Input ${page}`} style={{ borderWidth: 1, padding: 12 }} />
          <Button title={`Go to page ${1 - page}`} onPress={() => ref.current?.setPage(1 - page)} />
        </View>
      ))}
    </PagerView>
  );
}
  1. Focus Input 1 on page 1 and wait for the keyboard.
  2. Tap Go to page 0, or swipe back to page 0.
  3. Type.

The keyboard never closes, and the characters land in Input 1 while page 0 is on screen. Swipe back and you'll find the text in the input you couldn't see.

Lenguaje dominante
TypeScript
Estrellas
3.4k
Forks
485
Merge medio
2 d 11 h
PR fusionados (30 d)
26

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de callstack/react-native-pager-view

Todos los issues de callstack/react-native-pager-view

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.