Search Issue Tracker
Fixed in 2017.2.0f3
Fixed in 5.6.X, 2017.1.X
Votes
0
Found in
5.6.1p1
Issue ID
913164
Regression
Yes
[Android] Exporting project with Gradle forces to have a keystore
Steps to reproduce:
1) Open Unity and create a new project
2) In Build Settings, switch platform to Android
3) Select Build System as Gradle and enable Export Project
4) Click on Export button
Observe dialog window popping up which says "Release builds must be signed when using Gradle! Please select a keystore and a signing key!"
Expected result: Unity should not require to have a keystore when exporting project with Gradle
Actual result: Unity requires to have a keystore when exporting project with Gradle (check attached image 'bug.png')
Reproduced with:
5.6.1p1, 5.6.1p3, 2017.1.0b9, 2017.2.0a3
Not reproduced with:
5.6.0b10, 5.6.1f1
Regression since:
5.6.1p1
Note that only release builds with Gradle should require to have a keystore(Build || Build and Run), but not exporting projects
--------------------------------------
Fixed in: 5.6.3p2, 2017.1.0p5, 2017.2.0b9
Comments (3)
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
- 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
unifiedJed
Jan 28, 2018 17:11
one easy solution is checking "developement build" in build settings
drokid
Oct 16, 2017 10:59
I have Unity 2017.3 and still have this issue.
eslamtharwat
Aug 13, 2017 23:34
i need solution