Search Issue Tracker

Fixed

Fixed in 2021.3.20f1, 2022.2.9f1, 2023.1.0b6, 2023.2.0a1

Won't Fix in 2020.3.X

Votes

0

Found in

2020.3.42f1

2021.3.14f1

2022.1.23f1

2022.2.0b16

2023.1.0a20

2023.2.0a1

Issue ID

UUM-19683

Regression

No

[Android] Network.OperationalStatus method returns Unknown status for all network interfaces when observing their operational state

--

-

How to reproduce:
1. Open the user’s attached “bug-android-networkinterface” project
2. Build and Run the “SampleScene” Scene on Android
3. Click the “NetworkInterface”-labeled button
4. Search for “@@@” pattern in Android logcat

Expected result: For the most network interfaces “OpStatus” value isn’t “Unknown”
Actual result: “OpStatus” value for all network interfaces is “Unknown”

Reproducible with: 2020.3.42f1, 2021.3.14f1, 2022.1.23f1, 2022.2.0b16, 2023.1.0a20

Reproduced on: macOS 13.0 (Intel)

Reproducible with devices:
VLNQA00479 - Samsung Galaxy S22 (SM-S901B), CPU: Exynos 2200, GPU: ANGLE (Samsung Xclipse 920) on Vulkan 1.1, OS: 12
VLNQA00472 - Samsung Galaxy A52 (SM-A525F), CPU: Snapdragon 720G (SM7125), GPU: Adreno 618, OS: 12
VLNQA00468 - HUAWEI P40 Pro (Global) (ELS-NX9), CPU: HiSilicon Kirin 990 5G, GPU: Mali-G76, OS: 10
VLNQA00407 - Galaxy Z Flip3 5G (SM-F711B), CPU: Snapdragon 888, GPU: Adreno 660, OS: 11
VLNQA00409 - Galaxy Z Fold3 5G (SM-F926B), CPU: Snapdragon 888, GPU: Adreno 660, OS: 11
(user’s info) - Samsung Galaxy A32, OS: 12
(user’s info) - Samsung Galaxy S20 FE 5G, OS: 12

Not reproducible with devices:
VLNQA00414 - Galaxy Note10+ 5G (SM-N976V), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 9
VLNQA00264 - Samsung Galaxy S10+ (SM-G975F), CPU: Exynos 9 9820, GPU: Mali-G76, OS: 10.0.0

  1. Resolution Note (fix version 2023.2.0a1):

    Fixed in 2023.2.0a1

  2. Resolution Note (fix version 2023.1.0b6):

    Fixed in 2023.1.0b6

  3. Resolution Note (fix version 2022.2.9f1):

    Fixed in 2022.2.9f1

  4. Resolution Note (fix version 2021.3.20f1):

    Fixed in 2021.3.20f1

  5. Resolution Note (2020.3.X):

    Unfortunately, the fix for this bug for this issue is too risky to bring back to a stable release such as 2020.3 as the underlying implementation is considerably different than 2021.3+

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.