Hi, > Can I assume we’ve never seen this error before?
There been a few instances of the same string, but given it’s generic nature it’s hard to tell if it’s the same error or not. For example: https://www.google.com/analytics/web/?hl=en#report/content-pages/a37926454w66427073p68310079/%3F_u.date00%3D20150201%26_u.date01%3D20150702%26explorer-table.plotKeys%3D%5B%5D%26_r.drilldown%3Danalytics.pagePath%3A%2Ftrack-installer.html%3Ffailure%3Dtrue%2526label%3DApache%20Flex%20SDK%204.14.0%2526version%3D4.14.0%2526os%3Dwindows%2526info%3DError/ <https://www.google.com/analytics/web/?hl=en#report/content-pages/a37926454w66427073p68310079/?_u.date00=20150201&_u.date01=20150702&explorer-table.plotKeys=[]&_r.drilldown=analytics.pagePath:/track-installer.html?failure=true%26label=Apache Flex SDK 4.14.0%26version=4.14.0%26os=windows%26info=Error/> It occurs for FlexJS as well: https://www.google.com/analytics/web/?hl=en#report/content-pages/a37926454w66427073p68310079/%3F_u.date00%3D20150201%26_u.date01%3D20150702%26explorer-table.plotKeys%3D%5B%5D%26_r.drilldown%3Danalytics.pagePath%3A%2Ftrack-installer.html%3Ffailure%3Dtrue%2526label%3DApache%20FlexJS%20Nightly%2526version%3D0.0.3%2526os%3Dmac%2526info%3DError/ <https://www.google.com/analytics/web/?hl=en#report/content-pages/a37926454w66427073p68310079/?_u.date00=20150201&_u.date01=20150702&explorer-table.plotKeys=[]&_r.drilldown=analytics.pagePath:/track-installer.html?failure=true%26label=Apache FlexJS Nightly%26version=0.0.3%26os=mac%26info=Error/> There is a spike in the numbers of this error in the last few days so I think we can assume it’s the new installer. > Is there a way to find out if a failure is from an IP address that later > gets a success? Not easily. We can’t tell if the same address gets repeated failures :-( > Did any other errors go away? Not all of them no, but the windows directory issue is certainly less than before but not gone, but I assume that this is because not every one is using the new installer yet. Overall error rate is slightly higher. > A third place is in the uncaught error handler, but it would require > someone throwing an Error with the error string “Error” and the stack > trace not being invisible. Running on older AIR versions perhaps??? Another thing we could possible log. > So it is a bit puzzling how we can be getting this sort of failure report. > Folks, if you experience an installer failure, please post the log > somewhere and send us a link. Probably the only we we’ll find out more. From previous experience it take about 100 errors to get someone to speak up. Thanks, Justin
