Search Issue Tracker
By Design
Votes
0
Found in
2017.3.0b3
Issue ID
956362
Regression
Yes
Exporting with Gradle 'Release Build' skips the keystore checking
Steps to reproduce:
1) Open Unity and create a new project
2) Switch Platform to Android
3) In the Player Settings, fill Package Name field
4) In the Build Settings, select Gradle Build System
5) Enable Export Project
6) Click on Export button
Expected result: Error "Release builds must be signed when using Gradle! Please select a keystore and a signing key!" should appear on Release Build if there is no keystore selected
Actual result: There is no error when exporting and keystore is not selected on Release Build
Reproduced with:
5.6.3p4, 2017.1.1p4, 2017.2.0f3, 2017.3.0b3
Regression since:
For 2017.2 version - 2017.2.0b2
For 2017.1 version - 2017.1.0p2
For 5.6 version - 5.6.3p2
Not reproduced with:
5.6.3p1, 2017.1.0p1, 2017.2.0b1
Note: Development Build works as expected, keystore is not required when exporting this project
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment