Hello I had the same issue as you describe. I fixed it by reinstalling node_modules and running : npx react-native start --reset-cache

I am facing the same issue with react-native version0.64.1

I built a wrapper component do un-virtualize the list when scrollEnabled={false} to get around this, eg:

import React from 'react';
import { FlatListProps, FlatList as NativeFlatList, View } from 'react-native';

// Custom FlatList that doesnt try to virtualize when scrollEnabled={false}
// Do this to avoid "VirtualizedLists should never be nested inside plain ScrollViews with the same orientation" error in console
export default function FlatListWrapper<ItemT>(props: FlatListProps<ItemT>) {
  if (!props.scrollEnabled) {
    return (
      <View style={props.style}>
        {!!props.ListHeaderComponent && !!props.data && props.data.length > 0 && props.ListEmptyComponent}
        {!!props.ListEmptyComponent && (!props.data || props.data.length === 0) && props.ListEmptyComponent}
        {!!props.data && props.data.map((item: any, index) => <View key={!!props.keyExtractor ? props.keyExtractor(item, index) : `${index}`}>
          {!!props.renderItem && props.renderItem({
            item, index, separators: {
              highlight: () => null,
              unhighlight: () => null,
              updateProps: (select: 'leading' | 'trailing', newProps: any) => null
            }
          })}
        </View>)}
        {!!props.ListFooterComponent && !!props.data && props.data.length > 0 && props.ListFooterComponent}
      </View>
    );
  }
  return <NativeFlatList {...props} />;
}

Hi @RSNara , any update on this PR?

If someone encounters this problem, please let me know how to solve it. Thank you

receive Forbidden!

Description

Please provide a clear and concise description of what the bug is. Include screenshots if needed. Please test using the latest React Native release to make sure your issue has not already been fixed: https://reactnative.dev/docs/upgrading.html

React Native version:

Run react-native info in your terminal and copy the results here.

Steps To Reproduce

Provide a detailed list of steps that reproduce the issue.

Expected Results

Describe what you expected to happen.

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

Please provide a Snack (https://snack.expo.io/), a link to a repository on GitHub, or provide a minimal code example that reproduces the problem. You may provide a screenshot of the application if you think it is relevant to your bug report. Here are some tips for providing a minimal example: https://stackoverflow.com/help/mcve

receive Forbidden!

Description

Please provide a clear and concise description of what the bug is. Include screenshots if needed. Please test using the latest React Native release to make sure your issue has not already been fixed: https://reactnative.dev/docs/upgrading.html

React Native version:

Run react-native info in your terminal and copy the results here.

Steps To Reproduce

Provide a detailed list of steps that reproduce the issue.

Expected Results

Describe what you expected to happen.

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

Please provide a Snack (https://snack.expo.io/), a link to a repository on GitHub, or provide a minimal code example that reproduces the problem. You may provide a screenshot of the application if you think it is relevant to your bug report. Here are some tips for providing a minimal example: https://stackoverflow.com/help/mcve

Have you fixed it? I got it too. Everything worked well, but it shows errors in the console.

I am having this issue now on one of my app.

@Simek @EyMaddis I'm sorry I'm so late to this conversation -- I'm just now getting to the work of moving the React Native TV repo to 0.64.2 and saw this PR and discussion. Yes TVEventHandler is a weird API, but it's much easier if you use my more modern version, useTVEventHandler() (see https://github.com/react-native-tvos/react-native-tvos/pull/86). Maybe that could be merged to core.

I had the same issue so upgraded React and React Native using the Upgrade helper as a guide

My System:

• Apple Mac Mini M1 Silicon (2020).
• Mac OS 11.4
• XCode 12.5 (open with Rosetta)
• Target Build IOS 14.3

I made the following changes to package.json:

• Updated from "react": "16.13.1" to "react": "17.0.1"
• Updated from "react-native": "0.63.4" to "react-native": "0.64.2",
• Updated from "@babel/core": "^7.8.4" to "@babel/core": "^7.12.9"
• Updated from "@babel/runtime": "^7.8.4" to "@babel/runtime": "^7.12.5"
• Updated from "@react-native-community/eslint-config": "^1.1.0" to "@react-native-community/eslint-config": "^2.0.0"
• Updated from "@types/jest": "^25.1.0" to "@types/jest": "^26.0.23"
• Updated from "eslint": "^6.5.1" to "eslint": "^7.14.0"
• Updated from "jest": "^25.1.3" to "jest": "^26.6.3"
• Updated from "metro-react-native-babel-preset": "^0.59.0" to "metro-react-native-babel-preset": "^0.64.0"
• Updated from "react-test-renderer": "16.13.1" to "react-test-renderer": "17.0.1"

Updated Node to 16.3.0 in NVM.

• In Terminal: nvm unalias default Deleted node_modules folders, pod folder and cleaned build in Xcode Deleted everything in /Users/xxxxx/Library/Developer/Xcode/DerivedData Installed all packages: npm install Updated pod repo: arch -x86_64 pod repo update Installed pod packages: arch -x86_64 pod install (Note: arch -x86_64 only for M1 Silicon)

Then built and archived successfully in Xcode 12.5. Images then rendered in TestFlight

@Fannolo Great thank you! Would you also be interested in writing a jest test for this component? You can take a look at VirtualizedList-test as an example: https://github.com/facebook/react-native/blob/dc80b2dcb52fadec6a573a9dd1824393f8c29fdc/Libraries/Lists/tests/VirtualizedList-test.js

you can check out the Jest API: and run the the test via

yarn test [name of your test]

Hi @lunaleaps, I added some tests to the StaturBar component could you take a look and see if I'm going on the right direction? Thanks!

Description

Text: display: none won't work on Android for nested text elements.

React Native version:

<pre> System: OS: Linux 5.9 Manjaro Linux CPU: (8) x64 Intel(R) Core(TM) i7-8809G CPU @ 3.10GHz Memory: 2.58 GB / 31.28 GB Shell: 5.8 - /bin/zsh Binaries: Node: 14.16.0 - /usr/bin/node Yarn: 2.4.0 - /usr/bin/yarn npm: 7.15.0 - /usr/bin/npm Watchman: 4.9.0 - /usr/bin/watchman SDKs: Android SDK: API Levels: 28, 29, 30 Build Tools: 28.0.3, 29.0.0, 29.0.2, 29.0.3, 30.0.0, 30.0.1, 30.0.3, 31.0.0 System Images: android-22 | Google APIs Intel x86 Atom, android-23 | Google APIs Intel x86 Atom, android-27 | Google APIs Intel x86 Atom, android-29 | Google APIs Intel x86 Atom, android-30 | Google APIs Intel x86 Atom, android-30 | Google APIs Intel x86 Atom_64, android-30 | Google Play Intel x86 Atom Android NDK: Not Found IDEs: Android Studio: 4.2 AI-202.7660.26.42.7351085 Languages: Java: 1.8.0_292 - /usr/bin/javac npmPackages: @react-native-community/cli: Not Found react: 17.0.2 => 17.0.2 react-native: ^0.64.2 => 0.64.2 npmGlobalPackages: react-native: Not Found </pre>

Steps To Reproduce

Implement any component rendering this hierarchy of elements:

<Text>
  <Text style={{ display: 'none' }}>Hello world!</Text>
</Text>

And run on Android.

Expected Results

"Hello world" should not be displayed on screen.

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

https://snack.expo.io/@jsamr/nested-text-display-none

So.... anything new?

Dear Support Team,

I am using react native with expo cli to build my app, I got an error:

Warning I got

Unable to start your application. Please refer to https://expo.fyi/no-registered-application for more information.

Error I got

ReferenceError: e is not @defined

Nothing elegant, I ended up rescaling my image so that the pattern was 2x smaller than I wanted it. Then, when it got blown up in production, it was at least the right size. 🤷‍♀️

any updates ?

Getting blank screen for android on Mac OS. Looks fine on Windows OS.

OS: macOS 10.14.4 React Native version: react: 16.8.6 => 16.8.6 react-native: 0.60.3 => 0.60.3

Steps To Reproduce

1. react-native init testapp
2. react-native run-android

Expected screen New intro screen

Workaround Run react-native start before running react-native run-android

@amarlette #31532 fixes this issue.

Description

New clear project is not running on physical device via Xcode.

React Native version:

System: OS: macOS 11.4 CPU: (8) x64 Apple M1 Memory: 640.37 MB / 16.00 GB Shell: 5.8 - /bin/zsh Binaries: Node: 14.17.0 - /usr/local/bin/node Yarn: Not Found npm: 6.14.13 - /usr/local/bin/npm Watchman: 2021.06.07.00 - /usr/local/bin/watchman Managers: CocoaPods: 1.10.1 - /usr/local/bin/pod SDKs: iOS SDK: Platforms: iOS 14.5, DriverKit 20.4, macOS 11.3, tvOS 14.5, watchOS 7.4 Android SDK: API Levels: 29, 30 Build Tools: 28.0.3, 29.0.2, 30.0.3 System Images: android-30 | Google APIs Intel x86 Atom, android-S | Google APIs ARM 64 v8a Android NDK: Not Found IDEs: Android Studio: 4.2 AI-202.7660.26.42.7231092 Xcode: 12.5/12E262 - /usr/bin/xcodebuild Languages: Java: 1.8.0_292 - /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/bin/javac npmPackages: @react-native-community/cli: Not Found react: 17.0.1 => 17.0.1 react-native: 0.64.2 => 0.64.2 react-native-macos: Not Found npmGlobalPackages: react-native: Not Found

Steps To Reproduce

1. npx react-native init ProjectName 2.open ProjectName.xcworkspace in iOS folder in project folder 3.try to build

But npx react-native run-ins works perfect. issue is only with Xcode when trying to build and test in physical device.

Physical device: iPhone 8 Plus iOS 14.6