Being able to "drop" old releases up to a version

[johnuopini]

I know the project just started and there are a lot of things to do (like grouping) that are more important, but, from my point of view, being able to completely "clear" old releases would be also a very welcome addition.

The simplest way to do this could be a parameter that tells Acralyzer from which versions exception are accepted, everything else will be dropped.

This is very useful especially if you release a buggy version with a "silentErrorReport" somewhere that generates tons of exceptions, if some of your users never upgrade you will get flooded by those errors forever.

Or maybe it could be done at the acraproxy.php level? This would make some of us save some money on the couchDB hosting :)

[KevinGaudin]

Yes, you could do it in the acraproxy.php, you would need to:

• read php://input in a variable, for example report_data
• parse its JSON content (or maybe just use a regexp to get the content of the APP_VERSION_CODE field)
• check the APP_VERSION_CODE
• if OK, rewrite the report_data content to an in-memory file (using php://memory or php://temp as the file output)
• feed the curl CURLOPT_INFILE parameter with this file

[littleguy77]

@johnuopini In the acra-storage source, check out validate_doc_update.js -- you can specify a minimum app version code, to exclude reports from obsolete releases of your app. If I understand the OP's question, then I would consider this resolved.

[KevinGaudin]

Yep, I updated this and it requires ACRA v4.5.0 stable. With previous versions (4.5.0RC*), refused reports are kept on the device.