Revert "Use internal property and custom get/set for public BTThreeDS…

…ecureRequest.cardAddChallenge to avoid Xcode deprecation usage warnings" This reverts commit 1eb5eaf.
braintree · Nov 2, 2023 · 9c9f462 · 9c9f462
1 parent 1eb5eaf
commit 9c9f462
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 9 deletions.
diff --git a/Sources/BraintreeThreeDSecure/BTThreeDSecureClient.swift b/Sources/BraintreeThreeDSecure/BTThreeDSecureClient.swift
@@ -351,9 +351,9 @@ import BraintreeCore
                 "dataOnlyRequested": request.dataOnlyRequested
             ]
 
-            if request._cardAddChallenge == .requested || request.cardAddChallengeRequested == true {
+            if request.cardAddChallenge == .requested || request.cardAddChallengeRequested == true {
                 requestParameters["cardAdd"] = true
-            } else if request._cardAddChallenge == .notRequested {
+            } else if request.cardAddChallenge == .notRequested {
                 requestParameters["cardAdd"] = false
             }
 

diff --git a/Sources/BraintreeThreeDSecure/BTThreeDSecureRequest.swift b/Sources/BraintreeThreeDSecure/BTThreeDSecureRequest.swift
@@ -58,14 +58,8 @@ import BraintreeCore
     /// If set to `.notRequested` the authentication challenge will not be requested from the issuer.
     /// If set to `.unspecified`, when the amount is 0, the authentication challenge will be requested from the issuer.
     /// If set to `.unspecified`, when the amount is greater than 0, the authentication challenge will not be requested from the issuer.
-    @available(*, deprecated, message: "Use `cardAddChallengeRequested` instead")
-    public var cardAddChallenge: BTThreeDSecureCardAddChallenge {
-        get { return _cardAddChallenge }
-        set { _cardAddChallenge = newValue }
-    }
+    public var cardAddChallenge: BTThreeDSecureCardAddChallenge = .unspecified
 
-    var _cardAddChallenge: BTThreeDSecureCardAddChallenge = .unspecified
-
     /// Optional.  An authentication created using this flag should only be used for vaulting operations (creation of customers' credit cards or payment methods) and not for creating transactions.
     /// If set to `true`, a card-add challenge will be requested from the issuer.
     /// If set to `false`, a card-add challenge will not be requested.