Open pri-kise opened 10 months ago
We are encountering the same issue on our BC23 builds.
@pri-kise Have you been able to make any headway with this?
No. I didn't found any solution yet.
Can you may be try to sign outside a docker container?
- task: ALOpsAppCompiler@2
inputs:
artifacttype: 'Sandbox'
versionselect: Current
...
- task: ALOpsAppSign@1
inputs:
usedocker: false
batchsigncompiledapps: true
publish_artifact: true
pfx_path: $(pfxurl)
pfx_password: $(pfxpwd)
Tried signing outside docker. Same error:
We assume this has something to do with not having the right version of navsip. We'll see what we can do about that from the sign-step.
I could not get any meaningful information out of this, but here is the signing section of the log for a succeeding build alongside that of a failing build for the same app. The only change in the yml between the two is that we at some point changed the file filter from '.app' to '._APP.app' to see if excluding the runtime app would help (undoing this did not fix anything).
We are going to try to include NavSip.dll in our steps, so there is no confusion.
Describe the bug I currentyl receive always the error The form specified for the subject is not one supported or known by the specified trust provider when trying to sign an app for BC 23.0
the used yaml please provide the yaml that you used. It helps you put the yaml like this:
The File:
The template:
the output Also the complete output is necessary for us to see what is going on. Also use backtics:
Expected behavior The problem seems to be isolated to BC 23 any other pipline for BC21 or BC22 is working fine.
Additional Context I searched in the repository for similiar issues and found only the following one https://github.com/HodorNV/ALOps/issues/681 But I don't know if this is a different issue, since we only have this problem for BC23.
I'd happy for an updated yaml file, if there is anything I can change.