Hi, Readers.
I would like to share a piece of information today because I’ve seen this mentioned by too many people this week, transient failures while running v.24 updates and publishing apps from Visual Studio Code.
Some questions from the Dynamics 365 Community:
Issue while publishing extension
Solved: Per-tenant extension ‘XXX’ version 2.1.0.0 by ‘XXX’ failed to compile.
Cannot start a debug session from VS Code
Yes, starting from about last Thursday, if you publish an extension to the BC24.0 Cloud sandbox environment, the following error will appear.
Or
The extension will be published successfully, but will not be installed.
You can install it manually from the Extension Management page.
Also, if you use Upload Extension action to install the extension, this won’t cause any problems.
So the problem is that it can’t be debugged now.
PS: My version: W1 24.0 (Platform 24.0.18764.0 + Application 24.0.16410.17628)
This is discussed in detail in the AL Issues below.
This Extension cannot be published as it has the same App ID and Version as a previously published Extension · Issue #7721 · microsoft/AL · GitHub
And there is a temporary solution mentioned in the post that you can try.
Suggestion:
For deployment use the Extension Management interface
Just for Debugging, you can add a configuration for Attach in the launch.json, Example below
{
“name”: “Attach: Microsoft cloud sandbox”,
“type”: “al”,
“request”: “attach”,
“environmentType”: “Sandbox”,
“environmentName”: “sandbox”,
“breakOnError”: “All”,
“breakOnRecordWrite”: “None”,
“enableSqlInformationDebugger”: true,
“enableLongRunningSqlStatements”: true,
“longRunningSqlStatementsThreshold”: 500,
“numberOfSqlStatements”: 10,
“breakOnNext”: “WebClient”
}
Then early this morning Japan time, Microsoft released developer news in AL Home.
More details: AL/News.md at master · microsoft/AL · GitHub
2024-04-24 Transient failures while running v.24 updates and publishing apps from Visual Studio Code
AL/News.md at master · microsoft/AL · GitHub
We have identified an issue where publishing apps might sometimes fail due to a race condition in the flow of installing or updating multiple apps, causing certain development operations like app publishing and updates to v. 24 to fail with an internal error. For troubleshooting update issues, see the Operations Log page in the Business Central Admin Center. Here you’ll find the details of the errors discovered during update or app publishing.
We are actively working on identifying the root cause and mitigating the issue.
While we are working on addressing this instability, the issue can be mitigated by re-trying the operation, for example, re-trying app publishing or update, until it succeeds. When deploying PTEs as DEV extensions from Visual Studio code fails, another option is to upload it through the Extension Management page in the web client, and optionally subsequently use debug without publishing if you’re doing debugging.
Please do not open any new, duplicate support cases on above. Communication on this issue is posted under ID DN78455 if you need to refer to that in any existing, related support case.
We will delete this entry when the issue has been resolved.
In the meantime, you can follow or provide details on the GitHub AL issue on deploying through Visual Studio code fails
Just wait patiently for Microsoft to solve the problem and do not submit duplicate support cases.
Share this information with those who need it.
Update 2024-04-29:
2024-04-29 [UPDATE] Transient failures while running v.24 updates and publishing apps from Visual Studio Code
We have released a hotfix for below issue and it has been deployed over the weekend. We have verified that it works. We recognize the impact it has had on AL developers and the publishing story and sincerely apologize for the disruption this issue caused. Unfortunately, the root cause was a race condition caused due to a database configuration change. It was an issue that was very hard to debug and reproduce due to appearing only on specific database configurations and only intermittently, which is why it took so long to fix.
We will keep this entry open for a short time for awareness of the issue being fixed, and then remove the entry
We have identified an issue where publishing apps might sometimes fail due to a race condition in the flow of installing or updating multiple apps, causing certain development operations like app publishing and updates to v. 24 to fail with an internal error. For troubleshooting update issues, see the Operations Log page in the Business Central Admin Center. Here you’ll find the details of the errors discovered during update or app publishing.
We are actively working on identifying the root cause and mitigating the issue.
While we are working on addressing this instability, the issue can be mitigated by re-trying the operation, for example, re-trying app publishing or update, until it succeeds. When deploying PTEs as DEV extensions from Visual Studio code fails, another option is to upload it through the Extension Management page in the web client, and optionally subsequently use debug without publishing if you’re doing debugging.
Please do not open any new, duplicate support cases on above. Communication on this issue is posted under ID DN784551 if you need to refer to that in any existing, related support case.
We will delete this entry when the issue has been resolved.
In the meantime, you can follow or provide details on the GitHub AL issue on deploying through Visual Studio code fails
END
Hope this will help.
Thanks for your reading.
ZHU
コメント