Warning: include() [function.include]: Unable to access /var/www/html/rogue-development/blog2/wp-content/advanced-cache.php in /var/www/html/rogue-development/blog2/wp-settings.php on line 62

Warning: include(/var/www/html/rogue-development/blog2/wp-content/advanced-cache.php) [function.include]: failed to open stream: No such file or directory in /var/www/html/rogue-development/blog2/wp-settings.php on line 62

Warning: include() [function.include]: Failed opening '/var/www/html/rogue-development/blog2/wp-content/advanced-cache.php' for inclusion (include_path='.:/usr/share/pear:/usr/share/php') in /var/www/html/rogue-development/blog2/wp-settings.php on line 62

Notice: add_option was called with an argument that is deprecated since version 2.3 with no alternative available. in /var/www/html/rogue-development/blog2/wp-includes/functions.php on line 3468

Notice: register_sidebar_widget is deprecated since version 2.8! Use wp_register_sidebar_widget() instead. in /var/www/html/rogue-development/blog2/wp-includes/functions.php on line 3382

Notice: register_widget_control is deprecated since version 2.8! Use wp_register_widget_control() instead. in /var/www/html/rogue-development/blog2/wp-includes/functions.php on line 3382
Comments on: A lesson on AIR certificate signing http://www.rogue-development.com/blog2/2010/05/a-lesson-on-air-certificate-signing/ Comments and thoughts on technology from Marc Hughes Sun, 30 Jan 2011 18:36:22 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Adrian Raper http://www.rogue-development.com/blog2/2010/05/a-lesson-on-air-certificate-signing/comment-page-1/#comment-1765 Adrian Raper Thu, 22 Jul 2010 07:08:48 +0000 http://www.rogue-development.com/blog2/?p=623#comment-1765 This is a very helpful post, thanks. I can now make an update to my AIR app with a renewed certificate. But I can't quite get my head round a multi-version problem. 1) I release v4.1 under certificate-expire-Mar-2010 in Jan 2010 2) I release v4.2 under certificate-epxire-Mar-2012 in May 2010, but using the update from certificate-expire-Mar-2010. This will update v4.1 fine. 3) I release v4.3 under certificate-epxire-Mar-2012 in Sept 2010. Since I can't use adt migrate it means that people who still have v4.1 will not be able to update, right? This is a very helpful post, thanks. I can now make an update to my AIR app with a renewed certificate. But I can’t quite get my head round a multi-version problem.
1) I release v4.1 under certificate-expire-Mar-2010 in Jan 2010
2) I release v4.2 under certificate-epxire-Mar-2012 in May 2010, but using the update from certificate-expire-Mar-2010. This will update v4.1 fine.
3) I release v4.3 under certificate-epxire-Mar-2012 in Sept 2010. Since I can’t use adt migrate it means that people who still have v4.1 will not be able to update, right?

]]> By: bdefore http://www.rogue-development.com/blog2/2010/05/a-lesson-on-air-certificate-signing/comment-page-1/#comment-1702 bdefore Thu, 06 May 2010 21:34:34 +0000 http://www.rogue-development.com/blog2/?p=623#comment-1702 I ran into this issue too, and it would only manifest itself when a user would be prompted to update, then get an AIR file that report that the installer was "damaged". I don't know why Adobe even bothers to check for expiration on unsigned certificates. I agree this could be really infuriating for those past the 180 day limit, when they lose all ability to use AIR's built-in auto-update. I ran into this issue too, and it would only manifest itself when a user would be prompted to update, then get an AIR file that report that the installer was “damaged”. I don’t know why Adobe even bothers to check for expiration on unsigned certificates. I agree this could be really infuriating for those past the 180 day limit, when they lose all ability to use AIR’s built-in auto-update.

]]> By: Marc http://www.rogue-development.com/blog2/2010/05/a-lesson-on-air-certificate-signing/comment-page-1/#comment-1700 Marc Thu, 06 May 2010 15:06:41 +0000 http://www.rogue-development.com/blog2/?p=623#comment-1700 I think you may be screwed. One thing you could do. Give the app a new Application ID so it's a brand new app. Then in the code of the app you could have it check the old local settings folder manually, and if it exists use that instead of the default. It'd be messy. I think you may be screwed.

One thing you could do. Give the app a new Application ID so it’s a brand new app. Then in the code of the app you could have it check the old local settings folder manually, and if it exists use that instead of the default. It’d be messy.

]]> By: hosey http://www.rogue-development.com/blog2/2010/05/a-lesson-on-air-certificate-signing/comment-page-1/#comment-1699 hosey Thu, 06 May 2010 14:58:00 +0000 http://www.rogue-development.com/blog2/?p=623#comment-1699 I had the same issue, except I found all this out at day 190. Now I am screwed! Any ideas? I had the same issue, except I found all this out at day 190. Now I am screwed! Any ideas?

]]>