Text is not displayed on Android physical device after 0.73.0

[crawraps]

Description

Since version 0.73.0 text in the Text component is not displayed on a physical connected Android device.

It works well both on Android Studio Emulator (tested with API 33 and API 34) and on physical connected device with react native below 0.73.0

Tested on two different physical devices

If I add background color to it, Text component would be visible, but content is not. Also, text is visible in TextInput component. Text in error logs is not visible too, but visible in loading log (at the very top of the application)

Steps to reproduce

1. Install the application on physical Android device
2. Notice that any text in the Text component is not displayed

React Native Version

0.73.1

Affected Platforms

Runtime - Android

Output of npx react-native info

System:
  OS: Linux 6.6 Arch Linux
  CPU: (12) x64 AMD Ryzen 5 5600H with Radeon Graphics
  Memory: 3.57 GB / 14.98 GB
  Shell:
    version: "5.9"
    path: /usr/bin/zsh
Binaries:
  Node:
    version: 18.18.2
    path: ~/.local/nvm/versions/node/v18.18.2/bin/node
  Yarn: Not Found
  npm:
    version: 9.8.1
    path: ~/.local/nvm/versions/node/v18.18.2/bin/npm
  Watchman:
    version: 20231028.222255.0
    path: /usr/local/bin/watchman
SDKs:
  Android SDK: Not Found
IDEs:
  Android Studio: Not Found
Languages:
  Java:
    version: 17.0.9
    path: /home/crawraps/.local/sdkman/candidates/java/current/bin/javac
  Ruby: Not Found
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.73.1
    wanted: 0.73.1
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: Not found
  newArchEnabled: false

### Stacktrace or Logs

```text
-

Reproducer

https://github.com/crawraps/reproducer

Screenshots and Videos

initial react native reproducer template

[cortinico]

Install the application on physical Android device

Which device are you using?

[crawraps]

Install the application on physical Android device

Which device are you using?

OnePlus 9RT with custom rom riceDroid-13.0
Also tested on Pixel 7 and get same behaviour

[cortinico]

That's a screenshot from a Pixel 3 (physical device):

I cannot reproduce what you're reporting @crawraps

[github-actions]

⚠️	Missing Reproducible Example
ℹ️	We could not detect a reproducible example in your issue report. Please provide either: If your bug is UI related: a Snack If your bug is build/update related: use our Reproducer Template

[cetfu]

Tested on Pixel 5a (Android 14) physical device

[cortinico]

Closing as cannot reproduce @crawraps
Please provide further evidence and we can re-open

[dhruvpvx]

@cortinico I'm also facing the same issue in my physical android device it is OnePlus 9r with NameLess Custom Rom.
I think to reproduce this issue someone will need a oneplus device with custom rom

[dhruvpvx]

@cortinico currently I'm trying to switch from commits from each release to figure out in which release this issue first appeared
Is there any other way to figure out the issue?

[dhruvpvx]

@cortinico I tried switching from commit to commit on 0.73 I was able to generate a build from yarn android but in 72.8 this command is not running.
what I hit "yarn start" it says
No Metro config found in /Users/Desktop/react-native.

[cortinico]

I'm trying to switch from commits from each release to figure out in which release this issue first appeared

You should use the nightlies version we have listed here:
https://www.npmjs.com/package/react-native?activeTab=versions
to bisect this.

Specifically you can create a new app from a nightly version with:

npx react-native@latest init RNNightly --version 0.74.0-nightly-20231031-572dd76ba --skip-install

then do cd RNNightly && yarn && yarn android and verify when the issue started happening.

[dhruvpvx]

Okay thanks I'll try this way and update you in which version it started appearing first

[dhruvpvx]

as I am able to figure out this is working in 0.72.9 but not it 73.0.

[dhruvpvx]

@cortinico this issue first appeared in 0.73.0-nightly-20230521-6d24ee13a working fine in 0.73.0-nightly-20230519-de1e9f5d1

[dhruvpvx]

this the commit which is mentioned in the nightly version
6d24ee1
I tried reverting these changes but still text is not visible.

[cortinico]

I tried reverting these changes but still text is not visible.

How have you reverted those changes? The code is pre-compiled on Android, so editing the files inside node_modules will have no effect

[dhruvpvx]

I tried reverting these changes but still text is not visible.

How have you reverted those changes? The code is pre-compiled on Android, so editing the files inside node_modules will have no effect

How can I revert these changes other then that?

[dhruvpvx]

hey @cortinico can you please help to check if this is causing the issue

[cortinico]

You'll have to use a build from source:
https://reactnative.dev/contributing/how-to-build-from-source

[dhruvpvx]

@cortinico this is now working in latest commit I think #42258 this fixed this issue since all the changes are in the same file as in the commit which first started this issue

[dhruvpvx]

@cortinico i'm using react native 0.73 I need this part only how can I get this changing in node_modules doesn't work any other way?

[cortinico]

@cortinico i'm using react native 0.73 I need this part only how can I get this changing in node_modules doesn't work any other way?

Can you try to follow the insutrctions I linked (reactnative.dev/contributing/how-to-build-from-source), apply the changes in #42258 inside your node_modules folder, and verify if it solves?

[Ainias]

Is the fix included inside RN 0.73.6 or only in the 0.74-RCs?

[defnotsuhas]

Hi @cortinico,

I too am facing the same issue. I'm currently upgrading my Project's React Native from 72.7 -> 73.8. The text is being rendered on Android Simulator but on My Physical Device [OnePlus 6T running SuperiorOS Custom Rom Android 13] text is not rendered. I just tried a new project using 0.74 and it's working. The issue is resolved somewhere between 73.8 to 74.0.