The runtime must be created in the UI process but the CrashReporterService is not allowed to run on it, as it's explained in commit 63f474a.
This PR provides a workaround by creating a dummy CrashReportIntent if the runtime instance has not been created.
It's important to consider that this change discovers an underlying issue we already had, due to the way Gecko starts the CrashReportService: context.startForegroundService(intent);It seems that if the Service doesn't call to startForegound() in a short period of time, android raises a ForegroundServiceDidNotStartInTimeException:
The runtime must be created in the UI process but the CrashReporterService is not allowed to run on it, as it's explained in commit 63f474a.
This PR provides a workaround by creating a dummy CrashReportIntent if the runtime instance has not been created.
It's important to consider that this change discovers an underlying issue we already had, due to the way Gecko starts the CrashReportService:
context.startForegroundService(intent);It seems that if the Service doesn't call tostartForegound()in a short period of time, android raises aForegroundServiceDidNotStartInTimeException: