Update macOS config for Privacy Pro survey changes #101
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Task: https://app.asana.com/0/1199333091098016/1208279675094863/f
This PR updates the macOS Privacy Pro surveys to add a hardcoded build type parameter to the survey URLs. This is a temporary measure until the survey builder supports the build type parameter.
See the linked Asana task for an easier-to-read mapping of rules to messages.
How to test:
RemoteMessagingClient.swift
to use the staging URLRemoteMessagingConfigMatcherProvider
and overrideprivacyProPurchasePlatform
to saystripe
, as internal user accounts use a custom purchase platform that the survey isn't checking forprivacyProDaysSinceSubscribed
initializer value inRemoteMessagingConfigMatcherProvider
to be 14 or above - if your account is already older than that then you won't need to do anythingshouldProcessConfig
func in BSK to always return true, or use the Debug menu to reset and refresh the RMF cache if necessarybuild
parameter is present and it references the correct build typeHow to test the exit survey:
RemoteMessagingConfigMatcherProvider
to setisPrivacyProSubscriptionExpiring
to true and all other booleans to falsebuild
parameter is present and it references the correct build typedismissedMessageIDs()
function and return an empty array. The console logs will be able to tell you which attributes are failing as well.