Closed RodrigoPuelma closed 2 months ago
It is out in the wild, but takes time to reach all environments - some people had it earlier (see answers above saying all is okay, others like me were a couple of hours later etc. I'd imagine it won't take long to propogate, but generally the guide rule of thumb seems to be 24 hours.
Does anyone know the version number(s) for the hotfix?
Admin Center says my environment is Up to Date, but it has the same publishing problem as last week.
I do not think version number is changing with the fix. I have 24.0.16410.17628 that had the error and is working now.
fix is still not available....
I am still seeing the issue with this reason while publishing from VS code
failed with code UnprocessableEntity. Reason: This Extension cannot be published as it has the same App ID and Version as a previously published Extension.
If this is still your error message, then you need to increase the version number in app.json.
fix is still not available....
failed with code UnprocessableEntity. Reason: Sequence contains more than one element
I am seeing this message now.
fix is still not available....
failed with code UnprocessableEntity. Reason: Sequence contains more than one element
I am seeing this message now.
I cleared alpackages and cache, then downloaded symbols from the updated environment. After that mine worked.
Hi @RodrigoPuelma
Why is the status of this issue Closed? People are still getting errors...
fix is still not available....
failed with code UnprocessableEntity. Reason: Sequence contains more than one element I am seeing this message now.
I cleared alpackages and cache, then downloaded symbols from the updated environment. After that mine worked.
Thanks but still not working... I think fix has not been released yet for some region.
they have already replied that they are working on it, there is no point in writing anymore.
@RSMNishant
Hi @RodrigoPuelma Why is the status of this issue Closed? People are still getting errors...
Please refer to the previous reply here:
https://github.com/microsoft/AL/issues/7721#issuecomment-2082288284
It is the policy of this repository to close issues once a fix has been planned for release. People with the updated BC platform version are reporting being unblocked., so please be patient as we safely release the fix in stages.
My problem didnt solve with your solution and code cop my problem was with the fact that the network drive we used to open project wasnt mapped as a network drive on my pc i just opened the folder on the network without mapping it . The solution was so easy just mapping the network drive ! Solution page : https://www.365cycle.nl/dynamics/an-application-object-of-type-x-is-already-declared/
Please include the following with each issue:
1. Describe the bug When trying to publish an extension via VS Code to a clean sandbox, I get the following error:
"The request for path [] failed with code UnprocessableEntity. Reason: This Extension cannot be published as it has the same App ID and Version as a previously published Extension."
The sandbox is created in a tenant where the Production environment has current version 23.5.16502.16589 while the sandbox is created with the next version 24.0.16410.17628.
The extension versions are different as we are trying to do some testing for the next version of Business Central. This has never been an issue before.
2. To Reproduce
3. Expected behavior No errors when publishing app via VS Code.
4. Actual behavior Error message: "The request for path [] failed with code UnprocessableEntity. Reason: This Extension cannot be published as it has the same App ID and Version as a previously published Extension."
5. Versions: AU Business Central 24.0 (Platform 24.0.18532.0 + Application 24.0.16410.17628)
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