# Crashed while building composer using Kit app template

**URL:** <https://forums.developer.nvidia.com/t/crashed-while-building-composer-using-kit-app-template/342457>\
**Category:** Kit App Template / SDK\
**Created:** [August 18, 2025, 3:55pm UTC](https://forums.developer.nvidia.com/t/crashed-while-building-composer-using-kit-app-template/342457 "2025-08-18T15:55:07Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Zephyr](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@Zephyr](https://forums.developer.nvidia.com/u/Zephyr)\
**Post date:** [August 18, 2025, 3:55pm UTC](https://forums.developer.nvidia.com/t/crashed-while-building-composer-using-kit-app-template/342457/1 "2025-08-18T15:55:07Z")

</div>

When trying to create a composer using Kit app template, I always encounter crashes。  
`2394-08-18T15:53:14Z [1,762,375ms] [Error] [omni.ext.plugin] One or a few of extensions failed to pull. 2394-08-18T15:53:14Z [1,762,375ms] [Error] [omni.kit.app.plugin] Failed to generate version file, kit file: my_company.my_usd_composer-0.1.0 failed to resolve dependencies. 2394-08-18T15:53:14Z [1,762,376ms] [Error] [omni.kit.app.plugin] Exiting app because of dependency solver failure... [08/18/25 23:53:14] ERROR error running: G:\kit-app-template\_build\windows-x86_64\release\kit\kit.exe utils.py:264 G:\kit-app-template\source\apps\my_company.my_usd_composer.kit --allow-root --portable --ext-precache-mode --/crashreporter/gatherUserStory=0 --/app/settings/persistent=0 --/app/settings/loadUserConfig=0 --/app/extensions/generateVersionLock=1 --/app/extensions/parallelPullEnabled=1 --/app/enableStdoutOutput=1 --/app/extensions/detailedSolverExplanation=1 --/app/extensions/registryEnabled=1 --/app/extensions/mkdirExtFolders=0 --/app/extensions/registryCacheFull='G:\kit-app-template\_build\windows-x86_64 \release\extscache' --/log/flushStandardStreamOutput=1 --/exts/omni.kit.registry.nucleus/registries/0/name=\"kit/default\" --/exts/omni.kit.registry.nucleus/registries/0/url=\"https://ovextensionsprod. blob.core.windows.net/exts/kit/prod/${kit_version_major}/shared\" --/exts/omni.kit.registry.nucleus/registries/1/name=\"kit/sdk\" --/exts/omni.kit.registry.nucleus/registries/1/url=\"https://ovextensionsprod. blob.core.windows.net/exts/kit/prod/sdk/${kit_version_short}/${kit_git_hash}\" --/exts/omni.kit.registry.nucleus/registries/2/name=\"kit/community\" --/exts/omni.kit.registry.nucleus/registries/2/url=\"https://dw290v42wisod.clo udfront.net/exts/kit/community\" --/app/extensions/target/config=release --ext-folder G:\kit-app-template\source\extensions --ext-folder G:\kit-app-template\source\apps --portable-root G:/kit-app-template/_build/windows-x86_64/release --/app/extensions/generateVersionLockSkipLocalExts=1, code: 55, message: "" ERROR SystemExit exception stack trace dumped to logfile log.py:182 G:/kit-app-template/_repo/repo.log. Stacks dumped to console via `–verbose`or `–tracebacks`. SystemExit: 55 [08/18/25 23:53:14] ERROR error running: G:/kit-app-template/repo.bat precache_exts -c release, code: utils.py:264 55, message: "" WARNING Retrieving repo_build version via VERSION file. version.py:312 ERROR SystemExit exception stack trace dumped to logfile log.py:182 G:/kit-app-template/_repo/repo.log. Stacks dumped to console via `–verbose`or `–tracebacks`. SystemExit: 55`

---

<div class="post-metadata">

**Author:** ![Richard3D](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/richard3d/32/207062_2.png) [@Richard3D](https://forums.developer.nvidia.com/u/Richard3D)\
**Post date:** [August 18, 2025, 8:31pm UTC](https://forums.developer.nvidia.com/t/crashed-while-building-composer-using-kit-app-template/342457/2 "2025-08-18T20:31:53Z")

</div>

This is just an initial guess, but I have seen a lot of people that cannot create the kit app template on any drive other than the main C drive. I would say, straight away, forget the G Drive and test it on the C drive. It is very small. It does not take a lot of room up. Test it and at least confirm. I suspect it may work fine.

---

<div class="post-metadata">

**Author:** ![Zephyr](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@Zephyr](https://forums.developer.nvidia.com/u/Zephyr)\
**Post date:** [August 19, 2025, 1:14pm UTC](https://forums.developer.nvidia.com/t/crashed-while-building-composer-using-kit-app-template/342457/3 "2025-08-19T13:14:26Z")

</div>

Thank you very much for your reminder, but I tried testing on the C drive and still encountered this error.  
[repo.log](https://forums.developer.nvidia.com/uploads/short-url/reIa0jFkv9hBPQ3B2FGbnvNPZFS.log) (19.6 KB)  
This is the log I tested on the C drive. Could you please help me check it？

（I have also tried testing on other disks and virtual machines.）

---

<div class="post-metadata">

**Author:** ![Richard3D](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/richard3d/32/207062_2.png) [@Richard3D](https://forums.developer.nvidia.com/u/Richard3D)\
**Post date:** [August 19, 2025, 3:48pm UTC](https://forums.developer.nvidia.com/t/crashed-while-building-composer-using-kit-app-template/342457/4 "2025-08-19T15:48:47Z")

</div>

Just checking if you could send me this file, “C:/kit-app-template/\_repo/repo.log”

Also I see that you are running your Packman repo still from the F drive. I would clear that out and clear out the kit app template, and start fresh, putting BOTH of C drive. Do not use any older, previously used Packman Repo folder. Clear out both and start over on the C

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/system/32/68080_2.png) [@system](https://forums.developer.nvidia.com/u/system)\
**Post date:** [September 10, 2025, 1:11am UTC](https://forums.developer.nvidia.com/t/crashed-while-building-composer-using-kit-app-template/342457/5 "2025-09-10T01:11:11Z")

</div>

Closed on September 10, 2025, 1:11am UTC

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
