From 00a4d95e6105a1ffaf6da9426bb0c143cf6f8d9f Mon Sep 17 00:00:00 2001
From: "K. Shankari" <shankari@eecs.berkeley.edu>
Date: Sun, 5 May 2024 10:34:42 -0700
Subject: [PATCH] =?UTF-8?q?=F0=9F=92=A9=20Turn=20off=20the=20background=20?=
 =?UTF-8?q?checks=20for=20fleet=20deployments?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Since the fleet deployments are installed on work phones, and the background restriction is apparently grayed out on android work phones.
https://github.com/e-mission/e-mission-docs/issues/1070

This is a hack (hence the 💩 emoji) but it will allow us to make progress
through the onboarding, get the logs and then resolve the issue the right way.
Or if we can't figure out how to access it the right way, this can become a
config option for deployments that plan to use work phones.

This should unblock
https://github.com/e-mission/e-mission-docs/issues/1070#issuecomment-2094354832
---
 www/js/usePermissionStatus.ts | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/www/js/usePermissionStatus.ts b/www/js/usePermissionStatus.ts
index f8fef085b..5e136655f 100644
--- a/www/js/usePermissionStatus.ts
+++ b/www/js/usePermissionStatus.ts
@@ -446,9 +446,10 @@ const usePermissionStatus = () => {
       setupAndroidFitnessChecks();
       if (appConfig.tracking?.bluetooth_only) {
         setupAndroidBluetoothChecks();
+      } else {
+        setupAndroidBackgroundRestrictionChecks();
       }
       setupAndroidNotificationChecks();
-      setupAndroidBackgroundRestrictionChecks();
     } else if (window['device'].platform.toLowerCase() == 'ios') {
       setupIOSLocChecks();
       setupIOSFitnessChecks();