Possible concurrency issues because two processes have different application class instances about customactivityoncrash HOT 2 CLOSED

I am currently investigating this problem.

First of all, the process for the error activity only needs to be set on API<17, so the library should only use that option with API<17. See: ACRA/acra#284

Secondly, I am investigating if it's possible to kill the error activity process before launching the restart activity.

from customactivityoncrash.

There is no way to make the error activity be on another process depending on the API level. I tried using a string resource for the process attribute, but that only seems to work on recent versions of the API (>18, I think). On previous platform versions the process is left blank and therefore runs on the same process as the app, which is just the opposite of what we want.

So... Now the error activity process is completely killed when restarting the app. This guarantees that there will not be multiple Application instances running on different processes (unless you do multiprocesses yourself on your app, in that case, please take extra care because this library is untested under those conditions).

Hopefully this fixed the problem.

from customactivityoncrash.