Publish-BCContainerApp on environment fails after upgrade to BC24

Question

Publish-BCContainerApp on environment fails after upgrade to BC24

Closed this issue 5 months ago · 13 comments

PLEASE DO NOT INCLUDE ANY PASSWORDS OR TOKENS IN YOUR ISSUE!!!

Describe the issue
Yesterday we upgraded our test environment to BC24. We have setup a pipeline in devops that uses Publish-BCContainerApp to update the environment with our latest apps from our build pipelines. Since the upgrade the install of every app fails with the following error message:

2024-04-23T08:16:17.9456818Z Installing Apps
2024-04-23T08:16:19.9499400Z Publishing Dynavision_Dynavision Advanced Finance_23.0.8.18655_sandbox_23.1_w1.app to https://api.businesscentral.dynamics.com/v2.0/DynavisionTest/dev/apps?SchemaUpdateMode=forcesync&DependencyPublishingOption=default
2024-04-23T08:16:36.9244284Z Status Code 422 : Unprocessable Entity
2024-04-23T08:16:36.9244892Z Er is geen gepubliceerde extensie die overeenkomt met de opgegeven parameterwaarden.
2024-04-23T08:16:36.9245146Z 
2024-04-23T08:16:37.3597442Z Publish-BcContainerApp Telemetry Correlation Id: 5fc028b7-d7bd-4fc0-b6e0-6c6fe6f5ba00
2024-04-23T08:16:37.3965657Z Status Code 422 : Unprocessable Entity
2024-04-23T08:16:37.3966209Z Er is geen gepubliceerde extensie die overeenkomt met de opgegeven parameterwaarden.
2024-04-23T08:16:37.3967137Z At C:\Program Files\WindowsPowerShell\Modules\BCContainerHelper\6.0.15\AppHandling\Publish-NavContainerApp.ps1:295 
2024-04-23T08:16:37.3967783Z char:25
2024-04-23T08:16:37.3968019Z +                         throw $message
2024-04-23T08:16:37.3968271Z +                         ~~~~~~~~~~~~~~
2024-04-23T08:16:37.3968590Z     + CategoryInfo          : OperationStopped: (Status Code 422...meterwaarden.
2024-04-23T08:16:37.3969194Z :String) [], RuntimeException
2024-04-23T08:16:37.3969940Z     + FullyQualifiedErrorId : Status Code 422 : Unprocessable Entity
2024-04-23T08:16:37.3970535Z Er is geen gepubliceerde extensie die overeenkomt met de opgegeven parameterwaarden.
2024-04-23T08:16:37.3971094Z  
2024-04-23T08:16:37.4673773Z ##[error]PowerShell exited with code '1'.

Scripts used to create container and cause the issue

# Create temporary directory
$TempDirectoryName = [System.IO.Path]::Combine($env:TEMP, [guid]::NewGuid().ToString('N'))
New-Item -ItemType Directory -Path $TempDirectoryName -Force | Out-Null

Write-Host "The following Apps will be published:"
(Get-ChildItem -Path $AppFolder -Filter '*.app' -Recurse) | % {
    Write-Host "$($_.Name) (found in directory '$($_.Directory)')"     
    Copy-Item -Path $_.FullName -Destination $TempDirectoryName
}
   
Write-Host "Installing Apps"
Publish-BcContainerApp `
    -bcAuthContext $AuthContext `
    -environment $Environment `
    -appFile $TempDirectoryName `
    -dependencyPublishingOption default `
    -syncMode ForceSync 

# Remove temporary directory
Remove-Item $TempDirectoryName -Recurse

Full output of scripts
See above

Screenshots
N/A

Additional context
BCContainerHelper fails when executing the API call to BC:

When I inspect the environment after the error, I notice the app is published but not installed. So it appears the install fails. I also noticed it takes a while for the published app the show up in extension management. It seems there's a delay that might cause this error.

On BC23 the update of our test environment was already quite slow (we have 27 apps to publish) but It worked. The environment has quite some companies.

Answer 1 · 2024-04-23T08:44:10.000Z

Does the extension management page reveal what the problem is?

Answer 2 · 2024-04-23T08:47:09.000Z

Does the extension management page reveal what the problem is?

No, nothing is displayed. It takes a while for the published extension to show up and when it does I can install it manually without a problem.

I'm currently updating a copy of our test environment (still on bc23) and it works perfectly fine there.

Answer 3 · 2024-04-23T08:49:10.000Z

are you using s2s or impersonation for deployment?

Answer 4 · 2024-04-23T08:49:55.000Z

Looks like impersonation (dev scope) - right?

Answer 5 · 2024-04-23T08:51:00.000Z

Looks like impersonation (dev scope) - right?

Jep.

Here's the full script:

[CmdletBinding()]
param (
    [Parameter(Mandatory = $true)]
    [string]$AppFolder,    
    [Parameter(Mandatory = $true)]
    [string]$Environment,
    [Parameter(Mandatory = $true)]
    [string]$RefreshToken,
    [Parameter(Mandatory = $false)]
    [array]$PublishedApps,
    [Parameter(Mandatory = $false)]
    [Switch]$PublishTestApps = $false    
)

if (!(Get-Module -ListAvailable -Name 'BcContainerHelper')) { Install-Module BcContainerHelper -Force } 
Import-Module BCContainerHelper

Write-Host "Sorting Apps"
$AppsToInstall = Sort-AppFilesByDependencies -appFiles ((Get-ChildItem -Path $AppFolder -Filter '*.app' -Recurse).FullName)

Write-Host "Retrieving Authentication Context"
$AuthContext = New-BcAuthContext -refreshToken $RefreshToken

foreach ($App in $AppsToInstall) {
    $AppFileNameSplitted = [System.IO.Path]::GetFileName($App).Split("_")
    $Publisher = $AppFileNameSplitted[0]
    $Name = $AppFileNameSplitted[1]
    $Version = $AppFileNameSplitted[2]

    if ((-not $PublishTestApps) -and ($Name -like "*-test*")) { continue }

    $PublishedApp = $PublishedApps | Where-Object { ($_.publisher -eq $Publisher) -and ($_.displayName -eq $Name) }
    if ($null -ne $PublishedApp) {
        $PublishedAppVersion = "$($PublishedApp.versionMajor).$($PublishedApp.versionMinor).$($PublishedApp.versionBuild).$($PublishedApp.versionRevision)"
        if ($Version -eq $PublishedAppVersion) { 
            Write-Host "App $Name with version $Version for publisher $Publisher already installed" -ForegroundColor Yellow
            Remove-Item -Path $App
        }
    }
}

$bcContainerHelperConfig.NoOfSecondsToSleepAfterPublishBcContainerApp = 5

# Create temporary directory
$TempDirectoryName = [System.IO.Path]::Combine($env:TEMP, [guid]::NewGuid().ToString('N'))
New-Item -ItemType Directory -Path $TempDirectoryName -Force | Out-Null

Write-Host "The following Apps will be published:"
(Get-ChildItem -Path $AppFolder -Filter '*.app' -Recurse) | % {
    Write-Host "$($_.Name) (found in directory '$($_.Directory)')"     
    Copy-Item -Path $_.FullName -Destination $TempDirectoryName
}
   
Write-Host "Installing Apps"
Publish-BcContainerApp `
    -bcAuthContext $AuthContext `
    -environment $Environment `
    -appFile $TempDirectoryName `
    -dependencyPublishingOption default `
    -syncMode ForceSync 

# Remove temporary directory
Remove-Item $TempDirectoryName -Recurse

Answer 6 · 2024-04-23T08:51:03.000Z

Could you try this:

Replace-DependenciesInAppFile -Path $appFile -replacePackageId

before publishing the app?

Answer 7 · 2024-04-23T08:54:53.000Z

Could you try this:
Replace-DependenciesInAppFile -Path $appFile -replacePackageId
before publishing the app?

I'll get back to you about that in a bit. We are currently copying the bc24 environment to an environment with a new name and restoring our bc23 test environment.

Answer 8 · 2024-04-23T09:32:37.000Z

Replace-DependenciesInAppFile -Path $appFile -replacePackageId

I'm afraid this doesn't help.

WARNING: The names of some imported commands from the module 'BCContainerHelper' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
Attempting authentication to https://api.businesscentral.dynamics.com/user_impersonation offline_access using refresh token...
Authenticated using refresh token as user ...
Authenticated to common, using tenant id ...
Replacing Package ID with new GUID
Replacing Package ID with new GUID
Replacing Package ID with new GUID
Publishing Dynavision_Dynavision Advanced Finance_23.0.8.18655_sandbox_23.1_w1.app to https://api.businesscentral.dynamics.com/v2.0/DynavisionDEV/dev/apps?SchemaUpdateMode=forcesync&DependencyPublishingOption=default
Status Code 422 : Unprocessable Entity
Er is geen gepubliceerde extensie die overeenkomt met de opgegeven parameterwaarden.

Publish-BcContainerApp Telemetry Correlation Id: 7dec0997-a498-41f2-9a98-065e920e5ed7
Status Code 422 : Unprocessable Entity
Er is geen gepubliceerde extensie die overeenkomt met de opgegeven parameterwaarden.
At C:\Program Files\WindowsPowerShell\Modules\BCContainerHelper\6.0.15\AppHandling\Publish-NavContainerApp.ps1:295 char:25
+                         throw $message
+                         ~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (Status Code 422...meterwaarden.
:String) [], RuntimeException
    + FullyQualifiedErrorId : Status Code 422 : Unprocessable Entity
Er is geen gepubliceerde extensie die overeenkomt met de opgegeven parameterwaarden.

After the error above was thrown I checked the environment and the app was published but not installed:

It took over a minute for the app to show op in extension management. So it really looks like for some reason the publish has not completed yet when an attempt is made to install the app.

Answer 9 · 2024-04-23T09:35:46.000Z

I have a repro of this - will investigate why this happens.

Answer 10 · 2024-04-23T09:40:54.000Z

I have a repro of this - will investigate why this happens.

Thx! In the meantime we've restored our environment to BC23. We still have a copy of the BC24 environment for investigating the issue.

Answer 11 · 2024-04-23T12:02:26.000Z

It looks like this problem is in the service and also happens from VS Code - we have people investigating

Answer 12 · 2024-04-23T19:13:56.000Z

microsoft/AL#7721

Answer 13 · 2024-04-26T10:06:26.000Z

This should be fixed now