On Sun, Aug 24, 2014 at 6:49 PM, Justin Mclean <justinmcl...@me.com> wrote:
> Hi, > > Just took a look at the installer errors in the last week. > > Overall there here were 707 errors and 702 successful installs, that's a > 50% error rate and the error rate is higher on windows. The good news is > we've had 3000+ installs of Apache Flex4.13.0. > > Here a rough total of the significant issues: > > On windows: > 146 Unable to create temporary directory > 105 [IOErrorEvent type="ioError" bubbles=false cancelable=false > eventPhase=2 text="Error #2032" errorID=2032] > 89 The Apache Flex SDK MD5 Signature of the downloaded files does not > match the reference value. The file is invalid, installation is aborted. > 50 aglj40.jar download failed > 49 Error > 29 Unable to download Apache Flex SDK > 27 AIR SDK download failed > 18 Flash SDK download failed > 10 Unable to load > https://www.apache.org/dist/flex/4.13.0/binaries/apache-flex-sdk-installer-config.xml > 7 afe.jar download failed > > On mac: > 48 [get] [IOErrorEvent type="ioError" bubbles=false cancelable=false > eventPhase=2 text="Error #2032" errorID=2032] > 8 Flash SDK download failed > > Obviously we need to do something about the temporary directory issue. > This should be a straightforward feature to implement. When the user selects a directory, we try to write create a temp dir there. We should be able to catch that error provide feedback to the user to select a different directory or to restart the app as Administrator. Anyone in the community willing to add this feature? Thanks, Om > > Can we add any more information to work out what's causing the 2032 error? > Do we need to increase timeouts on download requests or something? > > There was a large number of MD5 signature mismatches, this is a little > surprising. Is there anything we can do to try and fix this? Given our > infrastructure (ie mirrors) is seem odd that more than 1 in 10 downloads > results in a MD5 issue. > > I also find > https://www.apache.org/dist/flex/4.13.0/binaries/apache-flex-sdk-installer-config.xml > odd, as it wasn't able to get the config file but was able to log the error > (also a HTTP request) which seems odd to me. > > Thanks, > Justin
