test: O11Y-685 - Manual way to test signals when app runs in background/foreground service #275
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.
Summary
Adds a way to test the observability signals are being created even when the application is hidden but running a foreground or background service.
How did you test this change?
No tests needed
Are there any deployment considerations?
No, the code added just changes the Sample App
Note
Adds Android foreground/background services that run 30s periodic observability logging, with new UI buttons to start them and manifest updates for permissions and service registration.
ObservabilityForegroundServicewith notification channel and foreground execution.ObservabilityBackgroundServicefor non-foreground execution.launchObservabilityLoggingTasklogs every 5s for 30s viaLDObserve.AndroidViewModeland addstartForegroundService()andstartBackgroundService()helpers.MainActivity):android.permission.FOREGROUND_SERVICE.ObservabilityForegroundServiceandObservabilityBackgroundService.Written by Cursor Bugbot for commit 210ab48. This will update automatically on new commits. Configure here.