Closed vejbalzer closed 3 days ago
We have seen this issue, also, with a quite a few .app files in 25.0.23170.0.
Here is a screendump of the result of trying to reformat SymbolReference.json from artefact downloaded file C:\bcartifacts.cache\sandbox\25.0.23170.0\dk\Extensions\Microsoft_Transactions and Receipts Storage_25.0.23170.0.app
.
The part in the red square looks like the end of a normal SymbolReference.json file.
Maybe SymbolReference.json was written with File.OpenWrite (which by default does not truncate if the file already exists) at a time when there is a bigger SymbolReference.json from a previous build (unclean workspace)?
I have the same issue when I was working for the BaseApp with version 25.0.23212.0 The symbol reference of the System Application is wrong: SymbolReference.json
I suspect we also are experiencing issues from this. We get weird error messages like error AL0281: Object member '<EventPublisherName>' is not an event.
when having an event subscriber to an event publisher for which nothing has changed. The target procedure is actually an event publisher.
The fix for this issue has been checked in to the master branch. It will be available in the bcinsider.azurecr.io/bcsandbox-master Docker image starting from platform build number 26.0.23829.0 and VS Code Extension Version 15.0.1128421.
If you don’t have access to these images you need to become part of the Ready2Go program: aka.ms/readytogo
For more details on code branches and docker images please read: https://blogs.msdn.microsoft.com/nav/2018/05/03/al-developer-previews-multiple-releases-and-github/ https://freddysblog.com/2020/06/25/working-with-artifacts/
Will the fix will be available in BC25, VS Code Extension version 14 also?
Please include the following with each issue:
1. Describe the bug When creating an app package e.g. with the "AL: Package" command, the generated app file contains a SymbolReference.json file with invalid JSON. It seems like the content is doubled, compared to how it should be. For example it looks like this:
2. To Reproduce Steps to reproduce the behavior:
3. Expected behavior SymbolReference.json contains valid JSON
4. Actual behavior SymbolReference.json contains doubled content which leads to invalid JSON
5. Versions:
Final Checklist
Please remember to do the following:
[x] Search the issue repository to ensure you are reporting a new issue
[x] Reproduce the issue after disabling all extensions except the AL Language extension
[x] Simplify your code around the issue to better isolate the problem
Internal work item: AB#545880