Closed buzzwick closed 8 months ago
We now know why - but it is a strange error - will check why
Just noting that we still get this error, after you fixed the "AuthTokenSecret" for appDependencyProbingPaths
In which repo? I don't see that error in the Element repo?
Sorry, I keep jumping back and forth between these two extension repos, because the errors were coming up interchangeably.
This would be the most recent CI/CD run in https://github.com/CAI-Software-Inc/Johnson-Matthey-UK
Yeah, so the reason for the error is that it tries to download a dependency, which isn't installed (very bad error message) In this repo, it cannot find: Johnson Matthey_JM-CAI Extension_1.0.0.0.app - is that in a different repo?
I found the root cause of the strange error message and there is a fix for this in a future version. In the future, the error message should look like:
Aha! No, that dependency is not in fact in this repo. Or any repo that we have access to, so far as I know. It turns out that our client is developing their own extension separately; I listed the dependency anticipating our extension relying on fields/tables in their extension. But of course there is no way to compile them together. I will have to remove that reference for now, but I wonder what happens if we do have to include, say, a symbol reference that they have added? A little hazy on that particular situation.
Hoorah for the new error message! That should speed things up enormously and avoid a lot of New Issues!
During a build after merging a pull request, we get this error when trying to download symbols for the named dependent app. Because this app will not build, then a Publish to Environment cannot find any build artifacts. So we need to understand how to get an app with a dependency to build in its own repository.
Going back to the Workshop files on Dependencies, to see if this is covered there.