David Baldwin

Now we can reproduce the scenarios I described earlier: An attempt to deploy a _later_ version (minor version increment) fails due to authentication failure. A successive attempt to deploy the...

All of these environments are Sandbox--we are currently not deploying to any Production environments. All use RefreshToken (New-BcAuthContext); it is only the UAT, JMSandbox and JMDEV that have expirations on...

Some more examples of this sequence; I am pretty sure that a failed publish "pulls" (as in it disappears from the Extension Management list) the installed version of the app,...

Thank you. That will be a great relief, because our client is breathing down our necks to have "stable" environments and deployments. In the meantime--so far I have not discovered...

More data: Log below records a session where an "unprocessable entity" error definitely uninstalled the DEV app from the target environment. [unprocessable entity (2).zip](https://github.com/microsoft/AL-Go/files/14185793/unprocessable.entity.2.zip) And for the record: an immediate...

Updated the system files and ran a CI/CD (builds from the AL-Go update failed; I had to remove our codesigning flags because that's not working yet). But that failure did...

I will try to be as diligent as possible about tracking what happens, and will post logs. We have several other clients with sandbox environments that we are deploying to,...

Would love to see this as a feature or at least an option.

> Will look into this. > > BTW - one way to make your development branch keep artifacts is to setup continuous deployment to a QA environment. Then it will...

We did find a workaround--namely to build the container using the same script but in the repo of the dependent app. Then we build against and deploy the extension app...