Use InlineFilters to populate correct variable names for Android

Author: mattcreaser

src/fragments/lib/auth/common/mfa/flows.mdx

@@ -219,13 +219,23 @@ You can use Time-based One-Time Password (TOTP) for multi-factor authentication
 
 ### Setting up TOTP for a user
 
+<InlineFilter filters={['android']}>
+After you initiate a user sign in with the `signIn` API where a user is required to set up TOTP as an MFA method, the API call will return `CONTINUE_SIGN_IN_WITH_TOTP_SETUP` as a challenge and next step to handle in your app. You will get that challenge if the following conditions are met:
+</InlineFilter>
+<InlineFilter filters={['swift', 'flutter']}>
 After you initiate a user sign in with the `signIn` API where a user is required to set up TOTP as an MFA method, the API call will return `continueSignInWithTOTPSetup` as a challenge and next step to handle in your app. You will get that challenge if the following conditions are met:
+</InlineFilter>
 
 - MFA is marked as **Required** in Cognito User Pool.
 - TOTP is enabled in the Cognito User Pool
 - User does not have TOTP MFA set up already.
 
+<InlineFilter filters={['android']}>
+The `CONTINUE_SIGN_IN_WITH_TOTP_SETUP` step signifies that the user must set up TOTP before they can sign in. The step returns an associated value of type `TOTPSetupDetails` which must be used to configure an authenticator app like Microsoft Authenticator or Google Authenticator. `TOTPSetupDetails` provides a helper method called `getSetupURI` which generates a URI that can be used, for example, in a button to open the user's installed authenticator app. For more advanced use cases, `TOTPSetupDetails` also contains a `sharedSecret` which can be used to either generate a QR code or be manually entered into an authenticator app.
+</InlineFilter>
+<InlineFilter filters={['swift', 'flutter']}>
 The `continueSignInWithTOTPSetup` step signifies that the user must set up TOTP before they can sign in. The step returns an associated value of type `TOTPSetupDetails` which must be used to configure an authenticator app like Microsoft Authenticator or Google Authenticator. `TOTPSetupDetails` provides a helper method called `getSetupURI` which generates a URI that can be used, for example, in a button to open the user's installed authenticator app. For more advanced use cases, `TOTPSetupDetails` also contains a `sharedSecret` which can be used to either generate a QR code or be manually entered into an authenticator app.
+</InlineFilter>
 
 Once the authenticator app is set up, the user can generate a TOTP code and provide it to the library to complete the sign in process.
 
@@ -599,7 +609,12 @@ Future<void> updateMfaPreferences() async {
 
 </InlineFilter>
 
+<InlineFilter filters={['android']}>
+If multiple MFA methods are enabled for the user, the `signIn` API will return `CONTINUE_SIGN_IN_WITH_MFA_SELECTION` as the next step in the auth flow. During this scenario, the user should be prompted to select the MFA method they want to use to sign in and their preference should be passed to `confirmSignIn`.
+</InlineFilter>
+<InlineFilter filters={['swift', 'flutter']}>
 If multiple MFA methods are enabled for the user, the `signIn` API will return `continueSignInWithMFASelection` as the next step in the auth flow. During this scenario, the user should be prompted to select the MFA method they want to use to sign in and their preference should be passed to `confirmSignIn`.
+</InlineFilter>
 
 import iosContinueSignInWithMFASelection from '/src/fragments/lib/auth/ios/signin_next_steps/91_continue_mfa_selection_code.mdx';
 

src/fragments/lib/auth/native_common/signin_next_steps/common.mdx

@@ -35,7 +35,12 @@ import flutter1 from '/src/fragments/lib/auth/flutter/signin_next_steps/20_confi
 
 ### Confirm signin with TOTP MFA
 
+<InlineFilter filters={['android']}>
+If the next step is `CONFIRM_SIGN_IN_WITH_TOTP_CODE`, you should prompt the user to enter the TOTP code from their associated authenticator app during set up. The code is a six-digit number that changes every 30 seconds. The user must enter the code before the 30-second window expires.
+</InlineFilter>
+<InlineFilter filters={['swift', 'flutter']}>
 If the next step is `confirmSignInWithTOTPCode`, you should prompt the user to enter the TOTP code from their associated authenticator app during set up. The code is a six-digit number that changes every 30 seconds. The user must enter the code before the 30-second window expires.
+</InlineFilter>
 
 After the user enters the code, your implementation must pass the value to Amplify Auth `confirmSignIn` API.
 
@@ -164,7 +169,12 @@ Future<void> confirmTotpUser(String totpCode) async {
 
 ### Continue signin with MFA Selection
 
+<InlineFilter filters={['android']}>
+If the next step is `CONTINUE_SIGN_IN_WITH_MFA_SELECTION`, the user must select the MFA method to use. Amplify Auth currently only supports SMS and TOTP as MFA methods. After the user selects an MFA method, your implementation must pass the selected MFA method to Amplify Auth using `confirmSignIn` API.
+</InlineFilter>
+<InlineFilter filters={['swift', 'flutter']}>
 If the next step is `continueSignInWithMFASelection`, the user must select the MFA method to use. Amplify Auth currently only supports SMS and TOTP as MFA methods. After the user selects an MFA method, your implementation must pass the selected MFA method to Amplify Auth using `confirmSignIn` API.
+</InlineFilter>
 
 import iosContinueSignInWithMFASelectionCode from 'src/fragments/lib/auth/ios/signin_next_steps/91_continue_mfa_selection_code.mdx';
 
@@ -280,7 +290,12 @@ Future<void> _handleMfaSelection(MfaType selection) async {
 
 ### Continue signin with TOTP Setup
 
+<InlineFilter filters={['android']}>
+If the next step is `CONTINUE_SIGN_IN_WITH_TOTP_SETUP`, then the user must provide a TOTP code to complete the sign in process. The step returns an associated value of type `TOTPSetupDetails` which would be used for generating TOTP. `TOTPSetupDetails` provides a helper method called `getSetupURI` that can be used to generate a URI, which can be used by native password managers for TOTP association. For example. if the URI is used on Apple platforms, it will trigger the platform's native password manager to associate TOTP with the account. For more advanced use cases, `TOTPSetupDetails` also contains the `sharedSecret` that will be used to either generate a QR code or can be manually entered into an authenticator app.
+</InlineFilter>
+<InlineFilter filters={['swift', 'flutter']}>
 If the next step is `continueSignInWithTOTPSetup`, then the user must provide a TOTP code to complete the sign in process. The step returns an associated value of type `TOTPSetupDetails` which would be used for generating TOTP. `TOTPSetupDetails` provides a helper method called `getSetupURI` that can be used to generate a URI, which can be used by native password managers for TOTP association. For example. if the URI is used on Apple platforms, it will trigger the platform's native password manager to associate TOTP with the account. For more advanced use cases, `TOTPSetupDetails` also contains the `sharedSecret` that will be used to either generate a QR code or can be manually entered into an authenticator app.
+</InlineFilter>
 
 Once the authenticator app is set up, the user can generate a TOTP code and provide it to the library to complete the sign in process.