Question Android build succeeded but no artifacts

Hi,
Android debug build using Unity Cloud Build.
It shows success, but no artifacts.

I looked at the full log and while there are shader errors, there are no errors
that would cause the build to fail.

Please let me know if there are any logs to review or settings to check.

--- LOG

Unity Editor version: 2021.3.5f1 (40eb3a945986)
Branch: 2021.3/staging
Build type: Release
Batch mode: YES
macOS version: Version 11.6.2 (Build 20G314)
Darwin version: 20.6.0
Architecture: x86_64
Running under Rosetta: NO
Available memory: 16384 MB


COMMAND LINE ARGUMENTS:
/Volumes/2021_3_5f1/Unity.app/Contents/MacOS/Unity
-batchmode
-skipMissingProjectID
-skipMissingUPID
-buildTarget
android
-projectPath
/BUILD_PATH/***.***.android-debug/***
-logFile
-buildconfig
-bvrbuildtarget
android-debug
-upmServerPort
10010
-executeMethod
UnityEditor.CloudBuild.Builder.Build
-bvriconpath
/BUILD_PATH/***.***.android-debug/.build/last/android-debug/extra_data/artifacts/icon.png
-bvrbuildreportpath
/BUILD_PATH/***.***.android-debug/.build/last/android-debug/extra_data/build_report
-quit
Successfully changed project path to: /BUILD_PATH/***.***.android-debug/***

WORKSPACESIZE | ARTIFACTSSIZE
--------------|--------------
148.86 MiB | 2.77 KiB
[2022-08-09T07:39:13.381Z] - 6.2.2.2.7.4 - INFO: Publishing build 4 of ***/*** for target 'android-debug'...
[2022-08-09T07:39:18.254Z] - 6.2.2.2.7.4 - INFO: Zipping cache files from Library
tar: Library: Cannot stat: No such file or directory
tar: Error exit delayed from previous errors.
[2022-08-09T07:39:18.263Z] - 6.2.2.2.7.4 - INFO: Created the archive file.
[2022-08-09T07:39:19.815Z] - 6.2.2.2.7.4 - DEBUG: done.
Using /BUILD_PATH/.rvm/gems/ruby-2.7.4
[2022-08-09T07:39:40.081Z] - 6.2.2.2.7.4 - INFO: postbuildsteps finished successfully
[2022-08-09T07:39:46.113Z] - 6.2.2.2.7.4 - INFO: postbuildstatus finished successfully.
[+] Running with logging option...
Finished: SUCCESS

 

Same case here, Mac build and android build

Mac build was a new build config using the updated config UI
Android build was an edited build config using the updated config UI

Both have no prebuild/postbuild scripts/function

Any old configs untouched by the new UI still works as expected

 

Same case here. Making a bundled build, no artifacts available to download.

We use the API to run a private dashboard and it looks like it got the success signal and links to the correct set of artifacts but if I follow the link I get this response

Code (XML):

1. <Error>
2. <Code>ExpiredToken</Code>
3. <Message>The provided token has expired.</Message>
4. <Details>Request signature expired at: 2022-08-08T22:02:28+00:00</Details>
5. </Error>

 

It worked (as of this morning) with apks.

It does not work currently with abbs.

 

We did not have addressables enabled but it did set our default build selection to be a Content Only Build.

Enabling addressables, disabling this option and then building seems to have worked. It looks like it's respecting this option even if addressables is not enabled for the build.

 

O man this was driving me insane. Really hope that this was the issue on my end. Also some more descriptive error reporting would be nice when there is no build artifact and the share link "link" is clicked.

Something like, "This is a content only build, so there is no build to share".

 

Hi, benjamingooding

I had the same issue with a different but simpler project than the one I first reported, so I'll post the ProjectID for simpler one.

ProjectID
39816984-bebf-4564-a491-64d950b6f15f
The problem occurred in Default Android Debug #1.

using Pre-Export method

thx

 

The issue is still occurring.

 

I found a artifacts.
Thanks

 

I'm getting no IPA, APK, or AAB artifacts for any of our builds since the new Build Target Configuration UI rolled out. We do not use addressables.

Need help!!

ProjectID
988a7f8f-2f90-45a5-baae-640155348043

 

Thanks for the help, disabling 'content builds only' seems to have worked for me. I've never switched that on before though and the build was working ok previously. The only change I noticed was that it suddenly moved to the new Build Target UI so perhaps there's something in that code that sets that flag automatically.

 

Benjamin - yes, following your advice fixed the builds. I misinterpreted your advice the first pass through, it took taking a look at it the next day to understand what you were suggesting.

Thanks for the help!

 

I'm having the same problem, on a windows build. Everything was fine until I renamed the build executable name, then artifacts were no longer built.
I tried enabling addressables, saving, then disabling them, but that didn't work.

Is there a trick I'm missing?