localDevEnv.ps1 - fails to find dependency app

[buzzwick]

Running localDevEnv.ps1 for a repo with a dependency on our main app. The script seems to be generating the download URL from the app.json file. But no matter what I put in the app.json, it looks like it is failing to find the app to download symbols from. How/what should I configure so that this script can find the .app file it needs?

Compiling C:\Users\dbaldwin\OneDrive - Computer Associates, Inc. - MBS\Documents_ALPROJECTS\Elemet-Inc\Elemet Custom Mods Copying DLLs from C:\Program Files\Microsoft Dynamics NAV\230\Service to assemblyProbingPath Removing dotnet Framework Assemblies Using Symbols Folder: C:\Users\dbaldwin\OneDrive - Computer Associates, Inc. - MBS\Documents_ALPROJECTS\Elemet-Inc\Elemet Custom Mods.alPackages Processing dependency Microsoft_Application_20.0.0.0 () Dependency App exists Processing dependency Microsoft_System_20.0.0.0 () Dependency App exists Processing dependency CAI Software_CAi Software Precious Metals Solution_22.1.32.0 (8788f8f7-2afb-4cd8-9935-068947847f2a) Downloading symbols: CAI Software_CAi Software Precious Metals Solution_22.1.32.0.app Url : http://172.24.12.126:7049/BC/dev/packages?appId=8788f8f7-2afb-4cd8-9935-068947847f2a&versionText=22.1.32.0&tenant=default Downloading using HttpClient ERROR Exception calling "GetResult" with "0" argument(s): "Response status code does not indicate success: 404 (Not Found)." Compile-AppInBcContainer Telemetry Correlation Id: 1de8ef6a-66f1-4f99-a64f-1a3a5be40c7f Run-AlPipeline Telemetry Correlation Id: 053daebe-0a7a-4c0c-92c8-156ffe63d04e Error: Exception calling "GetResult" with "0" argument(s): "Response status code does not indicate success: 404 (Not Found)." Response status code does not indicate success: 404 (Not Found). Stacktrace: at Compile-AppInBcContainer, C:\ProgramData\BcContainerHelper\6.0.0\BcContainerHelper\AppHandling\Compile-AppInNavContainer.ps1: line 486 at <ScriptBlock>, C:\ProgramData\BcContainerHelper\6.0.0\BcContainerHelper\AppHandling\Run-AlPipeline.ps1: line 779 at <ScriptBlock>, C:\ProgramData\BcContainerHelper\6.0.0\BcContainerHelper\AppHandling\Run-AlPipeline.ps1: line 1894 at <ScriptBlock>, C:\ProgramData\BcContainerHelper\6.0.0\BcContainerHelper\AppHandling\Run-AlPipeline.ps1: line 1441 at <ScriptBlock>, C:\ProgramData\BcContainerHelper\6.0.0\BcContainerHelper\AppHandling\Run-AlPipeline.ps1: line 1434 at <ScriptBlock>, C:\ProgramData\BcContainerHelper\6.0.0\BcContainerHelper\AppHandling\Run-AlPipeline.ps1: line 904 at Run-AlPipeline, C:\ProgramData\BcContainerHelper\6.0.0\BcContainerHelper\AppHandling\Run-AlPipeline.ps1: line 866 at CreateDevEnv, C:\Users\dbaldwin\AppData\Local\Temp\tmp8825.tmp.ps1: line 1844 at <ScriptBlock>, C:\Users\dbaldwin\OneDrive - Computer Associates, Inc. - MBS\Documents_ALPROJECTS\Elemet-Inc.AL-Go\localDevEnv.ps1: line 128 at <ScriptBlock>, <No file>: line 1 PS C:\Users\dbaldwin\OneDrive - Computer Associates, Inc. - MBS\Documents_ALPROJECTS\Elemet-Inc>

[buzzwick]

We did find a workaround--namely to build the container using the same script but in the repo of the dependent app. Then we build against and deploy the extension app to that container. But would still like to know the proper setup for building a container from the subordinate app's local repo.