Hi folks,
I am encountering a very weird issue while uploading and scheduling a customized extension (new version: 1.0.0.38) in our production environment for the next minor update: the upload failed and the error message is /Deploy Operation rejected. Error: The application extension with app id 'xxx' cannot be staged for future deployment because there is no existing deployed version to upgrade from./
This is weird because a previous version (which is 1.0,0.37) of the extension has been successfully installed in our business central tenant. When we set the version number of the .app package back to 1.0.0.37 and tried to schedule this version to the next minor update, we have got another error message stating: An extension with app Id 'xxx' and version at least '1.0.0.37' is already installed on this environment
The newer version of the extension 1.0.0.38 contains the newest symbols of the next minor version (which we have downloaded from our test environment that has been updated recently to the newest minor version 22.3).
The production environment is currently at 22.2 and should be upgraded to 22.3 soon.
I have also inquired our business central partners but unfortunately, they couldn't help us with this issue.
Could someone please give me a hint why the scheduling fails? (without deleting the extension manually shortly before the next scheduled update window).
Thanks!!
