[PR #6419] [MERGED] Remove intialization of NetworkConnectionManager from application class #43657

Closed
opened 2026-04-23 22:19:07 -05:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/bitwarden/android/pull/6419
Author: @david-livefront
Created: 1/27/2026
Status: Merged
Merged: 1/28/2026
Merged by: @david-livefront

Base: mainHead: incorrect-network-status


📝 Commits (1)

  • 1c4dc1a Remove intialization of NetworkConnectionManager from application class

📊 Changes

1 file changed (+0 additions, -4 deletions)

View changed files

📝 app/src/main/kotlin/com/x8bit/bitwarden/BitwardenApplication.kt (+0 -4)

📄 Description

🎟️ Tracking

N/A

📔 Objective

This PR removes the NetworkConnectionManager from the BitwardenApplication in order to resolve an odd issue where initializing the manager so early was causing the activeNetwork to be null 100% of the time. This issue would occur whenever the Autofill framework initialized the app, under normal circumstances where the app is launched by the user, this issue would not occur.

The original reason for the manager to be initialized so early was for logging purposes, so it is not required to be there for core functionality and is okay to remove.

Reminders before review

  • Contributor guidelines followed
  • All formatters and local linters executed and passed
  • Written new unit and / or integration tests where applicable
  • Protected functional changes with optionality (feature flags)
  • Used internationalization (i18n) for all UI strings
  • CI builds passed
  • Communicated to DevOps any deployment requirements
  • Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team

🦮 Reviewer guidelines

  • 👍 (:+1:) or similar for great changes
  • 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
  • (:question:) for questions
  • 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
  • 🎨 (:art:) for suggestions / improvements
  • (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
  • 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
  • ⛏ (:pick:) for minor or nitpick changes

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/bitwarden/android/pull/6419 **Author:** [@david-livefront](https://github.com/david-livefront) **Created:** 1/27/2026 **Status:** ✅ Merged **Merged:** 1/28/2026 **Merged by:** [@david-livefront](https://github.com/david-livefront) **Base:** `main` ← **Head:** `incorrect-network-status` --- ### 📝 Commits (1) - [`1c4dc1a`](https://github.com/bitwarden/android/commit/1c4dc1a60419d17029bfd9ca9daf915f61ccd161) Remove intialization of NetworkConnectionManager from application class ### 📊 Changes **1 file changed** (+0 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `app/src/main/kotlin/com/x8bit/bitwarden/BitwardenApplication.kt` (+0 -4) </details> ### 📄 Description ## 🎟️ Tracking N/A ## 📔 Objective This PR removes the `NetworkConnectionManager` from the `BitwardenApplication` in order to resolve an odd issue where initializing the manager so early was causing the `activeNetwork` to be null 100% of the time. This issue would occur whenever the Autofill framework initialized the app, under normal circumstances where the app is launched by the user, this issue would not occur. The original reason for the manager to be initialized so early was for logging purposes, so it is not required to be there for core functionality and is okay to remove. ## ⏰ Reminders before review - Contributor guidelines followed - All formatters and local linters executed and passed - Written new unit and / or integration tests where applicable - Protected functional changes with optionality (feature flags) - Used internationalization (i18n) for all UI strings - CI builds passed - Communicated to DevOps any deployment requirements - Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team ## 🦮 Reviewer guidelines <!-- Suggested interactions but feel free to use (or not) as you desire! --> - 👍 (`:+1:`) or similar for great changes - 📝 (`:memo:`) or ℹ️ (`:information_source:`) for notes or general info - ❓ (`:question:`) for questions - 🤔 (`:thinking:`) or 💭 (`:thought_balloon:`) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion - 🎨 (`:art:`) for suggestions / improvements - ❌ (`:x:`) or ⚠️ (`:warning:`) for more significant problems or concerns needing attention - 🌱 (`:seedling:`) or ♻️ (`:recycle:`) for future improvements or indications of technical debt - ⛏ (`:pick:`) for minor or nitpick changes --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-23 22:19:07 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#43657