Closed IgorAlfonso closed 1 year ago
Any update on this issue ? It seems it is still there, also in validation to BC22 version.
@freddydk Bump :)
Sorry, have been crazy busy - will try to get to the bottom of all issues this week.
This is likely because your app has a dependency on aCICatech SOLUCIONES TECNOLOGICAS, SL_Acicatech Access Control_1.0.3.0.app
which needs to be added to Run-AlValidation as installApps.
Hi freddy , is still added look at the script.
Run-AlValidation `
-apps "C:\appsource\NewVersion.app" `
-installapps **"C:\appsource\AccessControl.app"** `
-affixes "AST" `
-countries "es" `
-previousApps "C:\appsource\PreviousVersion.app"
Yeah, I can see that, but somehow that app isn't being recognized. Is that a runtime package? If I am to investigate further, I need a repro - if you can .zip the 3 apps and make them available for me on a onedrive or like to freddyk at microsoft dot com, then I will try and see what happens.
It might be that the app in installApps needs to have the exact name from the compilation
aCICatech SOLUCIONES TECNOLOGICAS, SL_Acicatech Access Control_1.0.3.0.app
Describe the issue
Run-AlValidation is returning error related to ClientServicesCredentialType property not found.
Scripts used to create container and cause the issue
Full output of scripts
1 errors found in NewVersion.app on https://bcartifacts.azureedge.net/sandbox/21.4.52563.53801/es: No se encuentra la propiedad 'ClientServicesCredentialType' en este objeto. Compruebe que existe.
Additional context
Its happening from 2 weeks ago. App submission on appsource is failing also , and no telemetry on appinsights.