Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[0.78.0-rc.2] Test Report: vonovak #757

Closed
8 tasks done
vonovak opened this issue Jan 28, 2025 · 3 comments
Closed
8 tasks done

[0.78.0-rc.2] Test Report: vonovak #757

vonovak opened this issue Jan 28, 2025 · 3 comments
Assignees
Labels
Type Release Crew Issues that are only relevant for Release Crew

Comments

@vonovak
Copy link

vonovak commented Jan 28, 2025

Target Minor

0.78.0-rc.2

Under what system configuration was the test run?

Details

System:
OS: macOS 15.2
CPU: (10) arm64 Apple M1 Max
Memory: 138.53 MB / 64.00 GB
Shell:
version: 5.2.15
path: /opt/homebrew/bin/bash
Binaries:
Node:
version: 22.11.0
path: /opt/homebrew/bin/node
Yarn:
version: 1.22.22
path: /opt/homebrew/bin/yarn
npm:
version: 10.9.0
path: /opt/homebrew/bin/npm
Watchman:
version: 2024.10.21.00
path: /opt/homebrew/bin/watchman
Managers:
CocoaPods:
version: 1.16.2
path: /opt/homebrew/lib/ruby/gems/2.7.0/bin/pod
SDKs:
iOS SDK:
Platforms:
- DriverKit 24.1
- iOS 18.1
- macOS 15.1
- tvOS 18.1
- visionOS 2.1
- watchOS 11.1
Android SDK:
API Levels:
- "26"
- "33"
- "34"
- "35"
Build Tools:
- 26.0.3
- 30.0.2
- 30.0.3
- 33.0.0
- 33.0.1
- 34.0.0
- 35.0.0
System Images:
- android-23 | Google APIs ARM 64 v8a
- android-24 | Google Play Intel x86 Atom
- android-26 | Google APIs Intel x86_64 Atom
- android-33 | Google APIs Intel x86_64 Atom
- android-33 | Google Play ARM 64 v8a
- android-34 | Google APIs ARM 64 v8a
- android-VanillaIceCream | Google Play ARM 64 v8a
Android NDK: Not Found
IDEs:
Android Studio: 2024.2 AI-242.23726.103.2422.12816248
Xcode:
version: 16.1/16B40
path: /usr/bin/xcodebuild
Languages:
Java:
version: 21.0.4
path: /usr/bin/javac
Ruby:
version: 3.3.6
path: /opt/homebrew/bin/ruby
npmPackages:
"@react-native-community/cli": Not Found
react: Not Found
react-native: Not Found
react-native-macos: Not Found
npmGlobalPackages:
"react-native": Not Found

Tested configurations

Refer to this spreadsheet for test cases.

  • RNTester + iOS + Hermes
  • RNTester + iOS + JSC
  • RNTester + Android + Hermes

gives these errors in redbox but everything works after dismissing them. I've seen this before on 77 too but it's intermittent it seems.

 (NOBRIDGE) LOG  Running "RNTesterApp" with {"rootTag":11,"initialProps":{},"fabric":true}
 (NOBRIDGE) ERROR  StaticViewConfigValidator: Invalid static view config for 'RCTView'.

- 'validAttributes.experimental_layoutConformance' is missing.
 (NOBRIDGE) ERROR  StaticViewConfigValidator: Invalid static view config for 'RCTImageView'.

- 'validAttributes.experimental_layoutConformance' is missing.
 (NOBRIDGE) ERROR  StaticViewConfigValidator: Invalid static view config for 'AndroidTextInput'.

- 'validAttributes.experimental_layoutConformance' is missing.
 (NOBRIDGE) ERROR  StaticViewConfigValidator: Invalid static view config for 'RCTScrollView'.

- 'validAttributes.experimental_layoutConformance' is missing.
 (NOBRIDGE) ERROR  StaticViewConfigValidator: Invalid static view config for 'DebuggingOverlay'.

- 'validAttributes.experimental_layoutConformance' is missing.
 (NOBRIDGE) ERROR  StaticViewConfigValidator: Invalid static view config for 'RCTSafeAreaView'.

- 'validAttributes.experimental_layoutConformance' is missing.
 (NOBRIDGE) ERROR  StaticViewConfigValidator: Invalid static view config for 'AndroidHorizontalScrollContentView'.

- 'validAttributes.experimental_layoutConformance' is missing.
 (NOBRIDGE) ERROR  StaticViewConfigValidator: Invalid static view config for 'AndroidHorizontalScrollView'.

modal looks odd, as if elevation prop was interfering. Let me see how it was on 77

Click me

Image

  • RNTester + Android + JSC

I sometimes see Images not loading, accompanied with Encoded image is null in metro logs.

  • RNTestProject + iOS + Hermes

still seeing debugger icon missing as in #724 (comment)

  • RNTestProject + iOS + JSC
  • RNTestProject + Android + Hermes
  • RNTestProject + Android + JSC

Close this issue if there are no blocking issues.

Blocking Issues?

  • Android - blocking for stable: I sometimes see Images not loading, accompanied with Encoded image is null in metro logs and unknown:WrappingUtils com.facebook.react.uiapp W Don't know how to round that drawable: com.facebook.react.views.image.ReactImageDownloadListener$EmptyDrawable in logcat.
@vonovak vonovak added the Type Release Crew Issues that are only relevant for Release Crew label Jan 28, 2025
@fabriziocucci fabriziocucci moved this from Inbox to In Progress in React Native 0.78 Releases Jan 28, 2025
@vonovak vonovak closed this as completed Jan 28, 2025
@github-project-automation github-project-automation bot moved this from In Progress to Done / Picked in React Native 0.78 Releases Jan 28, 2025
@cortinico
Copy link
Collaborator

  • Android - blocking for stable: I sometimes see Images not loading, accompanied with Encoded image is null in metro logs and unknown:WrappingUtils com.facebook.react.uiapp W Don't know how to round that drawable: com.facebook.react.views.image.ReactImageDownloadListener$EmptyDrawable in logcat.

Oh that's concerning. How do you reproduce this @vonovak ?

@vonovak
Copy link
Author

vonovak commented Jan 28, 2025

I reproduce this with yarn test-e2e-local -t "RNTester" -p "Android" -h false / true -c $GITHUB_TOKEN

when I go to the Image screen I see no images, but space for them seems occupied.

Details

Image

It seems the emulator is somehow faulty or has some weird settings that break the images, because my other emulators (tried 2) do render them and also print the Encoded image is null in console. Let me try 77 branch too and report later.

The buggy emulator below.

Properties
avd.ini.displayname              Pixel 6 Pro API 34-14 noGS
avd.ini.encoding                 UTF-8
AvdId                            Pixel_6_Pro_API_34-14_noGS
disk.dataPartition.size          6442450944
fastboot.chosenSnapshotFile      
fastboot.forceChosenSnapshotBoot no
fastboot.forceColdBoot           no
fastboot.forceFastBoot           yes
hw.accelerometer                 yes
hw.arc                           false
hw.audioInput                    yes
hw.battery                       yes
hw.camera.back                   virtualscene
hw.camera.front                  emulated
hw.cpu.ncore                     4
hw.device.hash2                  MD5:a8abfd3536f3d35e4ba2041a7b99f40e
hw.device.manufacturer           Google
hw.device.name                   pixel_6_pro
hw.dPad                          no
hw.gps                           yes
hw.gpu.enabled                   yes
hw.gpu.mode                      auto
hw.initialOrientation            portrait
hw.keyboard                      yes
hw.lcd.density                   560
hw.lcd.height                    3120
hw.lcd.width                     1440
hw.mainKeys                      no
hw.ramSize                       2048
hw.sdCard                        yes
hw.sensors.orientation           yes
hw.sensors.proximity             yes
hw.trackBall                     no
image.androidVersion.api         34
image.sysdir.1                   system-images/android-34/google_apis/arm64-v8a/
PlayStore.enabled                false
runtime.network.latency          none
runtime.network.speed            full
showDeviceFrame                  yes
skin.dynamic                     yes
tag.display                      Google APIs
tag.displaynames                 Google APIs
tag.id                           google_apis
tag.ids                          google_apis
vm.heapSize                      384

@vonovak
Copy link
Author

vonovak commented Jan 28, 2025

I confirm the Modal component looks the same on 77, and the problem was with my emulator. After purging its data and cold-starting it, it works all good.
So the bottom line is that all is good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type Release Crew Issues that are only relevant for Release Crew
Projects
Status: Done / Picked
Development

No branches or pull requests

2 participants