Search Issue Tracker
In Progress
Fix In Review for 6000.4.0a4
Under Consideration for 6000.0.X, 6000.2.X, 6000.3.X
Votes
0
Found in
6000.0.59f1
6000.2.6f1
6000.3.0b4
6000.4.0a1
Issue ID
UUM-120359
Regression
No
[Android] Application not deployed on a device when "activity-alias" is used in the AndroidManifest
How to reproduce:
1. Open the “ReportBugProject.zip“ project
2. Open the “SampleScene“
3. Build and Run for Android
Expected result: The application gets deployed
Actual result: The application does not get deployed
Reproducible with: 2023.2.0a21 (25bfa0fab379), 6000.0.59f1, 6000.2.6f1, 6000.3.0b4, 6000.4.0a1
Reproducible environment: macOS 15.6.1 (M4 Max), Windows 11 (Reporters)
Not reproducible environment: No other environment tested
Reproducible with these devices:
VLNQA00319, Google - (Pixel 4), Android 13, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00511, Samsung Galaxy S8 (SM-G950F), Android 9, CPU: Exynos 9 Octa 8895, GPU: Mali-G71
VLNQA00335, Samsung Galaxy S20+ 5G (SM-G986B), Android 10, CPU: Exynos 990, GPU: Mali-G77
VLNQA00107, Huawei Nexus 6P (Nexus 6P), Android 8.1.0, CPU: Snapdragon 810 MSM8994, GPU: Adreno (TM) 430
Notes:
- Using “<activity-alias> [...] </activity-alias>“ in the custom AndroidManifest.xml file is the culprit of the issue
- You can open the app after the installation manually by pressing on it, but it does not open during the “Build and Run“ process
Errors:
DeploymentOperationFailedException: No activity in the manifest with action MAIN and category LAUNCHER. Try launching the application manually on the device.
UnityException: Could not find any valid targets to launch on for Android
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment