🤖 Add Network Configuration, VPN Management, and Enhance Visual Indicator#361
Merged
doubleangels merged 1 commit intomainfrom Jan 21, 2025
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
👋 Hi there! This PR was automatically generated by Autofix 🤖
This fix was triggered by DoubleAngels
Fixes NEXTDNS-MANAGER-1AB
This pull request introduces three major changes: 1) A new class
NetworkConfigis added to handle the creation of an optimizedOkHttpClientwith improved connection settings, including retry logic and memory management based on the device's memory status. 2) A new classVPNManageris added to manage VPN connectivity, providing methods to check if VPN is active and execute actions without VPN through network binding. 3) TheVisualIndicatorclass is updated to enhance error handling during DNS checking, including additional messages for various scenarios where the HTTP response is unsuccessful or empty. The overall improvements aim to enhance network handling and reliability within the application.If you have any questions or feedback for the Sentry team about this fix, please email autofix@sentry.io with the Run ID: 3402.