What is the expected outcome for the following scenario to create then update an Air application?
1. Using Flash Builder 4.7, Flex 4.12, with Air 3.1, create an .air distributable file, using a self-signed certificate that I have Flash Builder create during the packaging process (e.g. Export Release Build). I'm also using ApplicationUpdaterUI() for Air to manage the update process. 2. Install the application on my computer. 3. Update the application and repeat step 1 (incrementing versionNumber as needed, and moving it to my web server, along with update.xml). 4. Run the installed application on my computer, and see the Updater window appear. 5. Click to update the application... Is the update expected to fail because the self-signed certificate was created new in both steps 1 and 3 by Flash Builder (and updates must use the same certificate?)? If so, what is the expected error (number)? Also, I've tried to use my own self-signed code-signing certificate that I created outside Flash Builder, so that the same certificate is used to build each application, but Flash Builder always complains "Unable to build a valid certificate chain for the signer". I created my own CA and signed it, and still same error. I also tried exporting the entire certificate chain path into the certificate, and still same error. Has anyone succeeded in using a self-signed certificate to test the ApplicationUpdaterUI() auto-update process? I wonder if I'm trying to test something that was not intended for me to test (in development).
