Platform-independent Content (Android and iOS)
This article applies to both Android and iOS operating systems.
Repeat days, in general, specify how many days to wait until inviting a user to participate in a survey following a previous invitation. The following options are available:
repeatDaysAfterComplete: This defines the number of days after a user has completed a survey before they are eligible to be invited again. You can disable re-invite completely by removing this key from the
repeatDaysAfterDecline: This defines the number of days after a user has declined an invitation (or abandoned a survey) before they are eligible to be invited again. You can also disable re-invite completely by removing this key from the
repeatDaysAfterAccept: This defines the number of days that the SDK will wait to transition into the DECLINED state after a user has received a local notification.
**Note:** This option is for `Exit Invite` and `Exit Survey` invitation modes only. Please refer to the Invitation Modes section ([Android](doc:invite-modes) / [iOS](doc:invite-modes-1)) for more information.
Once the repeat days have elapsed, the state of the SDK is reset (and tracking/recording resumes) when the app is started. Once the state is reset, the original criteria must again be met before an invitation is shown.
To test the repeat days configuration, you can manually move the device clock backwards the number of defined repeat days, trigger an invitation and complete/decline the survey, then move the device clock forward to the present day.
Updated about a year ago