SignTool Timestamp Files - Signature index changes at runtime

FinalBuilder Bugs
1

This is a funky one. I have used the doublesign example target previously posted here to facilitate dual SHA1/SHA256 signing, except I have added a list iterator at the top to hardcode the list of files being signed. Now, what happens is that the first iteration doublesigns and double timestamps perfectly. On the second iteration, the timestamp operation fails, because the Signature Index value of the action has mysteriously changed from 1 to 2??

I’m sending the project via email.

2

What version of FinalBuilder 8 are you using at present?

3

The newest one available at the time the report was made.

4

Hi Eivind,

We haven’t seen an email from you at this time. Would you be able to resend the project? Thank you.

5

Here’s the email subject, returned from you: RE: (Case 151923) File for issue

6

Ah… case closed. I should have read the original script comments; it is WAD.