[tor-commits] [tor-browser/tor-browser-68.1.0esr-9.0-1] Bug 25741 - TBA: Move GCM Push prefs within preprocessor guard

[gk at torproject.org]

commit f130103fc3403cb6c9dbedd314a7face0e4e42e7
Author: Matthew Finkel <Matthew.Finkel at gmail.com>
Date:   Sun Apr 15 14:19:38 2018 +0000

    Bug 25741 - TBA: Move GCM Push prefs within preprocessor guard
    
    Otherwise the preprocessor is sad because MOZ_ANDROID_GCM_SENDERID is
    not defined. We don't need any of this, so we exclude it.
---
 mobile/android/app/mobile.js | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/mobile/android/app/mobile.js b/mobile/android/app/mobile.js
index 3e13d0d81a5d..9d4f331e968f 100644
--- a/mobile/android/app/mobile.js
+++ b/mobile/android/app/mobile.js
@@ -813,13 +813,13 @@ pref("dom.serviceWorkers.enabled", true);
 // click on mobile.  This is to account for some devices being quite slow.
 pref("dom.serviceWorkers.disable_open_click_delay", 5000);
 
+#ifdef MOZ_ANDROID_GCM
 pref("dom.push.debug", false);
 // The upstream autopush endpoint must have the Google API key corresponding to
 // the App's sender ID; we bake this assumption directly into the URL.
 pref("dom.push.serverURL", "https://updates.push.services.mozilla.com/v1/gcm/@MOZ_ANDROID_GCM_SENDERID@");
 pref("dom.push.maxRecentMessageIDsPerSubscription", 0);
 
-#ifdef MOZ_ANDROID_GCM
 pref("dom.push.enabled", true);
 #endif