Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #127
Issue is reproducible when service/process is potentially killed by the system and since
ScreenRecordingService.onStartCommand()
is returningSTART_STICKY
, and if the service is in the started state, system will try to recreate the service. But, it will not retain intent. So, intent will be null in that case andAttempt to invoke virtual method 'long android.content.Intent.getLongExtra(java.lang.String, long)' on a null object reference
will occur.In that case, stopping service is called to avoid any other potential issue.
Also, consider returning START_REDELIVER_INTENT instead of START_STICKY, so Intent is retained after a service restart.
Changes:
Added null check on Intent
Stop Service if Intent is null