microsoft / microsoft/react-native-windows

Crash when overwriting selected text in <TextInput/> with Japanese IME

Open
#16,088 0 comments 0 reactions 1 assignee View on GitHub

@protikbiswas100 is already working on this.

Since May 12, 2026.

bug Release0.85
Dominant language
C++
Stars
17.3k
Forks
1.2k
Avg merge
1d 13h
Merged PRs (30d)
33

Description

Problem Description

Selecting text that includes Japanese characters displayed in , turning on the Japanese IME, and typing any character causes an immediate crash.

Steps To Reproduce
  1. Type into the TextInput
  2. Select text that includes Japanese characters
  3. Turn on Japanese IME
  4. Type a single character
  5. The app crashes with the following log: INFO Connection established to app='TextInputCrash_1.0.0.0_x64__2f65sjwpnhfvw' on device='TowerPC'.
    I tried both Copilot Keyboard and Microsoft IME, but both showed the same behavior.
Selected text IME Result
Japanese text IME on Crash
Japanese text IME off Works
English text IME on Works
English text IME off Works

https://github.com/user-attachments/assets/d22f1f6b-9306-4216-bf64-962e2b65b5cc

Expected Results

No response

CLI version

20.0.0

Environment
> npx @react-native-community/cli info
info Fetching system and libraries information...
System:
  OS: Windows 11 10.0.26200
  CPU: (12) x64 Intel(R) Core(TM) i5-10500 CPU @ 3.10GHz
  Memory: 12.86 GB / 31.85 GB
Binaries:
  Node:
    version: 24.14.1
    path: C:\Program Files\nodejs\node.EXE
  Yarn:
    version: 1.22.22
    path: C:\Program Files (x86)\Yarn\bin\yarn.CMD
  npm:
    version: 11.11.0
    path: C:\Program Files\nodejs\npm.CMD
  Watchman: Not Found
SDKs:
  Android SDK: Not Found
  Windows SDK:
    AllowDevelopmentWithoutDevLicense: Enabled
    Versions:
      - 10.0.22621.0
      - 10.0.26100.0
IDEs:
  Android Studio: Not Found
  Visual Studio:
    - 17.14.37216.2 (Visual Studio Community 2022)
Languages:
  Java:
    version: 21.0.10
    path: C:\Program Files\Microsoft\jdk-21.0.10.7-hotspot\bin\javac.EXE
  Ruby: Not Found
npmPackages:
  "@react-native-community/cli":
    installed: 20.0.0
    wanted: 20.0.0
  react:
    installed: 19.1.1
    wanted: 19.1.1
  react-native:
    installed: 0.82.0
    wanted: 0.82.0
  react-native-windows:
    installed: 0.82.5
    wanted: ^0.82.5
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: true
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found

info React Native v0.85.3 is now available (your project is running on v0.82.0).
info Changelog: https://github.com/facebook/react-native/releases/tag/v0.85.3
info Diff: https://react-native-community.github.io/upgrade-helper/?from=0.82.0&to=0.85.3
info For more info, check out "https://reactnative.dev/docs/upgrading?os=windows".
Community Modules
  "dependencies": {
    "@react-native/new-app-screen": "0.82.0",
    "react": "19.1.1",
    "react-native": "0.82.0",
    "react-native-safe-area-context": "^5.5.2",
    "react-native-windows": "^0.82.5"
  },
Target React Native Architecture

New Architecture (WinAppSDK) Only

Target Platform Version

10.0.22621

Visual Studio Version

Visual Studio 2022

Build Configuration

Debug

Snack, code example, screenshot, or link to a repository

Minimal reproducible example:

import React, { useState } from 'react';
import { TextInput, View } from 'react-native';
import { SafeAreaView } from 'react-native-safe-area-context';
const SEED = '日本語テキスト';

export default function App() {
  const [text, setText] = useState(SEED);
  return (
    <SafeAreaView>
      <View>
        <TextInput
          value={text}
          onChangeText={t => {
            setText(t);
          }}
          autoCorrect={false}
        />
      </View>
    </SafeAreaView>
  );
}

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.