Adobe-Runtime-Support
Adobe-Runtime-Support copied to clipboard
Publisher "UNKNOWN" after upgrade from AIR SDK 32 to 33
We updated the AIR SDK to 33 and placed the license file in the folder. The Publishers shows as UNKONWN in Control Panel. The company certificate is valid and this only happens with AIR 33 SDK build native command. ( Windows 10 )
Also the copyright field is empty:

anyone?
@ajwfrost
Sorry, missed this one earlier! I'll ask someone to take a look, I think there's meant to be a process that sets the .exe file properties appropriately... (there's a possibility though that this may be linked with the generic runtime problem where it can't validate the publisher's certificates - which we've got a fix for now...)
thanks
So should we wait for the next SDK release and test with that?
Hmm... initial feedback here is that the .exe file properties are not being set, but weren't set in AIR 32 either. So, we can look at that but I'm not 100% sure whether the capability would exist in our current toolchain to be able to set those properties.
In terms of the headline issue with the publisher saying it's "UNKNOWN", this is because of the problem I mentioned with certificate validation. So that would be fixed once the next AIR shared runtime has been issued, for any apps that are installed using that..
thanks
@ajwfrost is the fix Publisher UNKNOWN issue fixed in AIR SDK & AIR Shared Runtime Version 33.1.1.932 ? I did not find any mention in the release notes.
We haven't actually published any release notes for build 932 (or 744) - these are basically the same as the earlier versions (929 and 743) but with the one change to sort out the certificate validation..
But yes if you have one of those AIR runtimes installed, and then install a .air app, the publisher details will be shown in the "programs and features" list and you will no longer get the "untrusted" warning when installing.
thanks
@ajwfrost "HARMAN are looking at adapting the previous AIR installer so that it would be possible for the AIR Developer Tool to perform this step, i.e. allowing developers to create installation MSI files for Windows apps in a single step."
Any update on this issue?