Search Issue Tracker

Fixed in 2.2.4

Fixed in 4.0.1

Votes

0

Found in [Package]

2.2.3

3.0.0

4.0.0

Issue ID

APB-2

Regression

No

AdaptivePerformanceGeneralSettings.Instance.Manager.activeLoader isn't null when using Samsung device which is not supported

Package: Adaptive Performance

-

How to reproduce:
1. Download the attached project 'UAP.zip'
2. Build and Run on Android (Samsung device that is not supported: https://docs.unity3d.com/Packages/com.unity.adaptiveperformance.samsung.android@4.0/manual/index.html)
3. When app loads, press 'Check loader status' button
4. Observe the printed text above the button

Expected result: The text printed: null loader
Actual result: The text printed: loader not null and initialized

Reproducible with: 2.0.0-preview.7, 2.2.2 (2019.4.37f1), 2.2.2 (2020.3.32f1), 4.0.0 (2021.2.18f1, 2022.1.0b14, 2022.2.0a10)
Could not test with: 2.0.0-preview.4 (2019.4.37f1) (compile errors)

Reproducible with:
VLNQA00288, Samsung Galaxy J7 (SM-J730F), Android 8.1.0, CPU: Exynos 7 Octa 7870, GPU: Mali-T830

Notes:
- Actual result is expected only on supported Samsung devices, however, it appears on unsupported Samsung devices too

  1. Resolution Note:

    Fix bug where Adaptive Performance Samsung Provider is not deinitialized properly after not being successfully initialized due to lack of Samsung GameSDK.

  2. Resolution Note:

    Fix bug where Adaptive Performance Samsung Provider is not deinitialized properly after not being successfully initialized due to lack of Samsung GameSDK.

  3. Resolution Note:

    Fix bug where Adaptive Performance Samsung Provider is not deinitialized properly after not being successfully initialized due to lack of Samsung GameSDK.

Log in to vote on this issue

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.

Latest issues

See all new issues