I was encountering an invalid manifest cache issue that was resulting in the following error:
JIT session error: Symbols not found
It seems that it would be cleaner to keep the manifest cache in the local project directory
I ran into this issue on CI and can't reproduce it locally...
Loading and constructing the graph
It might take a while if the cache is empty
The 'swift' command exited with error code 255 and message:
JIT session error: Symbols not found: [ _$s18ProjectDescription18FileHeaderTemplateO0aB7HelpersE13companyCopyrightACvau ]
Failed to materialize symbols: { (main, { _$s18ProjectDescription9WorkspaceV4name8projects7schemes18fileHeaderTemplate15additionalFiles17generationOptionsACSS_SayAA4PathVGSayAA6SchemeVGAA04FilehI0OSgSayAA0P7ElementOGAC010GenerationM0VtcfcfA4_, _symbolic Say_____G 18ProjectDescription14TestingOptionsV, ___swift_allocate_value_buffer, _$s18ProjectDescription14TestingOptionsVACs10SetAlgebraAAWL, _$sSa12_endMutationyyF, _main, _symbolic _____16codeCoverageMode______14testingOptions_____Sg12testLanguageSSSg0F6Region_____Sg0F19ScreenCaptureFormatt 18ProjectDescription9WorkspaceV17GenerationOptionsV013AutogeneratedC7SchemesO16CodeCoverageModeO AA07TestingE0V AA14SchemeLanguageV AA19ScreenCaptureFormatO, _$s9Workspace9workspace18ProjectDescriptionAAVvp, _got.$s18ProjectDescription18FileHeaderTemplateOMn, _$sSay18ProjectDescription14TestingOptionsVGSayxGSTsWL, _symbolic _____Sg 18ProjectDescription18FileHeaderTemplateO, _got.$s18ProjectDescription9WorkspaceV17GenerationOptionsV013AutogeneratedC7SchemesO16CodeCoverageModeOMn, _$sSa22_allocateUninitializedySayxG_SpyxGtSiFZ18ProjectDescription6SchemeV_Tgmq5, _$s18ProjectDescription14TestingOptionsVACs10SetAlgebraAAWl, _$sSa22_allocateUninitializedySayxG_SpyxGtSiFZ18ProjectDescription11FileElementO_Tgmq5, __swift_FORCE_LOAD_$_swiftDispatch_$_Workspace, _$sSa22_allocateUninitializedySayxG_SpyxGtSiFZ18ProjectDescription14TestingOptionsV_Tgmq5, _$s18ProjectDescription18FileHeaderTemplateOSgMD, __swift_FORCE_LOAD_$_swiftDarwin_$_Workspace, __swift_FORCE_LOAD_$_swiftFoundation_$_Workspace, ___swift_instantiateConcreteTypeFromMangledNameAbstract, __swift_FORCE_LOAD_$_swiftIOKit_$_Workspace, __swift_FORCE_LOAD_$_swiftCoreFoundation_$_Workspace, ___swift_instantiateConcreteTypeFromMangledName, __swift_FORCE_LOAD_$_swiftXPC_$_Workspace, __swift_FORCE_LOAD_$_swiftObjectiveC_$_Workspace, _$s18ProjectDescription9WorkspaceV4name8projects7schemes18fileHeaderTemplate15additionalFiles17generationOptionsACSS_SayAA4PathVGSayAA6SchemeVGAA04FilehI0OSgSayAA0P7ElementOGAC010GenerationM0VtcfcfA3_, _symbolic _____Sg 18ProjectDescription7VersionV, _$ss27_finalizeUninitializedArrayySayxGABnlF, _$sSay18ProjectDescription14TestingOptionsVGSayxGSTsWl, _got.$s18ProjectDescription7VersionVMn, _$s18ProjectDescription9WorkspaceV17GenerationOptionsV013AutogeneratedC7SchemesO16CodeCoverageModeO04codeiJ0_AA07TestingE0V07testingE0AA14SchemeLanguageVSg04testO0SSSg0P6RegionAA19ScreenCaptureFormatOSg0prsT0tMD, _got.$s18ProjectDescription14TestingOptionsVMn, _$s18ProjectDescription7VersionVSgMD, _$s18ProjectDescription9WorkspaceV4name8projects7schemes18fileHeaderTemplate15additionalFiles17generationOptionsACSS_SayAA4PathVGSayAA6SchemeVGAA04FilehI0OSgSayAA0P7ElementOGAC010GenerationM0VtcfcfA1_, _$sSay18ProjectDescription14TestingOptionsVGMD, ___swift_project_value_buffer, _$s18ProjectDescription7VersionVSgWOh, _got.$s18ProjectDescription14SchemeLanguageVMn, _got.$s18ProjectDescription19ScreenCaptureFormatOMn }) }
What happened?
I was encountering an invalid manifest cache issue that was resulting in the following error:
JIT session error: Symbols not foundRemoving the
~/.cache/Manifestsand~/.cache/ProjectDescriptionHelpersfolders solved the problem.It seems that it would be cleaner to keep the manifest cache in the local project directory
How do we reproduce it?
I ran into this issue on CI and can't reproduce it locally...
Error log
macOS version
14
Tuist version
4.11.0
Xcode version
15.3