Search Issue Tracker
Fixed
Votes
0
Found in [Package]
3.2.0
Issue ID
1206753
Regression
Yes
[Android] Banner Ads not working on application when built to Android device
To reproduce:
1. Open attached project
2. Build and run to android device
3. In application change the level from 1 to 2
4. Press load the level
Actual result: The banner ad is not showing up
Expected result: The banner ad should be visible instantly after loading
Reproduced with: 2019.2.18f1; 2020.1.0a19
Can not open the project on 2017.4- crashing; 2018.4 errors.
Tested and reproduced with:
VLNQA00099, Google Pixel XL (Pixel XL), Android 9, CPU: Snapdragon 821 MSM8996 Pro, GPU: Adreno (TM) 530
VLNQA00121, Samsung Galaxy S9 (SM-G960F), Android 9, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00285, Samsung Galaxy J4 Core (SM-J410F), Android 8.1.0, CPU: NOT FOUND, GPU: Adreno (TM) 308
VLNQA00290, Samsung Galaxy S10 5G (SM-G977U), Android 9, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00110, Samsung Galaxy Note2 (GT-N7100), Android 4.4.2, CPU: Exynos 4 Quad 4412, GPU: Mali-400 MP
Note: works on the editor
Can not check on standalone due to TLS Allocator ALLOC_TEMP_THREAD, underlying allocator ALLOC_TEMP_THREAD has unfreed allocations, size 33
Not reproducible with iPhone XR (iOS 12.0)
Logcat attached
Does not reproduce with 3.1.1 Ads package
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
- Size of ShadowCaster2D with Casting Source set to a Collider increases when RigidBody2D is attached to the GameObject
- GameObjects with a material derived from a Custom Lighting Surface Shader are displayed as skewed on quads when the Camera's Width and Height properties of the Viewport Rect are lower than 1
- Warning 'Unable to find player assmebly' is thrown when building some Project Templates
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
- [Linux] Touch freezes in Player when any mouse button is clicked
Resolution Note:
Not a bug, User Error.