-
-
Notifications
You must be signed in to change notification settings - Fork 30
ADFA-4397: Migrate crash and log reporting from Sentry to GlitchTip #1490
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Daniel-ADFA
wants to merge
1
commit into
stage
Choose a base branch
from
ADFA-4397
base: stage
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+28
−24
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🩺 Stability & Availability | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: appdevforall/CodeOnTheGo
Length of output: 6511
🏁 Script executed:
Repository: appdevforall/CodeOnTheGo
Length of output: 6445
🌐 Web query:
Android direct boot Settings.Secure.ANDROID_ID ContentResolver availability💡 Result:
In Android, Settings.Secure.ANDROID_ID is available to encryption-aware applications during Direct Boot mode [1][2]. Direct Boot mode allows an Android device to boot to a state where it is powered on but the user has not yet entered their credentials (such as a PIN, pattern, or password) [1][3]. To access system resources or perform operations during this phase, an application must be marked as encryption-aware by setting the android:directBootAware attribute to true in its manifest [2][4]. Regarding the specific availability of Settings.Secure.ANDROID_ID and ContentResolver: 1. Settings.Secure.ANDROID_ID: The Settings provider is generally available during Direct Boot, meaning applications can retrieve the ANDROID_ID via the standard ContentResolver interface [5][6]. 2. ContentResolver: While the ContentResolver class is available during Direct Boot, its utility is restricted by the encryption state of the underlying data [2][6]. An encryption-aware app can successfully use a ContentResolver to query data stored in device-encrypted storage [2]. However, attempts to access data in credential-encrypted storage (which is only decrypted after the user unlocks the device) will fail or be unavailable [2]. Developers should ensure that any components interacting with these APIs during the locked state are correctly registered and handle potential limitations regarding data access gracefully [2][4].
Citations:
Wrap the Sentry/Logback setup in
runCatching.DeviceProtectedApplicationLoaderis startup-critical in direct boot, and any exception here can abortload()beforeShizukuSettings.initialize()andEventBussetup.IDEApplication.ktalready warns that failures in this loader can lead to ANRs after reboot.🤖 Prompt for AI Agents