[BC 24] `Publish-NAVApp` hangs forever on compilation errors
@PooyaKharamesh is already working on this.
Since Aug 20, 2024.
- Dominant language
- PowerShell
- Stars
- 881
- Forks
- 285
- Avg merge
- 3d 36m
- Merged PRs (30d)
- 1
Description
Please include the following with each issue:
1. Describe the bug
Starting with BC24 Publish-NAVApp no longer shows an error when extension compilation fails but instead hangs forever.
2. To Reproduce
Steps to reproduce the behavior:
- Setup a BC24 container (I used
sandbox-24.0.16410.18981-de) - Publish an app that has a dependency that isn't published yet:
- Observe that
Publish-NAVApphangs foreverPS > Publish-NAVApp -ServerInstance BC -Path C:\azurefileshare\ccr.app -SkipVerification # ... hangs forever ... - Compare that with a BC23 container (I used
sandbox-23.5.16502.19504-w1) which shows the error immediately:PS > Publish-NAVApp -ServerInstance BC -Path C:\azurefileshare\ccr.app -SkipVerification # Publish-NAVApp : Extension compilation failed # error AL1024: A package with publisher 'xxx', name 'xxx', and a version compatible with '2.1.0.0' # could not be loaded. Symbols for the requested app xxx by xxx # 2.1.0.0 could not be found in the database.
Note: Because the developers need to copy and paste the code snippet, including a code snippet as a media file (i.e. .gif) is not sufficient.
3. Expected behavior
Publish-NAVApp should return an error like it did for BC 23.5
4. Actual behavior
Publish-NAVApp hangs forever
5. Versions:
- AL Language: N/A
- Visual Studio Code: N/A
- Business Central: 24.0.16410.18981
- List of Visual Studio Code extensions that you have installed: N/A
Final Checklist
Please remember to do the following:
-
Search the issue repository to ensure you are reporting a new issue
-
Reproduce the issue after disabling all extensions except the AL Language extension
-
Simplify your code around the issue to better isolate the problem
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.