Search Issue Tracker
Fixed in 2017.3.0f3
Fixed in 2017.1.X, 2017.2.X
Not Reproducible in 5.6.X
Votes
0
Found in
2017.1.0p1
Issue ID
934735
Regression
Yes
Android build fails but "Build completed with a result of 'Succeeded'" message is shown
How to reproduce:
1. Open the attached project
2. Set "Android" as the current target
3. Set "Gradle" as the build option
4. In player settings > publishing settings set existing keystore (you will find it in the project ../Keystore/TestKeyStore.jks , password is Unity77) or create a new one
5. Build the project
Actual result: Build fails, but one can see in Console (2017.2) or Editor.log "build succeeded" message
Expected result: if build fails, it shouldn't write that it succeeded
Reproducible: 2017.1.0p1, 2017.2.0b4, 2017.3.0a1
Not reproducible: 5.6.2p3
Same issue when building with Gradle or Internal build system
Comments (2)
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
- "Modifying the parent of a VisualElement while it’s already being modified is not allowed" error is thrown when entering text and pressing tab in the Search window
- Mesh colliders are not updating their positions of bounds correctly
- Images are missing from the "Open the sprite editor" documentation for 6.0, 6.1 and 6.2
- The previous element in the array is modified when assigning an Asset to a new element of AssetReferenceT
- Unity Perforce Integration: VCS Connection Active State Fails via CLI with Valid Inputs
pako
Sep 02, 2018 21:40
Same error Unity 2018.2.6f1.
However, BEFORE the "build succeeded" message, there were 2 error messages:
Failed running C:\Program Files\Unity 2018\Editor\Data\il2cpp/build/il2cpp.exe --convert-to-cpp --emit-null-checks --enable-array-bounds-check --compile-cpp --libil2cpp-static --platform="Android" --architecture="ARMv7" --configuration="Release" --outputpath= ...
and
Exception: C:\Program Files\Unity 2018\Editor\Data\il2cpp/build/il2cpp.exe did not run properly!
awais503
Jul 10, 2018 05:46
Again same error in unity 2018.2.0b.11..