Closed MortenRa closed 11 months ago
Hi,
did you check the version under properties? We also noticed the same error, but we ARE updating the version, and you'll see under properties that the version is indeed correct, but the error message is wrong. Not sure what to do about that.
If we simply open the offering, and press "review and publish" / "publish" - it does pick up the updated version...
About the library-filename - in our case, there are about 10 apps in the zipfile - so there isn't really a "filename" to use. So we simply used the same app, but with .zip as extension, which kind of indicates the collection.
I'll talk to development...
yes you are right the version are correct, to bad it errors out.
About the library-filename maybe just give it name as library apps.zip (we also have a few for some apps)
What about the -autoPromote is that supported so I can avoid going into appsource and press Go-live if the validation goes well.
We'll see what we can do - not sure if this will circumvent that error though ..
any luck in solving the problem with the error issue
Ayn updates on this issue
We are still investigating - we are bother with this as well :(.
-autoPromote doesn't help, because the validate already fails (which is a step before promote).
We have the same problem now that we try to automate the AppSource submission via the ALOpsAppSource task. We keep getting the error message, that the version number of the offering and the app.json don't match.
##[section]Starting: ALOps AppSource
==============================================================================
Task : ALOps AppSource
Description : Compile AL Extensions for Business Central
Version : 1.459.4971
Author : Hodor
Help : Compile a Business Central extension from AL code.
==============================================================================
*** Validate configuration
*** Task Inputs:
name value
---- -----
azure_tenant_id ***
azure_app_client_id ***
azure_app_client_secret ***
*** For documentation, please visit : https://www.alops.be/documentation
*** Importing required PS-Functions
*** Load Management DLL's
*** Import NAV/BC Management DLL's [False]
*** ServiceTier not specified, loading default assemblies.
*** Default Assemblies not found. Load via BC-Artifacts
*** Install/Update BCContainerHelper [https://github.com/microsoft/navcontainerhelper]
*** Check BcContainerHelper
*** Load BcContainerHelper
BcContainerHelper version 6.0.0
BC.HelperFunctions emits usage statistics telemetry to Microsoft
ModuleType Version Name ExportedCommands
---------- ------- ---- ----------------
Script 6.0.0 BcContainerHelper {Add-FontsToBcContainer, Add-GitToAlProjectFolder, AddTele...
##[command]"Get-BCArtifactUrl"
Name Value
---- -----
select Latest
type OnPrem
country W1
-select: Latest -type: OnPrem -country: W1
*** Platform: C:\bcartifacts.cache\onprem\23.0.12034.12841\platform
*** Localisation: C:\bcartifacts.cache\onprem\23.0.12034.12841\w1
*** BC Management DLL: C:\bcartifacts.cache\onprem\23.0.12034.12841\platform\ServiceTier\program files\Microsoft Dynamics NAV\230\Service\Management\Microsoft.Dynamics.Nav.Management.dll
*** Selected module: [C:\bcartifacts.cache\onprem\23.0.12034.12841\platform\ServiceTier\program files\Microsoft Dynamics NAV\230\Service\Management\Microsoft.Dynamics.Nav.Management.dll]
*** Loading module: [C:\bcartifacts.cache\onprem\23.0.12034.12841\platform\ServiceTier\program files\Microsoft Dynamics NAV\230\Service\Management\Microsoft.Dynamics.Nav.Management.dll]
*** BC App Management DLL: C:\bcartifacts.cache\onprem\23.0.12034.12841\platform\ServiceTier\program files\Microsoft Dynamics NAV\230\Service\Management\Microsoft.Dynamics.Nav.Apps.Management.dll
*** Selected module: [C:\bcartifacts.cache\onprem\23.0.12034.12841\platform\ServiceTier\program files\Microsoft Dynamics NAV\230\Service\Management\Microsoft.Dynamics.Nav.Apps.Management.dll]
*** Loading module: [C:\bcartifacts.cache\onprem\23.0.12034.12841\platform\ServiceTier\program files\Microsoft Dynamics NAV\230\Service\Management\Microsoft.Dynamics.Nav.Apps.Management.dll]
*** Load CodeAnalysis from [C:\bcartifacts.cache\onprem\23.0.12034.12841\platform\ServiceTier\program files\Microsoft Dynamics NAV\230\Service\Management]
*** Loading assemblies from: [C:\bcartifacts.cache\onprem\23.0.12034.12841\platform\ServiceTier\program files\Microsoft Dynamics NAV\230\Service\Management]
*** Loading: [C:\bcartifacts.cache\onprem\23.0.12034.12841\platform\ServiceTier\program files\Microsoft Dynamics NAV\230\Service\Management\Microsoft.Dynamics.Nav.CodeAnalysis.dll]
*** Check Powershell Module [AZ]
*** Install Powershell Module [AZ]
*** Request OAuth token for [api.partner.microsoft.com]
* Client ID: ***
*** Fetch Offering-Data from [api.partner.microsoft.com]
*** Offerings found:
resourceType name externalIDs isModularPublishing id
------------ ---- ----------- ------------------- --
AzureDynamics365BusinessCentral My App {@{type=AzureOfferId; value=my-app}} True 00000000-0...
*** Discover available .app files
*** Read App Manifest: [C:\agent\_work\1530\a\Some Company_My App_1.2.38134.0.app].
*** Read App Manifest: [C:\agent\_work\1530\a\Some Company_License Module_1.1.38072.0.app].
*** App Manifests [2]:
Path AppId
---- -----
C:\agent\_work\1530\a\Some Company_My App_1.2.38134.0.app 00000000-000...
C:\agent\_work\1530\a\Some Company_License Module_1.1.38072.0.app 00000000-000...
*** Unique App Manifests in latest version [2]:
Path AppId
---- -----
C:\agent\_work\1530\a\Some Company_My App_1.2.38134.0.app 00000000-000...
C:\agent\_work\1530\a\Some Company_License Module_1.1.38072.0.app 00000000-000...
*** Offering: My App
* Id : 00000000-0000-0000-0000-000000000000
* Name: My App
* Path: C:\agent\_work\1530\a\Some Company_My App_1.2.38134.0.app
* Dependencies: 2
* License Module
*** Offering: My App
* Id : 00000000-0000-0000-0000-000000000000
* Name: My App
* Path: C:\agent\_work\1530\a\Some Company_My App_1.2.38134.0.app
* Dependencies: 1
* License Module
*** Prepare release
* My App (ZIP Dependencies)
*** Set App versions
Verzeichnis: C:\agent\_work\1530\a
Mode LastWriteTime Length Name
---- ------------- ------ ----
d----- 13.10.2023 20:30 Release
resourceType industries categories additionalCategories submissionVersion productTags appVersion useEnterpriseContrac
t
------------ ---------- ---------- -------------------- ----------------- ----------- ---------- --------------------
AzureProperty {} {} {} {} 1.2.38127.0 False
##[warning]Upcoming breaking changes in the cmdlet 'New-AzStorageContext' :
is changing.
S token in created Storage context properties 'ConnectionString' and 'StorageAccount.Credentials' won't have the leading question mark '?' in a future release.
ake effect in Az version : '11.0.0'
ake effect in Az.Storage version : '6.0.0'
zps-changewarnings for steps to suppress this breaking change warning, and other information on breaking changes in Azure PowerShell.
resourceType : Dynamics365BusinessCentralAddOnExtensionPackage
fileName : Some Company_My App_1.2.38134.0.app
fileSasUri : *sanitized*
state : PendingUpload
@odata.etag : "00000000-0000-0000-0000-000000000000"
id : 00000000-0000-0000-0000-000000000000
resourceType : Dynamics365BusinessCentralAddOnLibraryExtensionPackage
fileName : Some Company_My App_1.2.38134.0.zip
fileSasUri : *sanitized*
state : PendingUpload
@odata.etag : "00000000-0000-0000-0000-000000000000"
id : 00000000-0000-0000-0000-000000000000
##[warning]Upcoming breaking changes in the cmdlet 'New-AzStorageContext' :
is changing.
S token in created Storage context properties 'ConnectionString' and 'StorageAccount.Credentials' won't have the leading question mark '?' in a future release.
ake effect in Az version : '11.0.0'
ake effect in Az.Storage version : '6.0.0'
zps-changewarnings for steps to suppress this breaking change warning, and other information on breaking changes in Azure PowerShell.
resourceType : Submission
state : InProgress
substate : InDraft
targets : {@{type=Scope; value=Preview}}
resources : {@{type=Availability; value=00000000-0000-0000-0000-000000000000}, @{type=Listing;
value=00000000-0000-0000-0000-000000000000}, @{type=Package;
value=00000000-0000-0000-0000-000000000000}, @{type=Property;
value=00000000-0000-0000-0000-000000000000}...}
publishedTimeInUtc : 1601-01-01T00:00:00Z
pendingUpdateInfo : @{updateType=Create; status=Running}
releaseNumber : 9
friendlyName : Submission 9
areResourcesReady : True
id : 0
*** Cleanup VSTS Environment: True
##[section]Finishing: ALOps AppSource
With New-AppSourceSubmission the same App works fine.
New-AppSourceSubmission `
-authContext $authContext `
-productId "00000000-0000-0000-0000-000000000000" `
-appFile "Some Company_My App_1.2.38139.0.app" `
-libraryAppFiles "Some Company_My App_1.2.38139.0.Lib.zip" `
-silent `
-autoPromote `
-doNotWait
GET https://api.partner.microsoft.com/v1.0/ingestion/products/00000000-0000-0000-0000-000000000000
GET https://api.partner.microsoft.com/v1.0/ingestion/products/00000000-0000-0000-0000-000000000000/setup
GET https://api.partner.microsoft.com/v1.0/ingestion/products/00000000-0000-0000-0000-000000000000/submissions
GET https://api.partner.microsoft.com/v1.0/ingestion/products/00000000-0000-0000-0000-000000000000/submissions/0
GET https://api.partner.microsoft.com/v1.0/ingestion/products/00000000-0000-0000-0000-000000000000/branches/getByModule(module=Package)
Extracting C:\Users\user\Desktop\Some Company_My App_1.2.38139.0.app
GET https://api.partner.microsoft.com/v1.0/ingestion/products/00000000-0000-0000-0000-000000000000/packageConfigurations/getByInstanceID(instanceID=00000000-0000-0000-0000-000000000000)
POST https://api.partner.microsoft.com/v1.0/ingestion/products/00000000-0000-0000-0000-000000000000/packages
{
"fileName": "Some Company_My App_1.2.38139.0.app",
"resourceType": "Dynamics365BusinessCentralAddOnExtensionPackage"
}
WARNUNG: Upcoming breaking changes in the cmdlet 'New-AzStorageContext' :
- The parameter : 'SasToken' is changing.
- Change description : The SAS token in created Storage context properties 'ConnectionString' and 'StorageAccount.Credentials' won't have the leading question mark '?'
in a future release.
- The change is expected to take effect in Az version : '11.0.0'
- The change is expected to take effect in Az.Storage version : '6.0.0'
Note : Go to https://aka.ms/azps-changewarnings for steps to suppress this breaking change warning, and other information on breaking changes in Azure PowerShell.
PUT https://api.partner.microsoft.com/v1.0/ingestion/products/00000000-0000-0000-0000-000000000000/packages/00000000-0000-0000-0000-000000000000
{
"id": "00000000-0000-0000-0000-000000000000",
"fileName": "Some Company_My App_1.2.38139.0.app",
"fileSasUri": *sanatized*,
"resourceType": "Dynamics365BusinessCentralAddOnExtensionPackage",
"state": "Uploaded",
"@odata.etag": "\"0900fb46-0000-0800-0000-6529a6790000\""
}
PUT https://api.partner.microsoft.com/v1.0/ingestion/products/00000000-0000-0000-0000-000000000000/packageConfigurations/00000000-0000-0000-0000-000000000000
{
"resourceType": "Dynamics365BusinessCentralPackageConfiguration",
"@odata.etag": "\"00000000-0000-0000-0000-000000000000\"",
"packageType": "AddOn",
"id": "00000000-0000-0000-0000-000000000000",
"packageReferences": [
{
"value": "00000000-0000-0000-0000-000000000000",
"type": "Dynamics365BusinessCentralAddOnLibraryExtensionPackage"
},
{
"value": "00000000-0000-0000-0000-000000000000",
"type": "Dynamics365BusinessCentralAddOnExtensionPackage"
}
]
}
GET https://api.partner.microsoft.com/v1.0/ingestion/products/00000000-0000-0000-0000-000000000000/branches/getByModule(module=Property)
GET https://api.partner.microsoft.com/v1.0/ingestion/products/00000000-0000-0000-0000-000000000000/properties/getByInstanceID(instanceID=00000000-0000-0000-0000-000000000000)
PUT https://api.partner.microsoft.com/v1.0/ingestion/products/00000000-0000-0000-0000-000000000000/properties/00000000-0000-0000-0000-000000000000
{
"resourceType": "AzureProperty",
"hideKeys": [
],
"categories": [
],
"leveledCategories": {
"Finance": [
"compliance-risk-management",
"credit-collections"
],
"Productivity": [
"document-management"
]
},
"extendedProperties": [
],
"@odata.etag": "\"00000000-0000-0000-0000-000000000000\"",
"useEnterpriseContract": false,
"globalAmendmentTerms": "",
"id": "00000000-0000-0000-0000-000000000000",
"leveledIndustries": {
},
"termsOfUse": "",
"applicableProducts": [
],
"industries": [
],
"productTags": [
],
"marketingOnlyChange": false,
"additionalCategories": [
],
"appVersion": "1.2.38139.0",
"submissionVersion": "",
"customAmendments": [
]
}
POST https://api.partner.microsoft.com/v1.0/ingestion/products/00000000-0000-0000-0000-000000000000/submissions
{
"resources": [
{
"type": "Package",
"value": "00000000-0000-0000-0000-000000000000"
},
{
"type": "Property",
"value": "00000000-0000-0000-0000-000000000000"
}
],
"targets": [
{
"type": "Scope",
"value": "preview"
}
],
"resourceType": "SubmissionCreationRequest"
}
Automated validation.........
@waldo1001 I think I have found the problem. You are updating the version number in the offer, but it looks like you haven't published the Properties like BCContainerHelper does.
If I publish it with all the changes, it works.
Thanks for this - we'll look into BCCH again to try to reverse-engineer what he is doing different.
any update on this issue
@MortenRa It works with version 1.461 released today. 🥳
Yes works fine, I close this issue
Describe the bug Using Alops Appsource task to submit to appsource, release pipeline runs fine but this not update offer description version properties to the version I´m uploading to appsource.
further more it names to library extension package file as the extension package file under Technical configuration, I would suggest to name it as the library app extension name(as it is another file)
The manifest property 'version' of the extension 'Use Dynamics' by 'Abakion' (version '22.0.202313.60408') specifies '22.0.202313.60408' while the offer description specifies '22.0.202313.60335'. Update the extension's manifest (app.json) or the offer description. For more information about the Technical Validation for the AppSource marketplace, see https://aka.ms/CheckBeforeYouSubmit.
the used yaml please provide the yaml that you used. It helps you put the yaml like this:
the output
Expected behavior Expected to update the version from our app in app.json so they correnspondence