Search Issue Tracker
Fixed in 5.6.0
Votes
2
Found in
5.5.0f3
Issue ID
860737
Regression
Yes
BuildOptions.AcceptExternalModificationsToPlayer causes UnityException: Unknown project type: 0
This throws an error in the Android build process, so sending it over to the Android team. Let me know if you don't concur and we'll start talks between dev teams.
How to reproduce:
1. Open user provided project
2. In editor press 'Tigercreate' > 'Build Android Exporter Template'
3. Observe error in console
Expected behaviour: Successful android build is placed in folder specified in editor script
Actual behaviour: UnityExpection: Unknown project type: 0 is thrown
Reproduced on: 5.5.0f3, 5.5.0p3, 5.6.0b2
Not reproduced on: 5.3.7p3, 5.4.4f1
Comments (5)
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
invadererik
Feb 27, 2018 22:17
still an issue building APK from command line on 2017.3.0f3 , if EditorUserBuildSettings.androidBuildSystem = AndroidBuildSystem.Internal; is also set
SBoltonMW
Jun 05, 2017 18:39
What versions of Unity was this fixed in?
michael-v
Jan 02, 2017 19:46
You should set EditorUserBuildSettings.androidBuildSystem = AndroidBuildSystem.ADT;
(or other prefered build system).
neec12
Dec 26, 2016 02:05
exactly same for me!
i've been testing on 5.5.0p2, 5.5.0p3.