Merge pull request #8814 from woocommerce/issue/8773-reveal-TTP-feature-toggle-in-release-builds

[Mobile Payments] Reveal TTP feature toggle in release builds

Author: joshheald

Experiments/Experiments/DefaultFeatureFlagService.swift

@@ -56,7 +56,9 @@ public struct DefaultFeatureFlagService: FeatureFlagService {
             // Disabled by default to avoid costs spikes, unless in internal testing builds.
             return buildConfig == .alpha
         case .tapToPayOnIPhone:
-            return buildConfig == .localDeveloper
+            // It is not possible to get the TTPoI entitlement for an enterprise certificate,
+            // so we should not enable this for alpha builds.
+            return buildConfig == .localDeveloper || buildConfig == .appStore
         case .domainSettings:
             return buildConfig == .localDeveloper || buildConfig == .alpha
         case .supportRequests:

WooCommerce/Classes/Model/BetaFeature.swift

@@ -70,12 +70,22 @@ extension BetaFeature {
         case .inAppPurchases:
             return ServiceLocator.featureFlagService.isFeatureFlagEnabled(.inAppPurchases)
         case .tapToPayOnIPhone:
-            return ServiceLocator.featureFlagService.isFeatureFlagEnabled(.tapToPayOnIPhone)
+            return ServiceLocator.featureFlagService.isFeatureFlagEnabled(.tapToPayOnIPhone) && deviceMaySupportTTP
         default:
             return true
         }
     }
 
+    // Full checking for support of TTP requires a more complicated call.
+    // This is sufficient for whether the feature toggle should be shown, as full support checks
+    // are done when a payment is started. This is a temporary measure until full release.
+    private var deviceMaySupportTTP: Bool {
+        guard #available(iOS 16, *) else {
+            return false
+        }
+        return !UIDevice.isPad()
+    }
+
     static var availableFeatures: [Self] {
         allCases.filter(\.isAvailable)
     }