Search Issue Tracker
By Design
Votes
0
Found in [Package]
3.0.1
Issue ID
1127423
Regression
Yes
#if UNITY_ADS doesn't return the right result when not on Ads platform (Windows)
This small repro project was ripped out of a customer project.
Repro steps:
- download this project
- open it with unity 18.3, 19.1 or 19.2
- Ads package version should be 3.0.1
- Play the scene
- notice there is no button in play mode
What happens:
- if on windows, the players should always be able to Hunt
- if on Android, the player will have to watch an add first
- #if UNITY_ADS doesn't return the right result so button ends up not appearing at all
In the larger project, i can't build at all with 3.0.1 because the code paths end up calling library functions that won't exist on Windows.
Reproducible on Unity Editor 2018.3.0.a1 and all older versions.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- GPU utilization increases by 20% on Meta Quest headsets when Render Graph is enabled on 6000.0.16f1 and higher
- Value on Slider (Int) control in UI Builder displays as default when saving UI Document
- Color mismatch in UI Builders Library panel when the Editors theme is set to Light Mode
- [Android ] "AndroidJNI.ToBooleanArray" returns a random non-zero value instead of "IntPtr.Zero" when the method argument is null
- Non-HDR color picker opens when selecting material color with HDR enabled
Resolution Note:
This behaviour is by design. UNITY_ADS returns false on the platforms other than Android/iOS (even in Editor). If you want to have such behaviour, you need to add UNITY_ADS to Scripting Define Symbols inside Project Settings.