CUSTOM_AUTH not working on v2.2.0 (working on 1.28.3)

Describe the bug
Confirming SMS code is not working when using CUSTOM_AUTH as authenticationFlowType.
Not working on 2.2.0 - working on 1.28.3 (it would be nice to have 2.0.0 because of async await)
Steps To Reproduce
This is our use case:

Call signup (in case of success go to signIn, or in case user exists go to signIn) - Working ✅

try await Amplify.Auth.signUp(username: username, password: password, options: options)

Call signIn - Working ✅

try await Amplify.Auth.signIn(username: username, password: password)

After that I get SMS code which I want to confirm with - not Working 🔴 (just calls the function and get stucked forever)

try await Amplify.Auth.confirmSignIn(challengeResponse: smsCode)

Our awsConfig:
{
    "auth":
    {
        "plugins":
        {
            "awsCognitoAuthPlugin":
            {
                "CognitoUserPool":
                {
                    "Default":
                    {
                        "PoolId": "our-pool",
                        "AppClientId": "our-appclientId",
                        "AppClientSecret": "our-appSecret",
                        "Region": "our-region"
                    }
                },
                "Auth":
                {
                    "Default":
                    {
                        "authenticationFlowType": "CUSTOM_AUTH"
                    }
                }
            }
        }
    }
}

### Expected behavior

It works - returns succes or error

### Amplify Framework Version

2.2.0

### Amplify Categories

Auth

### Dependency manager

Swift PM

### Swift version

5.7

### CLI version

-

### Xcode version

14.1

### Relevant log output

```shell
<details>
<summary>Log Messages</summary>

INSERT LOG MESSAGES HERE

```
Is this a regression?
No
Regression additional context
No response
Device
iPhone 14- Simulator
iOS Version
iOS 16.1
Specific to simulators
No response
Additional context
I'm working on KMM project where I have interface/protocol inside shared module and implementations on iOS and Android side.
I have to say this error exists in Android 2.x.x version as well (just slightly different) - will post issue there as well.

@JurajBegovac Since you didn't use the Amplify CLI and don't have an amplifyconfiguration.json, it's difficult to reproduce the issue without additional context or specific details of how you've configuration authentication with MFA.  Can you provide additional logs or console logs when you're seeing the issue?  Is there an error be thrown or captured?
Some other information that would help:

Your steps don't have a confirmSignUp, please confirm that you have email registration/verification disabled in Cognito.
How did you configure MFA and what are the settings?

Is it Off/Optional/Required

What is the password recovery setting in Cognito?

Do you have email/phone/ both phone and email verification enabled?

@JurajBegovac Additional logging can be enabled by adding this line when configuring Amplify plugins:
Amplify.Logging.logLevel = .verbose

I'm having the same issue as OP. I'm not sure how helpful this will be, but here is my amplify configuration.json file:
{
    "UserAgent": "aws-amplify-cli/2.0",
    "Version": "1.0",
    "api": {
        "plugins": {
            "awsAPIPlugin": {
                "radar": {
                    "endpointType": "GraphQL",
                    "endpoint": "https://<REDACTED>.appsync-api.us-west-2.amazonaws.com/graphql",
                    "region": "us-west-2",
                    "authorizationType": "AMAZON_COGNITO_USER_POOLS",
                    "apiKey": "<REDACTED>"
                }
            }
        }
    },
    "auth": {
        "plugins": {
            "awsCognitoAuthPlugin": {
                "UserAgent": "aws-amplify/cli",
                "Version": "0.1.0",
                "IdentityManager": {
                    "Default": {}
                },
                "CredentialsProvider": {
                    "CognitoIdentity": {
                        "Default": {
                            "PoolId": "us-west-2:<REDACTED>",
                            "Region": "us-west-2"
                        }
                    }
                },
                "CognitoUserPool": {
                    "Default": {
                        "PoolId": "us-west-2_<REDACTED>",
                        "AppClientId": "<REDACTED>",
                        "Region": "us-west-2"
                    }
                },
                "GoogleSignIn": {
                    "Permissions": "email,profile,openid",
                    "ClientId-WebApp": "<REDACTED>.apps.googleusercontent.com",
                    "ClientId-iOS": "<REDACTED>.apps.googleusercontent.com"
                },
                "Auth": {
                    "Default": {
                        "OAuth": {
                            "WebDomain": "<REDACTED>.auth.us-west-2.amazoncognito.com",
                            "AppClientId": "<REDACTED>",
                            "SignInRedirectURI": "<REDACTED>://",
                            "SignOutRedirectURI": "<REDACTED>://",
                            "Scopes": [
                                "phone",
                                "email",
                                "openid",
                                "profile",
                                "aws.cognito.signin.user.admin"
                            ]
                        },
                        "authenticationFlowType": "CUSTOM_AUTH",
                        "socialProviders": [],
                        "usernameAttributes": [
                            "EMAIL",
                            "PHONE_NUMBER"
                        ],
                        "signupAttributes": [
                            "EMAIL"
                        ],
                        "passwordProtectionSettings": {
                            "passwordPolicyMinLength": 8,
                            "passwordPolicyCharacters": []
                        },
                        "mfaConfiguration": "OPTIONAL",
                        "mfaTypes": [
                            "SMS"
                        ],
                        "verificationMechanisms": [
                            "PHONE_NUMBER"
                        ]
                    }
                },
                "AppSync": {
                    "Default": {
                        "ApiUrl": "https://<REDACTED>.appsync-api.us-west-2.amazonaws.com/graphql",
                        "Region": "us-west-2",
                        "AuthMode": "AMAZON_COGNITO_USER_POOLS",
                        "ClientDatabasePrefix": "radar_AMAZON_COGNITO_USER_POOLS"
                    },
                    "radar_API_KEY": {
                        "ApiUrl": "https://<REDACTED>.appsync-api.us-west-2.amazonaws.com/graphql",
                        "Region": "us-west-2",
                        "AuthMode": "API_KEY",
                        "ApiKey": "<REDACTED>",
                        "ClientDatabasePrefix": "radar_API_KEY"
                    }
                },
                "S3TransferUtility": {
                    "Default": {
                        "Bucket": "<REDACTED>",
                        "Region": "us-west-2"
                    }
                }
            }
        }
    },
    "storage": {
        "plugins": {
            "awsS3StoragePlugin": {
                "bucket": "<REDACTED>",
                "region": "us-west-2",
                "defaultAccessLevel": "guest"
            }
        }
    }
}

To answer your follow up questions:

MFA is optional, SMS method
User account recovery is enabled via sms (should never be used - our experience is passwordless)
Verification is enabled, attributes to verify is phone number
MFA is set to optional, sms
I have enabled verbose logging. After the confirm method is invoked, there are no logs from the Amplify service at all.
I am running a custom passwordless auth authentication system and using a lot of boilerplate code from the documentation online (minus the code generation part)

As per the instructions in the setup guide, I have 3 lambdas to execute the custom auth flow. Looking into the cloudwatch logs / metrics I can see that the Define Challenge and Create Challenge lambdas were invoked with the sign in method invocation, but there is never an invocation of the Verify Challenge lambda when the confirm sign in method is executed.

@JurajBegovac @patrickjohnson97 Do you have client side log? From Xcode console or logs from your iOS app or a stacktrace in a debug session?

@patrickjohnson97 If you have email verification enabled, are you calling confirmSignUp with the email verification code prior to calling signIn and confirmSignIn?

@phantumcode Ok here is some verbose log:
After I make signup, then signin (that's ok) - then I call confirmCredential - and then nothing happens:
2022-12-19 11:00:09.674875+0100 iosApp[65648:2045451] [Amplify] Configuring
2022-12-19 11:00:09.677581+0100 iosApp[65648:2045451] [Amplify] Configuration: Optional(Amplify.AmplifyConfiguration(analytics: nil, api: nil, auth: Optional(Amplify.AuthCategoryConfiguration(plugins: ["awsCognitoAuthPlugin": Amplify.JSONValue.object(["CognitoUserPool": Amplify.JSONValue.object(["Default": Amplify.JSONValue.object(["AppClientSecret": Amplify.JSONValue.string(<REDACTED>), "PoolId": Amplify.JSONValue.string("<REDACTED>"), "AppClientId": Amplify.JSONValue.string(<REDACTED>), "Region": Amplify.JSONValue.string(<REDACTED>)])]), "Auth": Amplify.JSONValue.object(["Default": Amplify.JSONValue.object(["authenticationFlowType": Amplify.JSONValue.string("CUSTOM_AUTH")])])])])), dataStore: nil, geo: nil, hub: nil, logging: nil, predictions: nil, storage: nil))
2022-12-19 11:00:09.684011+0100 iosApp[65648:2045451] [Amplify] Could not find Cognito Identity Pool configuration
2022-12-19 11:00:09.691145+0100 iosApp[65648:2045681] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.notConfigured" =     {
    };
}
2022-12-19 11:00:09.691686+0100 iosApp[65648:2045681] [AWSCognitoAuthPlugin] Credential Store state change:

notConfigured
2022-12-19 11:00:09.695634+0100 iosApp[65648:2045681] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configuringAuth" =     {
    };
}
2022-12-19 11:00:09.695739+0100 iosApp[65648:2045684] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitializeAuthConfiguration.swift Starting execution
2022-12-19 11:00:09.696738+0100 iosApp[65648:2045681] [AWSCognitoAuthPlugin] Credential Store state change:

migratingLegacyStore
2022-12-19 11:00:09.696957+0100 iosApp[65648:2045684] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/MigrateLegacyCredentialStore.swift Starting execution
2022-12-19 11:00:09.723054+0100 iosApp[65648:2045684] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/MigrateLegacyCredentialStore.swift Sending event CredentialStoreEvent.loadCredentialStore
2022-12-19 11:00:09.723156+0100 iosApp[65648:2045683] [AWSCognitoAuthPlugin] Credential Store state change:

loadingStoredCredentials
2022-12-19 11:00:09.723186+0100 iosApp[65648:2045684] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Starting execution
2022-12-19 11:00:09.723643+0100 iosApp[65648:2045684] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Retreiving credential amplifyCredentials
2022-12-19 11:00:09.726848+0100 iosApp[65648:2045684] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Sending event CredentialStoreEvent.throwError
2022-12-19 11:00:09.726953+0100 iosApp[65648:2045684] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Starting execution
2022-12-19 11:00:09.727001+0100 iosApp[65648:2045684] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Sending event CredentialStoreEvent.moveToIdleState
2022-12-19 11:00:09.727042+0100 iosApp[65648:2045684] [AWSCognitoAuthPlugin] No existing session found.
2022-12-19 11:00:09.727114+0100 iosApp[65648:2045684] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitializeAuthConfiguration.swift Sending event AuthEvent.validateCredentialAndConfiguration
2022-12-19 11:00:09.727180+0100 iosApp[65648:2045683] [AWSCognitoAuthPlugin] Credential Store state change:

error(KeychainStoreError: Unable to find the keychain item
Recovery suggestion: This should not happen. There is a possibility that there is a bug if this error persists. Please take a look at https://github.com/aws-amplify/amplify-ios/issues to see if there are any existing issues that match your scenario, and file an issue with the details of the bug if there isn't. Issue encountered at:
file: /Users/jurajbegovac/Library/Developer/Xcode/DerivedData/iosApp-ceumhqdilblatpbydusmyekmjbds/SourcePackages/checkouts/amplify-swift/AmplifyPlugins/Core/AWSPluginsCore/Keychain/KeychainStoreError.swift
function: recoverySuggestion
line: 69)
2022-12-19 11:00:09.727243+0100 iosApp[65648:2045683] [AWSCognitoAuthPlugin] Credential Store state change:

idle
2022-12-19 11:00:09.727437+0100 iosApp[65648:2045684] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/ValidateCredentialsAndConfiguration.swift Starting execution
2022-12-19 11:00:09.727469+0100 iosApp[65648:2045683] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.validatingCredentialsAndConfiguration" =     {
    };
}
2022-12-19 11:00:09.727481+0100 iosApp[65648:2045684] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/ValidateCredentialsAndConfiguration.swift Sending event AuthEvent.configureAuthentication
2022-12-19 11:00:09.729082+0100 iosApp[65648:2045686] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configuringAuthentication" =     {
        "AuthenticationState.notConfigured" =         {
        };
    };
}
2022-12-19 11:00:09.729398+0100 iosApp[65648:2045684] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitializeAuthenticationConfiguration.swift Starting execution
2022-12-19 11:00:09.729453+0100 iosApp[65648:2045684] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitializeAuthenticationConfiguration.swift Sending event AuthenticationEvent.configure
2022-12-19 11:00:09.730483+0100 iosApp[65648:2045684] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/ConfigureAuthentication.swift Start execution
2022-12-19 11:00:09.730499+0100 iosApp[65648:2045682] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configuringAuthentication" =     {
        "AuthenticationState.configured" =         {
        };
    };
}
2022-12-19 11:00:09.731065+0100 iosApp[65648:2045684] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/ConfigureAuthentication.swift Sending event AuthenticationEvent.initializedSignedOut
2022-12-19 11:00:09.731161+0100 iosApp[65648:2045684] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/ConfigureAuthentication.swift Sending event AuthEvent.authenticationConfigured
2022-12-19 11:00:09.731184+0100 iosApp[65648:2045683] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configuringAuthentication" =     {
        "AuthenticationState.signedOut" =         {
            lastKnownUserName = "(nil)";
        };
    };
}
2022-12-19 11:00:09.732568+0100 iosApp[65648:2045684] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitializeAuthorizationConfiguration.swift Starting execution
2022-12-19 11:00:09.732767+0100 iosApp[65648:2045684] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitializeAuthorizationConfiguration.swift Sending event AuthorizationEvent.configure
2022-12-19 11:00:09.732956+0100 iosApp[65648:2045683] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configuringAuthorization" =     {
        "AuthenticationState.signedOut" =         {
            lastKnownUserName = "(nil)";
        };
        "AuthorizationState.notConfigured" =         {
        };
    };
}
2022-12-19 11:00:09.734674+0100 iosApp[65648:2045684] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/ConfigureAuthorization.swift Starting execution
2022-12-19 11:00:09.734707+0100 iosApp[65648:2045682] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configuringAuthorization" =     {
        "AuthenticationState.signedOut" =         {
            lastKnownUserName = "(nil)";
        };
        "AuthorizationState.configured" =         {
        };
    };
}
2022-12-19 11:00:09.734723+0100 iosApp[65648:2045684] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/ConfigureAuthorization.swift Sending event AuthEvent.authorizationConfigured
2022-12-19 11:00:09.735068+0100 iosApp[65648:2045686] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configured" =     {
        "AuthenticationState.signedOut" =         {
            lastKnownUserName = "(nil)";
        };
        "AuthorizationState.configured" =         {
        };
    };
}
2022-12-19 11:00:09.805350+0100 iosApp[65648:2045684] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configured" =     {
        "AuthenticationState.signedOut" =         {
            lastKnownUserName = "(nil)";
        };
        "AuthorizationState.fetchingUnAuthSession" =         {
            "FetchSessionState.notStarted" =             {
            };
        };
    };
}
2022-12-19 11:00:09.805439+0100 iosApp[65648:2045682] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitializeFetchUnAuthSession.swift Starting execution
2022-12-19 11:00:09.805488+0100 iosApp[65648:2045682] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitializeFetchUnAuthSession.swift Sending event FetchAuthSessionEvent.throwError
2022-12-19 11:00:09.805843+0100 iosApp[65648:2045682] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InformSessionError.swift Starting execution
2022-12-19 11:00:09.805889+0100 iosApp[65648:2045682] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InformSessionError.swift Sending event AuthorizationEvent.receivedSessionError
2022-12-19 11:00:09.807211+0100 iosApp[65648:2045684] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configured" =     {
        "AuthenticationState.signedOut" =         {
            lastKnownUserName = "(nil)";
        };
        "AuthorizationState.fetchingUnAuthSession" =         {
            "FetchSessionState.error" =             {
                error = "AWSCognitoAuthPlugin.FetchSessionError.noIdentityPool";
            };
        };
    };
}
2022-12-19 11:00:09.808553+0100 iosApp[65648:2045684] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configured" =     {
        "AuthenticationState.signedOut" =         {
            lastKnownUserName = "(nil)";
        };
        "AuthorizationState.error" =         {
            Error = "AWSCognitoAuthPlugin.AuthorizationError.sessionError(AWSCognitoAuthPlugin.FetchSessionError.noIdentityPool, noCredentials)";
        };
    };
}
2022-12-19 11:00:12.112559+0100 iosApp[65648:2045682] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configured" =     {
        "AuthenticationState.signedOut" =         {
            lastKnownUserName = "(nil)";
        };
        "AuthorizationState.refreshingSession" =         {
            existing = noCredentials;
            refreshState =             {
                "RefreshSessionState.notStarted" =                 {
                };
            };
        };
    };
}
2022-12-19 11:00:12.113301+0100 iosApp[65648:2045686] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitializeRefreshSession.swift Starting execution
2022-12-19 11:00:12.113612+0100 iosApp[65648:2045686] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitializeRefreshSession.swift Sending event RefreshSessionEvent.throwError
2022-12-19 11:00:12.114470+0100 iosApp[65648:2045686] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InformSessionError.swift Starting execution
2022-12-19 11:00:12.114569+0100 iosApp[65648:2045686] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InformSessionError.swift Sending event AuthorizationEvent.receivedSessionError
2022-12-19 11:00:12.114754+0100 iosApp[65648:2045682] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configured" =     {
        "AuthenticationState.signedOut" =         {
            lastKnownUserName = "(nil)";
        };
        "AuthorizationState.refreshingSession" =         {
            existing = noCredentials;
            refreshState =             {
                "RefreshSessionState.error" =                 {
                    error = "AWSCognitoAuthPlugin.FetchSessionError.noCredentialsToRefresh";
                };
            };
        };
    };
}
2022-12-19 11:00:12.115910+0100 iosApp[65648:2045682] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configured" =     {
        "AuthenticationState.signedOut" =         {
            lastKnownUserName = "(nil)";
        };
        "AuthorizationState.error" =         {
            Error = "AWSCognitoAuthPlugin.AuthorizationError.sessionError(AWSCognitoAuthPlugin.FetchSessionError.noCredentialsToRefresh, noCredentials)";
        };
    };
}
2022-12-19 11:00:15.100161+0100 iosApp[65648:2045686] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Starting execution
2022-12-19 11:00:15.100172+0100 iosApp[65648:2045682] [AWSCognitoAuthPlugin] Credential Store state change:

loadingStoredCredentials
2022-12-19 11:00:15.100833+0100 iosApp[65648:2045686] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Retreiving credential deviceMetadata(username: "+385915013359")
2022-12-19 11:00:15.111150+0100 iosApp[65648:2045686] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Sending event CredentialStoreEvent.throwError
2022-12-19 11:00:15.111290+0100 iosApp[65648:2045686] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Starting execution
2022-12-19 11:00:15.111294+0100 iosApp[65648:2045682] [AWSCognitoAuthPlugin] Credential Store state change:

error(KeychainStoreError: Unable to find the keychain item
Recovery suggestion: This should not happen. There is a possibility that there is a bug if this error persists. Please take a look at https://github.com/aws-amplify/amplify-ios/issues to see if there are any existing issues that match your scenario, and file an issue with the details of the bug if there isn't. Issue encountered at:
file: /Users/jurajbegovac/Library/Developer/Xcode/DerivedData/iosApp-ceumhqdilblatpbydusmyekmjbds/SourcePackages/checkouts/amplify-swift/AmplifyPlugins/Core/AWSPluginsCore/Keychain/KeychainStoreError.swift
function: recoverySuggestion
line: 69)
2022-12-19 11:00:15.111367+0100 iosApp[65648:2045686] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Sending event CredentialStoreEvent.moveToIdleState
2022-12-19 11:00:15.111444+0100 iosApp[65648:2045682] [AWSCognitoAuthPlugin] Credential Store state change:

idle
2022-12-19 11:00:15.111555+0100 iosApp[65648:2045683] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Starting execution
2022-12-19 11:00:15.111566+0100 iosApp[65648:2045682] [AWSCognitoAuthPlugin] Credential Store state change:

loadingStoredCredentials
2022-12-19 11:00:15.111625+0100 iosApp[65648:2045683] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Retreiving credential asfDeviceId(username: "+385915013359")
2022-12-19 11:00:15.114595+0100 iosApp[65648:2045683] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Sending event CredentialStoreEvent.throwError
2022-12-19 11:00:15.114732+0100 iosApp[65648:2045683] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Starting execution
2022-12-19 11:00:15.114745+0100 iosApp[65648:2045682] [AWSCognitoAuthPlugin] Credential Store state change:

error(KeychainStoreError: Unable to find the keychain item
Recovery suggestion: This should not happen. There is a possibility that there is a bug if this error persists. Please take a look at https://github.com/aws-amplify/amplify-ios/issues to see if there are any existing issues that match your scenario, and file an issue with the details of the bug if there isn't. Issue encountered at:
file: /Users/jurajbegovac/Library/Developer/Xcode/DerivedData/iosApp-ceumhqdilblatpbydusmyekmjbds/SourcePackages/checkouts/amplify-swift/AmplifyPlugins/Core/AWSPluginsCore/Keychain/KeychainStoreError.swift
function: recoverySuggestion
line: 69)
2022-12-19 11:00:15.114769+0100 iosApp[65648:2045683] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Sending event CredentialStoreEvent.moveToIdleState
2022-12-19 11:00:15.114887+0100 iosApp[65648:2045683] [AWSCognitoAuthPlugin] Credential Store state change:

idle
2022-12-19 11:00:15.114977+0100 iosApp[65648:2045682] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/StoreCredentials.swift Starting execution
2022-12-19 11:00:15.114984+0100 iosApp[65648:2045683] [AWSCognitoAuthPlugin] Credential Store state change:

storingCredentials
2022-12-19 11:00:15.123888+0100 iosApp[65648:2045682] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/StoreCredentials.swift Sending event CredentialStoreEvent.completedOperation
2022-12-19 11:00:15.123992+0100 iosApp[65648:2045682] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Starting execution
2022-12-19 11:00:15.124029+0100 iosApp[65648:2045682] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Sending event CredentialStoreEvent.moveToIdleState
2022-12-19 11:00:15.124692+0100 iosApp[65648:2045683] [AWSCognitoAuthPlugin] Credential Store state change:

success(AWSCognitoAuthPlugin.CredentialStoreData.asfDeviceId("EE262985-A013-4B7B-8C7B-B064279C1EA7", "<REDACTED-phone-number"))
2022-12-19 11:00:15.124786+0100 iosApp[65648:2045683] [AWSCognitoAuthPlugin] Credential Store state change:

idle
2022-12-19T11:00:15+0100 info CognitoIdentityProviderClient : [Logging] Request: POST https:443
 Path: /
 Content-Length: 6499,
User-Agent: aws-sdk-swift/1.0 api/cognito-identity-provider/1.0 os/iOS/16.1.0 lang/swift/5.7 lib/amplify-ios/2.2.0,
x-amz-user-agent: aws-sdk-swift/1.0,
Host: cognito-idp.eu-west-1.amazonaws.com,
X-Amz-Target: AWSCognitoIdentityProviderService.SignUp,
Content-Type: application/x-amz-json-1.1
 Optional([])
2022-12-19T11:00:15+0100 info SerialExecutor : [Logging] Creating connection pool for Optional("https://cognito-idp.eu-west-1.amazonaws.com/?")with max connections: 50
2022-12-19T11:00:15+0100 info CRTClientEngine : [Logging] Connection was acquired to: Optional("https://cognito-idp.eu-west-1.amazonaws.com/?")
2022-12-19T11:00:15+0100 info CRTClientEngine : [Logging] headers were received
2022-12-19T11:00:15+0100 info CRTClientEngine : [Logging] headers were received
2022-12-19T11:00:15+0100 info CRTClientEngine : [Logging] headers were received
2022-12-19T11:00:15+0100 info CRTClientEngine : [Logging] headers were received
2022-12-19T11:00:15+0100 info CRTClientEngine : [Logging] headers were received
2022-12-19T11:00:15+0100 info CRTClientEngine : [Logging] headers were received
2022-12-19T11:00:15+0100 info CRTClientEngine : [Logging] headers were received
2022-12-19T11:00:15+0100 info CRTClientEngine : [Logging] header block is done
2022-12-19T11:00:15+0100 info CRTClientEngine : [Logging] incoming data
2022-12-19T11:00:15+0100 info CRTClientEngine : [Logging] stream completed
2022-12-19T11:00:15+0100 info SerialExecutor : [Logging] Connection to endpoint: Optional("https://cognito-idp.eu-west-1.amazonaws.com/?") is closing
performSignIn
2022-12-19 11:00:15.641551+0100 iosApp[65648:2045681] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IntializeSignInFlow.swift Starting execution
2022-12-19 11:00:15.641692+0100 iosApp[65648:2045681] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Starting execution
2022-12-19 11:00:15.641820+0100 iosApp[65648:2045681] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Retreiving credential deviceMetadata(username: "+385915013359")
2022-12-19 11:00:15.641831+0100 iosApp[65648:2045682] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configured" =     {
        "AuthenticationState.signingIn" =         {
            "SignInState.notStarted" =             {
            };
        };
        "AuthorizationState.signingIn" =         {
        };
    };
}
2022-12-19 11:00:15.641920+0100 iosApp[65648:2045682] [AWSCognitoAuthPlugin] Credential Store state change:

loadingStoredCredentials
2022-12-19 11:00:15.644981+0100 iosApp[65648:2045681] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Sending event CredentialStoreEvent.throwError
2022-12-19 11:00:15.645077+0100 iosApp[65648:2045681] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Starting execution
2022-12-19 11:00:15.645108+0100 iosApp[65648:2045682] [AWSCognitoAuthPlugin] Credential Store state change:

error(KeychainStoreError: Unable to find the keychain item
Recovery suggestion: This should not happen. There is a possibility that there is a bug if this error persists. Please take a look at https://github.com/aws-amplify/amplify-ios/issues to see if there are any existing issues that match your scenario, and file an issue with the details of the bug if there isn't. Issue encountered at:
file: /Users/jurajbegovac/Library/Developer/Xcode/DerivedData/iosApp-ceumhqdilblatpbydusmyekmjbds/SourcePackages/checkouts/amplify-swift/AmplifyPlugins/Core/AWSPluginsCore/Keychain/KeychainStoreError.swift
function: recoverySuggestion
line: 69)
2022-12-19 11:00:15.645122+0100 iosApp[65648:2045681] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Sending event CredentialStoreEvent.moveToIdleState
2022-12-19 11:00:15.645218+0100 iosApp[65648:2045682] [AWSCognitoAuthPlugin] Credential Store state change:

idle
2022-12-19 11:00:15.657963+0100 iosApp[65648:2045681] [AWSCognitoAuthPlugin] No existing device metadata found. AuthEnvironment(configuration: AWSCognitoAuthPlugin.AuthConfiguration.userPools(["clientId": "3c22****pc70", "region": "<REDACTED>", "hostedUI": "N/A", "poolId": "eu-w****6K4O", "pinpointAppId": "(nil)", "clientSecret": "1a****b1", "endpoint": "N/A"]), userPoolConfigData: Optional(["clientId": "3c22****pc70", "region": "<REDACTED>", "hostedUI": "N/A", "poolId": "eu-w****6K4O", "pinpointAppId": "(nil)", "clientSecret": "1a****b1", "endpoint": "N/A"]), identityPoolConfigData: nil, authenticationEnvironment: Optional(AWSCognitoAuthPlugin.BasicAuthenticationEnvironment(srpSignInEnvironment: AWSCognitoAuthPlugin.BasicSRPSignInEnvironment(srpAuthEnvironment: AWSCognitoAuthPlugin.BasicSRPAuthEnvironment(userPoolConfiguration: ["poolId": "eu-w****6K4O", "clientId": "3c22****pc70", "pinpointAppId": "(nil)", "endpoint": "N/A", "clientSecret": "1a****b1", "hostedUI": "N/A", "region": "<REDACTED>"], cognitoUserPoolFactory: (Function), eventIDFactory: (Function), srpClientFactory: (Function), srpConfiguration: (nHexValue: "FFFFFFFFFFFFFFFFC90FDAA22168C234C4C6628B80DC1CD129024E088A67CC74020BBEA63B139B22514A08798E3404DDEF9519B3CD3A431B302B0A6DF25F14374FE1356D6D51C245E485B576625E7EC6F44C42E9A637ED6B0BFF5CB6F406B7EDEE386BFB5A899FA5AE9F24117C4B1FE649286651ECE45B3DC2007CB8A163BF0598DA48361C55D39A69163FA8FD24CF5F83655D23DCA3AD961C62F356208552BB9ED529077096966D670C354E4ABC9804F1746C08CA18217C32905E462E36CE3BE39E772C180E86039B2783A2EC07A28FB5C55DF06F4C52C9DE2BCBF6955817183995497CEA956AE515D2261898FA051015728E5A8AAAC42DAD33170D04507A33A85521ABDF1CBA64ECFB850458DBEF0A8AEA71575D060C7DB3970F85A6E1E4C7ABF5AE8CDB0933D71E8C94E04A25619DCEE3D2261AD2EE6BF12FFA06D98A0864D87602733EC86A64521F2B18177B200CBBE117577A615D6C770988C0BAD946E208E24FA074E5AB3143DB5BFCE0FD108E4B82D120A93AD2CAFFFFFFFFFFFFFFFF", gHexValue: "2"))), userPoolEnvironment: AWSCognitoAuthPlugin.BasicUserPoolEnvironment(userPoolConfiguration: ["pinpointAppId": "(nil)", "hostedUI": "N/A", "endpoint": "N/A", "poolId": "eu-w****6K4O", "clientId": "3c22****pc70", "region": "<REDACTED>", "clientSecret": "1a****b1"], cognitoUserPoolFactory: (Function), cognitoUserPoolASFFactory: (Function), cognitoUserPoolAnalyticsHandlerFactory: (Function)), hostedUIEnvironment: nil)), authorizationEnvironment: nil, credentialsClient: AWSCognitoAuthPlugin.CredentialStoreOperationClient, logger: Amplify.OSLogWrapper)
2022-12-19 11:00:15.658558+0100 iosApp[65648:2045681] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IntializeSignInFlow.swift Sending event SignInEvent.initiateCustomSignInWithSRP
2022-12-19 11:00:15.660118+0100 iosApp[65648:2045681] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/StartSRPFlow.swift Start execution
2022-12-19 11:00:15.660172+0100 iosApp[65648:2045681] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/StartSRPFlow.swift Sending event SignInEvent.initiateSignInWithSRP
2022-12-19 11:00:15.660233+0100 iosApp[65648:2045682] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configured" =     {
        "AuthenticationState.signingIn" =         {
            "SignInState.signingInWithSRPCustom" =             {
                SRPSignInStaet =                 {
                    "SRPSignInState.notStarted" =                     {
                    };
                };
            };
        };
        "AuthorizationState.signingIn" =         {
        };
    };
}
2022-12-19 11:00:15.660394+0100 iosApp[65648:2045681] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitiateAuthSRP.swift Starting execution
2022-12-19 11:00:15.661791+0100 iosApp[65648:2045683] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configured" =     {
        "AuthenticationState.signingIn" =         {
            "SignInState.signingInWithSRPCustom" =             {
                SRPSignInStaet =                 {
                    "SRPSignInState.initiatingSRPA" =                     {
                        clientMetadata =                         {
                        };
                        password = "<REDACTED>";
                        signInMethod = "AWSCognitoAuthPlugin.SignInMethod.apiBased(AWSCognitoAuthPlugin.AuthFlowType.customWithSRP)";
                        username = "+3*********59";
                    };
                };
            };
        };
        "AuthorizationState.signingIn" =         {
        };
    };
}
2022-12-19 11:00:15.665843+0100 iosApp[65648:2045681] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Starting execution
2022-12-19 11:00:15.665860+0100 iosApp[65648:2045683] [AWSCognitoAuthPlugin] Credential Store state change:

loadingStoredCredentials
2022-12-19 11:00:15.665920+0100 iosApp[65648:2045681] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Retreiving credential deviceMetadata(username: "+385915013359")
2022-12-19 11:00:15.668747+0100 iosApp[65648:2045681] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Sending event CredentialStoreEvent.throwError
2022-12-19 11:00:15.668828+0100 iosApp[65648:2045681] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Starting execution
2022-12-19 11:00:15.668845+0100 iosApp[65648:2045683] [AWSCognitoAuthPlugin] Credential Store state change:

error(KeychainStoreError: Unable to find the keychain item
Recovery suggestion: This should not happen. There is a possibility that there is a bug if this error persists. Please take a look at https://github.com/aws-amplify/amplify-ios/issues to see if there are any existing issues that match your scenario, and file an issue with the details of the bug if there isn't. Issue encountered at:
file: /Users/jurajbegovac/Library/Developer/Xcode/DerivedData/iosApp-ceumhqdilblatpbydusmyekmjbds/SourcePackages/checkouts/amplify-swift/AmplifyPlugins/Core/AWSPluginsCore/Keychain/KeychainStoreError.swift
function: recoverySuggestion
line: 69)
2022-12-19 11:00:15.668871+0100 iosApp[65648:2045681] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Sending event CredentialStoreEvent.moveToIdleState
2022-12-19 11:00:15.668937+0100 iosApp[65648:2045683] [AWSCognitoAuthPlugin] Credential Store state change:

idle
2022-12-19 11:00:15.668994+0100 iosApp[65648:2045683] [AWSCognitoAuthPlugin] Credential Store state change:

loadingStoredCredentials
2022-12-19 11:00:15.669025+0100 iosApp[65648:2045681] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Starting execution
2022-12-19 11:00:15.669091+0100 iosApp[65648:2045681] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Retreiving credential asfDeviceId(username: "+385915013359")
2022-12-19 11:00:15.671394+0100 iosApp[65648:2045681] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Sending event CredentialStoreEvent.completedOperation
2022-12-19 11:00:15.671474+0100 iosApp[65648:2045681] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Starting execution
2022-12-19 11:00:15.671506+0100 iosApp[65648:2045683] [AWSCognitoAuthPlugin] Credential Store state change:

success(AWSCognitoAuthPlugin.CredentialStoreData.asfDeviceId("EE262985-A013-4B7B-8C7B-B064279C1EA7", "+385915013359"))
2022-12-19 11:00:15.671511+0100 iosApp[65648:2045681] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Sending event CredentialStoreEvent.moveToIdleState
2022-12-19 11:00:15.671594+0100 iosApp[65648:2045683] [AWSCognitoAuthPlugin] Credential Store state change:

idle
2022-12-19 11:00:15.673164+0100 iosApp[65648:2045681] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitiateAuthSRP.swift Starting execution
2022-12-19T11:00:15+0100 info CognitoIdentityProviderClient : [Logging] Request: POST https:443
 Path: /
 Content-Type: application/x-amz-json-1.1,
x-amz-user-agent: aws-sdk-swift/1.0,
User-Agent: aws-sdk-swift/1.0 api/cognito-identity-provider/1.0 os/iOS/16.1.0 lang/swift/5.7 lib/amplify-ios/2.2.0,
Host: cognito-idp.eu-west-1.amazonaws.com,
Content-Length: 6786,
X-Amz-Target: AWSCognitoIdentityProviderService.InitiateAuth
 Optional([])
2022-12-19T11:00:15+0100 info SerialExecutor : [Logging] Creating connection pool for Optional("https://cognito-idp.eu-west-1.amazonaws.com/?")with max connections: 50
2022-12-19T11:00:16+0100 info CRTClientEngine : [Logging] Connection was acquired to: Optional("https://cognito-idp.eu-west-1.amazonaws.com/?")
2022-12-19T11:00:17+0100 info CRTClientEngine : [Logging] headers were received
2022-12-19T11:00:17+0100 info CRTClientEngine : [Logging] headers were received
2022-12-19T11:00:17+0100 info CRTClientEngine : [Logging] headers were received
2022-12-19T11:00:17+0100 info CRTClientEngine : [Logging] headers were received
2022-12-19T11:00:17+0100 info CRTClientEngine : [Logging] headers were received
2022-12-19T11:00:17+0100 info CRTClientEngine : [Logging] header block is done
2022-12-19T11:00:17+0100 info CRTClientEngine : [Logging] incoming data
2022-12-19T11:00:17+0100 info CRTClientEngine : [Logging] stream completed
2022-12-19 11:00:17.013544+0100 iosApp[65648:2045681] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitiateAuthSRP.swift InitiateAuth response success
2022-12-19 11:00:17.017576+0100 iosApp[65648:2045681] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitiateAuthSRP.swift Sending event SignInEvent(data: nil, id: "6B636947-5177-4E1B-AE6D-ADB0E9FFC248", eventType: AWSCognitoAuthPlugin.SignInEvent.EventType.receivedChallenge(AWSCognitoAuthPlugin.RespondToAuthChallenge(challenge: AWSCognitoIdentityProvider.CognitoIdentityProviderClientTypes.ChallengeNameType.customChallenge, username: "0e70e643-2534-4fb5-ba8d-3ca4e1c4c7e0", session: Optional("AYABeIUQp3iPtEZRsIYb8_37W44AHQABAAdTZXJ2aWNlABBDb2duaXRvVXNlclBvb2xzAAEAB2F3cy1rbXMAS2Fybjphd3M6a21zOmV1LXdlc3QtMTo0NTU0NTg0OTMwODE6a2V5L2FiN2U3M2UzLWU2NDEtNDk5Zi1iNzc0LWZkZmM1MWM3NzFhYQC4AQIBAHigzwqzlp0D8sA0ltw8SHdsZPaJakxa-4NzPukgGo7dmgFHfCwNuz6Qj-9fnXXX5p7AAAAAfjB8BgkqhkiG9w0BBwagbzBtAgEAMGgGCSqGSIb3DQEHATAeBglghkgBZQMEAS4wEQQMakPGxsF_O5LKUpMKAgEQgDvdsMCZ9t-ZkdfRKGrTsMzWNO524kdrp1iqXjwr9w2Kl0di0I_JdCOi0jm10drChbs9gu8tWH5eBYyFzwIAAAAADAAAEAAAAAAAAAAAAAAAAABqXLY-bQ05dyTk7NBAWHCY_____wAAAAEAAAAAAAAAAAAAAAEAAAFCOlojgtepDGCNPhtofiBCzVQIDKA81lNR0pcmry4F8yRhWxIY8AllVYwAQB3-PmMq1YSjXYfKWMtLdTrQsvt564Xqo3RrKi4DIGsHkWBg-1kqrHIpy1Ay22h0Rs-D4DXW0bHPVQ4FM1wPgB_23a33MRv3ei_zqytytFc3WdlV5P-f5KYcsTlF15tcuVUXNNLEYUq9yzRXbKCb1nUy5GXuAXPryfgQNGutSvmHFlKeprZdJHh7mmzWe8JCMsWVXV17EH6kD7FbGoISeMyD_hnXB8D7ziA5TP66p0s3YzWBHHmokcaCWh9tBxotF-bwsI-QWS34yWI0MFJBlVodDA63qSuckxoa7lSl6Vo6zhIEMQzhIFkLeto4nBy6UKo13ahSMy8L0R3XPg1aOoQ99lZL30b-0TmRrUZSoLLGEHkdW1_3e-IHOF1F_4fvWanItoLQQKc"), parameters: Optional(["USERNAME": "0e70e643-2534-4fb5-ba8d-3ca4e1c4c7e0"]))), time: nil)
2022-12-19T11:00:17+0100 info SerialExecutor : [Logging] Connection to endpoint: Optional("https://cognito-idp.eu-west-1.amazonaws.com/?") is closing
2022-12-19 11:00:17.018630+0100 iosApp[65648:2045681] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitializeResolveChallenge.swift Starting execution
2022-12-19 11:00:17.018701+0100 iosApp[65648:2045681] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitializeResolveChallenge.swift Sending event SignInChallengeEvent.waitForAnswer
2022-12-19 11:00:17.019774+0100 iosApp[65648:2045683] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configured" =     {
        "AuthenticationState.signingIn" =         {
            "SignInState.resolvingChallenge" =             {
                "SignInChallengeState.notStarted" =                 {
                };
                challengeType = "AWSCognitoAuthPlugin.AuthChallengeType.customChallenge";
                signInMethod = "AWSCognitoAuthPlugin.SignInMethod.apiBased(AWSCognitoAuthPlugin.AuthFlowType.customWithSRP)";
            };
        };
        "AuthorizationState.signingIn" =         {
        };
    };
}
2022-12-19 11:00:17.020384+0100 iosApp[65648:2045683] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configured" =     {
        "AuthenticationState.signingIn" =         {
            "SignInState.resolvingChallenge" =             {
                "SignInChallengeState.waitingForAnswer" =                 {
                    challenge = "AWSCognitoIdentityProvider.CognitoIdentityProviderClientTypes.ChallengeNameType.customChallenge";
                    username = "0e********************************e0";
                };
                challengeType = "AWSCognitoAuthPlugin.AuthChallengeType.customChallenge";
                signInMethod = "AWSCognitoAuthPlugin.SignInMethod.apiBased(AWSCognitoAuthPlugin.AuthFlowType.customWithSRP)";
            };
        };
        "AuthorizationState.signingIn" =         {
        };
    };
}
SignInResult: com.wesports.data.common.aws.SignInResult.WaitForCredentialConfirmation@2520a50

Thank you for the logs, @JurajBegovac  this gives us more insight into the internals now. Looks like the auth plugin is waiting for confirm signIn api call to be invoked to continue the custom auth flow. Are you invoking Amplify.Auth.confirmSignIn in your flow?

Speaking for myself, I have the same logs and I am indeed invoking the confirmSignIn method with withSRP strategy (my custom lambda handles the SRP_A attribute. I have tried withoutSRP and updating my Define Auth Challenge lambda to match the example in the Amplify docs, but I am still facing this same issue.

Can you retry and test with the latest Amplify version 2.2.1

It is still not working after pulling in the new Amplify version. I was poking around today trying to see if I could get anything to work and I deleted the user I was trying to sign in with and created a new user with the same phone number. This may be unrelated, but I witnessed new behavior that I had not seen since the last version of Amplify I had (1.5X). I called .signUp, then .confirmSignUp with the confirmation code, and that was successful (yay!). However, then I saw these logs:
Confirm signUp succeeded
2022-12-21 09:00:18.117938-0800 radarios[24248:4410762] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitializeRefreshSession.swift Starting execution
2022-12-21 09:00:18.117990-0800 radarios[24248:4410762] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitializeRefreshSession.swift Sending event RefreshSessionEvent.throwError
2022-12-21 09:00:18.118224-0800 radarios[24248:4411353] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configured" =     {
        "AuthenticationState.signedOut" =         {
            lastKnownUserName = "(nil)";
        };
        "AuthorizationState.refreshingSession" =         {
            existing = noCredentials;
            refreshState =             {
                "RefreshSessionState.notStarted" =                 {
                };
            };
        };
    };
}
2022-12-21 09:00:18.118367-0800 radarios[24248:4410762] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InformSessionError.swift Starting execution
2022-12-21 09:00:18.118391-0800 radarios[24248:4410762] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InformSessionError.swift Sending event AuthorizationEvent.receivedSessionError
2022-12-21 09:00:18.118409-0800 radarios[24248:4411353] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configured" =     {
        "AuthenticationState.signedOut" =         {
            lastKnownUserName = "(nil)";
        };
        "AuthorizationState.refreshingSession" =         {
            existing = noCredentials;
            refreshState =             {
                "RefreshSessionState.error" =                 {
                    error = "AWSCognitoAuthPlugin.FetchSessionError.noCredentialsToRefresh";
                };
            };
        };
    };
}
2022-12-21 09:00:18.118592-0800 radarios[24248:4411353] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configured" =     {
        "AuthenticationState.signedOut" =         {
            lastKnownUserName = "(nil)";
        };
        "AuthorizationState.error" =         {
            Error = "AWSCognitoAuthPlugin.AuthorizationError.sessionError(AWSCognitoAuthPlugin.FetchSessionError.noCredentialsToRefresh, noCredentials)";
        };
    };
}
AuthError: There is no user signed in to retreive cognito tokens
Recovery suggestion: Call Auth.signIn to sign in a user and then call Auth.fetchSession

When I relaunched my app - I was no longer signed in (thus having to go back through the broken sign in flow again, sigh). Hopefully this information is relevant to the case.

I know it's the holiday season, so I'm not expecting much progress on this right now. However, I do see this was marked as pending response from requester. As I am not the requester but I am affected by the same issue, should I reopen a new ticket or can we keep this open to continue tracking this issue?

Hi @patrickjohnson97
Invoking Amplify.Auth.signUp does not automatically signIn the user. You need to invoke Amplify.Auth.signIn and check its result, if the result next step  is .done (result.nextStep == .done) the user is authenticated. If it is not .done you need to invoke subsequent api as mentioned here - https://docs.amplify.aws/lib/auth/signin_next_steps/q/platform/ios
Once the user is authenticated your can call other apis like Amplify.Auth.fetchAuthsession to get authenticated credentials.
From your logs it is not clear regarding what response you are getting when you invoke Amplify.Auth.signIn.

As I am not the requester but I am affected by the same issue, should I reopen a new ticket or can we keep this open to continue tracking this issue?

We are still trying to figure out if your issue is same as the requester's, for now we can keep this GitHub issue assuming that they are the same.
@JurajBegovac are you still facing the same issue with the latest Amplify swift release?

@royjit Just to clarify - I am still seeing the aforementioned hanging confirm sign in process. Here is every log I have for the entire auth process (starting immediately after I press the "Sign in" button on my app:
Signing in with radar...
2022-12-30 14:05:47.951377-0800 radarios[6472:2019045] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IntializeSignInFlow.swift Starting execution
2022-12-30 14:05:47.951437-0800 radarios[6472:2019048] [AWSCognitoAuthPlugin] Credential Store state change:

loadingStoredCredentials
2022-12-30 14:05:47.951457-0800 radarios[6472:2019045] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Starting execution
2022-12-30 14:05:47.951483-0800 radarios[6472:2019042] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configured" =     {
        "AuthenticationState.signingIn" =         {
            "SignInState.notStarted" =             {
            };
        };
        "AuthorizationState.signingIn" =         {
        };
    };
}
2022-12-30 14:05:47.952248-0800 radarios[6472:2019045] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Retreiving credential deviceMetadata(username: "<REDACTED>")
2022-12-30 14:05:47.958872-0800 radarios[6472:2019045] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Sending event CredentialStoreEvent.throwError
2022-12-30 14:05:47.958907-0800 radarios[6472:2019045] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Starting execution
2022-12-30 14:05:47.958914-0800 radarios[6472:2019045] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Sending event CredentialStoreEvent.moveToIdleState
2022-12-30 14:05:47.959278-0800 radarios[6472:2019042] [AWSCognitoAuthPlugin] Credential Store state change:

error(KeychainStoreError: Unable to find the keychain item
Recovery suggestion: This should not happen. There is a possibility that there is a bug if this error persists. Please take a look at https://github.com/aws-amplify/amplify-ios/issues to see if there are any existing issues that match your scenario, and file an issue with the details of the bug if there isn't. Issue encountered at:
file: /Users/patrickjohnson/Library/Developer/Xcode/DerivedData/radarios-dknagqfhvptgcvcevboslsbwdhqv/SourcePackages/checkouts/amplify-swift/AmplifyPlugins/Core/AWSPluginsCore/Keychain/KeychainStoreError.swift
function: recoverySuggestion
line: 69)
2022-12-30 14:05:47.959298-0800 radarios[6472:2019042] [AWSCognitoAuthPlugin] Credential Store state change:

idle
2022-12-30 14:05:47.973842-0800 radarios[6472:2019045] [AWSCognitoAuthPlugin] No existing device metadata found. AuthEnvironment(configuration: AWSCognitoAuthPlugin.AuthConfiguration.userPoolsAndIdentityPools(["clientId": "6num****35nf", "poolId": "us-w****54x6", "clientSecret": "(nil)", "region": "<REDACTED>", "hostedUI": "[\"clientId\": \"6num****35nf\", \"clientSecret\": \"(nil)\", \"oauth\": \"[\\\"domain\\\": \\\"rada****.com\\\", \\\"signInRedirectURI\\\": \\\"rada***s://\\\", \\\"signOutRedirectURI\\\": \\\"rada***s://\\\"]\"]", "pinpointAppId": "(nil)", "endpoint": "N/A"], ["region": "<REDACTED>", "poolId": "us-w****9f49"]), userPoolConfigData: Optional(["clientId": "6num****35nf", "poolId": "us-w****54x6", "clientSecret": "(nil)", "region": "<REDACTED>", "hostedUI": "[\"clientId\": \"6num****35nf\", \"clientSecret\": \"(nil)\", \"oauth\": \"[\\\"domain\\\": \\\"rada****.com\\\", \\\"signInRedirectURI\\\": \\\"rada***s://\\\", \\\"signOutRedirectURI\\\": \\\"rada***s://\\\"]\"]", "pinpointAppId": "(nil)", "endpoint": "N/A"]), identityPoolConfigData: Optional(["region": "<REDACTED>", "poolId": "us-w****9f49"]), authenticationEnvironment: Optional(AWSCognitoAuthPlugin.BasicAuthenticationEnvironment(srpSignInEnvironment: AWSCognitoAuthPlugin.BasicSRPSignInEnvironment(srpAuthEnvironment: AWSCognitoAuthPlugin.BasicSRPAuthEnvironment(userPoolConfiguration: ["endpoint": "N/A", "poolId": "us-w****54x6", "pinpointAppId": "(nil)", "region": "<REDACTED>", "clientSecret": "(nil)", "clientId": "6num****35nf", "hostedUI": "[\"oauth\": \"[\\\"signInRedirectURI\\\": \\\"rada***s://\\\", \\\"domain\\\": \\\"rada****.com\\\", \\\"signOutRedirectURI\\\": \\\"rada***s://\\\"]\", \"clientId\": \"6num****35nf\", \"clientSecret\": \"(nil)\"]"], cognitoUserPoolFactory: (Function), eventIDFactory: (Function), srpClientFactory: (Function), srpConfiguration: (nHexValue: "<REDACTED>", gHexValue: "2"))), userPoolEnvironment: AWSCognitoAuthPlugin.BasicUserPoolEnvironment(userPoolConfiguration: ["clientId": "6num****35nf", "poolId": "us-w****54x6", "clientSecret": "(nil)", "region": "<REDACTED>", "hostedUI": "[\"clientId\": \"6num****35nf\", \"clientSecret\": \"(nil)\", \"oauth\": \"[\\\"domain\\\": \\\"rada****.com\\\", \\\"signInRedirectURI\\\": \\\"rada***s://\\\", \\\"signOutRedirectURI\\\": \\\"rada***s://\\\"]\"]", "pinpointAppId": "(nil)", "endpoint": "N/A"], cognitoUserPoolFactory: (Function), cognitoUserPoolASFFactory: (Function), cognitoUserPoolAnalyticsHandlerFactory: (Function)), hostedUIEnvironment: Optional(AWSCognitoAuthPlugin.BasicHostedUIEnvironment(configuration: ["clientId": "6num****35nf", "clientSecret": "(nil)", "oauth": "[\"domain\": \"rada****.com\", \"signInRedirectURI\": \"rada***s://\", \"signOutRedirectURI\": \"rada***s://\"]"], hostedUISessionFactory: (Function), urlSessionFactory: (Function), randomStringFactory: (Function))))), authorizationEnvironment: Optional(AWSCognitoAuthPlugin.BasicAuthorizationEnvironment(identityPoolConfiguration: ["region": "<REDACTED>", "poolId": "us-w****9f49"], cognitoIdentityFactory: (Function), eventIDFactory: (Function))), credentialsClient: AWSCognitoAuthPlugin.CredentialStoreOperationClient, logger: Amplify.OSLogWrapper)
2022-12-30 14:05:47.974516-0800 radarios[6472:2019045] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IntializeSignInFlow.swift Sending event SignInEvent.initiateCustomSignInWithSRP
2022-12-30 14:05:47.975745-0800 radarios[6472:2019045] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/StartSRPFlow.swift Start execution
2022-12-30 14:05:47.975754-0800 radarios[6472:2019045] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/StartSRPFlow.swift Sending event SignInEvent.initiateSignInWithSRP
2022-12-30 14:05:47.975779-0800 radarios[6472:2019042] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configured" =     {
        "AuthenticationState.signingIn" =         {
            "SignInState.signingInWithSRPCustom" =             {
                SRPSignInStaet =                 {
                    "SRPSignInState.notStarted" =                     {
                    };
                };
            };
        };
        "AuthorizationState.signingIn" =         {
        };
    };
}
2022-12-30 14:05:47.975862-0800 radarios[6472:2019045] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitiateAuthSRP.swift Starting execution
2022-12-30 14:05:47.977267-0800 radarios[6472:2019048] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configured" =     {
        "AuthenticationState.signingIn" =         {
            "SignInState.signingInWithSRPCustom" =             {
                SRPSignInStaet =                 {
                    "SRPSignInState.initiatingSRPA" =                     {
                        clientMetadata =                         {
                        };
                        password = "(nil)";
                        signInMethod = "AWSCognitoAuthPlugin.SignInMethod.apiBased(AWSCognitoAuthPlugin.AuthFlowType.customWithSRP)";
                        username = "+1********58";
                    };
                };
            };
        };
        "AuthorizationState.signingIn" =         {
        };
    };
}
2022-12-30 14:05:47.979477-0800 radarios[6472:2019045] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Starting execution
2022-12-30 14:05:47.979484-0800 radarios[6472:2019048] [AWSCognitoAuthPlugin] Credential Store state change:

loadingStoredCredentials
2022-12-30 14:05:47.979496-0800 radarios[6472:2019045] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Retreiving credential deviceMetadata(username: "<REDACTED>")
2022-12-30 14:05:47.981078-0800 radarios[6472:2019045] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Sending event CredentialStoreEvent.throwError
2022-12-30 14:05:47.981099-0800 radarios[6472:2019045] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Starting execution
2022-12-30 14:05:47.981105-0800 radarios[6472:2019045] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Sending event CredentialStoreEvent.moveToIdleState
2022-12-30 14:05:47.981118-0800 radarios[6472:2019042] [AWSCognitoAuthPlugin] Credential Store state change:

error(KeychainStoreError: Unable to find the keychain item
Recovery suggestion: This should not happen. There is a possibility that there is a bug if this error persists. Please take a look at https://github.com/aws-amplify/amplify-ios/issues to see if there are any existing issues that match your scenario, and file an issue with the details of the bug if there isn't. Issue encountered at:
file: /Users/patrickjohnson/Library/Developer/Xcode/DerivedData/radarios-dknagqfhvptgcvcevboslsbwdhqv/SourcePackages/checkouts/amplify-swift/AmplifyPlugins/Core/AWSPluginsCore/Keychain/KeychainStoreError.swift
function: recoverySuggestion
line: 69)
2022-12-30 14:05:47.981130-0800 radarios[6472:2019042] [AWSCognitoAuthPlugin] Credential Store state change:

idle
2022-12-30 14:05:47.981134-0800 radarios[6472:2019045] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Starting execution
2022-12-30 14:05:47.981139-0800 radarios[6472:2019042] [AWSCognitoAuthPlugin] Credential Store state change:

loadingStoredCredentials
2022-12-30 14:05:47.981147-0800 radarios[6472:2019045] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Retreiving credential asfDeviceId(username: "+14053651058")
2022-12-30 14:05:47.982697-0800 radarios[6472:2019045] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Sending event CredentialStoreEvent.completedOperation
2022-12-30 14:05:47.982719-0800 radarios[6472:2019045] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Starting execution
2022-12-30 14:05:47.982725-0800 radarios[6472:2019045] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Sending event CredentialStoreEvent.moveToIdleState
2022-12-30 14:05:47.983648-0800 radarios[6472:2019048] [AWSCognitoAuthPlugin] Credential Store state change:

success(AWSCognitoAuthPlugin.CredentialStoreData.asfDeviceId("<REDACTED>", "<REDACTED>"))
2022-12-30 14:05:47.983665-0800 radarios[6472:2019048] [AWSCognitoAuthPlugin] Credential Store state change:

idle
2022-12-30 14:05:47.985732-0800 radarios[6472:2019045] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitiateAuthSRP.swift Starting execution
2022-12-30T14:05:47-0800 info CognitoIdentityProviderClient : [Logging] Request: POST https:443
 Path: /
 Host: cognito-idp.us-west-2.amazonaws.com,
User-Agent: aws-sdk-swift/1.0 api/cognito-identity-provider/1.0 os/iOS/16.2.0 lang/swift/5.7 lib/amplify-ios/2.2.1,
X-Amz-Target: AWSCognitoIdentityProviderService.InitiateAuth,
Content-Type: application/x-amz-json-1.1,
x-amz-user-agent: aws-sdk-swift/1.0,
Content-Length: 6632
 Optional([])
2022-12-30T14:05:47-0800 info SerialExecutor : [Logging] Creating connection pool for Optional("https://cognito-idp.us-west-2.amazonaws.com/?")with max connections: 50
2022-12-30T14:05:48-0800 info CRTClientEngine : [Logging] Connection was acquired to: Optional("https://cognito-idp.us-west-2.amazonaws.com/?")
2022-12-30T14:05:49-0800 info CRTClientEngine : [Logging] headers were received
2022-12-30T14:05:49-0800 info CRTClientEngine : [Logging] headers were received
2022-12-30T14:05:49-0800 info CRTClientEngine : [Logging] headers were received
2022-12-30T14:05:49-0800 info CRTClientEngine : [Logging] headers were received
2022-12-30T14:05:49-0800 info CRTClientEngine : [Logging] headers were received
2022-12-30T14:05:49-0800 info CRTClientEngine : [Logging] header block is done
2022-12-30T14:05:49-0800 info CRTClientEngine : [Logging] incoming data
2022-12-30T14:05:49-0800 info CRTClientEngine : [Logging] stream completed
2022-12-30 14:05:49.340789-0800 radarios[6472:2019048] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitiateAuthSRP.swift InitiateAuth response success
2022-12-30T14:05:49-0800 info SerialExecutor : [Logging] Connection to endpoint: Optional("https://cognito-idp.us-west-2.amazonaws.com/?") is closing
2022-12-30 14:05:49.351703-0800 radarios[6472:2019048] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitiateAuthSRP.swift Sending event SignInEvent(data: nil, id: "703A1D8E-2560-4A03-B144-CB387B13DFA5", eventType: AWSCognitoAuthPlugin.SignInEvent.EventType.receivedChallenge(AWSCognitoAuthPlugin.RespondToAuthChallenge(challenge: AWSCognitoIdentityProvider.CognitoIdentityProviderClientTypes.ChallengeNameType.customChallenge, username: "<REDACTED>", session: Optional("<REDACTED>"), parameters: Optional(["USERNAME": "<REDACTED>"]))), time: nil)
2022-12-30 14:05:49.352453-0800 radarios[6472:2019048] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitializeResolveChallenge.swift Starting execution
2022-12-30 14:05:49.352603-0800 radarios[6472:2019048] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitializeResolveChallenge.swift Sending event SignInChallengeEvent.waitForAnswer
GGGG confirmSignInWithCustomChallenge2022-12-30 14:05:49.355480-0800 radarios[6472:2019042] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configured" =     {
        "AuthenticationState.signingIn" =         {
            "SignInState.resolvingChallenge" =             {
                "SignInChallengeState.notStarted" =                 {
                };
                challengeType = "AWSCognitoAuthPlugin.AuthChallengeType.customChallenge";
                signInMethod = "AWSCognitoAuthPlugin.SignInMethod.apiBased(AWSCognitoAuthPlugin.AuthFlowType.customWithSRP)";
            };
        };
        "AuthorizationState.signingIn" =         {
        };
    };
}

2022-12-30 14:05:49.356672-0800 radarios[6472:2019042] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configured" =     {
        "AuthenticationState.signingIn" =         {
            "SignInState.resolvingChallenge" =             {
                "SignInChallengeState.waitingForAnswer" =                 {
                    challenge = "AWSCognitoIdentityProvider.CognitoIdentityProviderClientTypes.ChallengeNameType.customChallenge";
                    username = "45********************************b0";
                };
                challengeType = "AWSCognitoAuthPlugin.AuthChallengeType.customChallenge";
                signInMethod = "AWSCognitoAuthPlugin.SignInMethod.apiBased(AWSCognitoAuthPlugin.AuthFlowType.customWithSRP)";
            };
        };
        "AuthorizationState.signingIn" =         {
        };
    };
}
Confirming user... 895533

After this last log (which includes the OTP I am sending back), there are no more logs for any other operation I try to perform with Amplify.Auth. Any fetchAuthSession calls, sign in calls, everything is just unresponsive.

Thank you for the patience while we try to narrow down the root cause of this issue.
We are still trying to reproduce this behavior, from my testing this is what I found:

I could not reproduce the issue where calling Amplify.Auth.confirmSignIn is getting stuck.
But I found an issue where fetchAuthSession get stuck and all subsequent calls to Auth when a signIn is in progress.

Here is my branch royjit.fixfetchAuthSession that I am currently working on to fix this, and the PR https://github.com/aws-amplify/amplify-swift/pull/2653. Will you able to try the signIn flow with this branch?
For custom auth I used the following define auth lambda trigger:

Define auth lambda
  if (event.request.session.length === 1 &&
    event.request.session[0].challengeName === 'SRP_A') {
    event.response.issueTokens = false;
    event.response.failAuthentication = false;
    event.response.challengeName = 'CUSTOM_CHALLENGE';
  } else if (
    event.request.session.length === 2 &&
    event.request.session[1].challengeName === 'CUSTOM_CHALLENGE' &&
    event.request.session[1].challengeResult === true
  ) {
    event.response.issueTokens = true;
    event.response.failAuthentication = false;
  } else {
    event.response.issueTokens = false;
    event.response.failAuthentication = true;
  }

And my logs are here:

Log Messages for signIn
2023-01-03 20:27:46.264967-0800 AmplifyAuthSample[38816:428902] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IntializeSignInFlow.swift Starting execution
2023-01-03 20:27:46.265190-0800 AmplifyAuthSample[38816:428902] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Starting execution
2023-01-03 20:27:46.265503-0800 AmplifyAuthSample[38816:428907] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configured" =     {
        "AuthenticationState.signingIn" =         {
            "SignInState.notStarted" =             {
            };
        };
        "AuthorizationState.signingIn" =         {
        };
    };
}
2023-01-03 20:27:46.265838-0800 AmplifyAuthSample[38816:428907] [AWSCognitoAuthPlugin] Credential Store state change:

loadingStoredCredentials
2023-01-03 20:27:46.266146-0800 AmplifyAuthSample[38816:428902] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Retreiving credential deviceMetadata(username<EMAIL_ADDRESS>2023-01-03 20:27:46.270537-0800 AmplifyAuthSample[38816:428902] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Sending event CredentialStoreEvent.throwError
2023-01-03 20:27:46.270832-0800 AmplifyAuthSample[38816:428907] [AWSCognitoAuthPlugin] Credential Store state change:

error(KeychainStoreError: Unable to find the keychain item
Recovery suggestion: This should not happen. There is a possibility that there is a bug if this error persists. Please take a look at https://github.com/aws-amplify/amplify-ios/issues to see if there are any existing issues that match your scenario, and file an issue with the details of the bug if there isn't. Issue encountered at:
file: /Users/royji/work/iOS/amplify-swift/AmplifyPlugins/Core/AWSPluginsCore/Keychain/KeychainStoreError.swift
function: recoverySuggestion
line: 69)
2023-01-03 20:27:46.270811-0800 AmplifyAuthSample[38816:428902] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Starting execution
2023-01-03 20:27:46.270931-0800 AmplifyAuthSample[38816:428902] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Sending event CredentialStoreEvent.moveToIdleState
2023-01-03 20:27:46.271078-0800 AmplifyAuthSample[38816:428907] [AWSCognitoAuthPlugin] Credential Store state change:

idle
2023-01-03 20:27:46.279436-0800 AmplifyAuthSample[38816:428902] [AWSCognitoAuthPlugin] No existing device metadata found. AuthEnvironment(configuration: AWSCognitoAuthPlugin.AuthConfiguration.userPoolsAndIdentityPools(["hostedUI": "N/A", "poolId": "us-e****Amot", "endpoint": "N/A", "region": "<REDACTED>", "clientSecret": "(nil)", "pinpointAppId": "(nil)", "clientId": "xxx"], ["poolId": "xxx", "region": "<REDACTED>"]), userPoolConfigData: Optional(["hostedUI": "N/A", "poolId": "us-e****Amot", "endpoint": "N/A", "region": "<REDACTED>", "clientSecret": "(nil)", "pinpointAppId": "(nil)", "clientId": "xxx"]), identityPoolConfigData: Optional(["poolId": "xxx", "region": "<REDACTED>"]), authenticationEnvironment: Optional(AWSCognitoAuthPlugin.BasicAuthenticationEnvironment(srpSignInEnvironment: AWSCognitoAuthPlugin.BasicSRPSignInEnvironment(srpAuthEnvironment: AWSCognitoAuthPlugin.BasicSRPAuthEnvironment(userPoolConfiguration: ["poolId": "us-e****Amot", "region": "<REDACTED>", "endpoint": "N/A", "clientId": "xxx", "pinpointAppId": "(nil)", "clientSecret": "(nil)", "hostedUI": "N/A"], cognitoUserPoolFactory: (Function), eventIDFactory: (Function), srpClientFactory: (Function), srpConfiguration: (nHexValue: "xxx", gHexValue: "2"))), userPoolEnvironment: AWSCognitoAuthPlugin.BasicUserPoolEnvironment(userPoolConfiguration: ["endpoint": "N/A", "hostedUI": "N/A", "region": "<REDACTED>", "clientId": "xxx", "pinpointAppId": "(nil)", "clientSecret": "(nil)", "poolId": "us-e****Amot"], cognitoUserPoolFactory: (Function), cognitoUserPoolASFFactory: (Function), cognitoUserPoolAnalyticsHandlerFactory: (Function)), hostedUIEnvironment: nil)), authorizationEnvironment: Optional(AWSCognitoAuthPlugin.BasicAuthorizationEnvironment(identityPoolConfiguration: ["region": "<REDACTED>", "poolId": "xxx"], cognitoIdentityFactory: (Function), eventIDFactory: (Function))), credentialsClient: AWSCognitoAuthPlugin.CredentialStoreOperationClient, logger: Amplify.OSLogWrapper)
2023-01-03 20:27:46.280342-0800 AmplifyAuthSample[38816:428902] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IntializeSignInFlow.swift Sending event SignInEvent.initiateCustomSignInWithSRP
2023-01-03 20:27:46.281047-0800 AmplifyAuthSample[38816:428902] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/StartSRPFlow.swift Start execution
2023-01-03 20:27:46.281132-0800 AmplifyAuthSample[38816:428907] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configured" =     {
        "AuthenticationState.signingIn" =         {
            "SignInState.signingInWithSRPCustom" =             {
                SRPSignInStaet =                 {
                    "SRPSignInState.notStarted" =                     {
                    };
                };
            };
        };
        "AuthorizationState.signingIn" =         {
        };
    };
}
2023-01-03 20:27:46.281153-0800 AmplifyAuthSample[38816:428902] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/StartSRPFlow.swift Sending event SignInEvent.initiateSignInWithSRP
2023-01-03 20:27:46.281399-0800 AmplifyAuthSample[38816:428902] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitiateAuthSRP.swift Starting execution
2023-01-03 20:27:46.282432-0800 AmplifyAuthSample[38816:428907] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configured" =     {
        "AuthenticationState.signingIn" =         {
            "SignInState.signingInWithSRPCustom" =             {
                SRPSignInStaet =                 {
                    "SRPSignInState.initiatingSRPA" =                     {
                        clientMetadata =                         {
                        };
                        password = "<REDACTED>";
                        signInMethod = "AWSCognitoAuthPlugin.SignInMethod.apiBased(AWSCognitoAuthPlugin.AuthFlowType.customWithSRP)";
                        username =<EMAIL_ADDRESS>                    };
                };
            };
        };
        "AuthorizationState.signingIn" =         {
        };
    };
}
2023-01-03 20:27:46.286757-0800 AmplifyAuthSample[38816:428902] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Starting execution
2023-01-03 20:27:46.286767-0800 AmplifyAuthSample[38816:428907] [AWSCognitoAuthPlugin] Credential Store state change:

loadingStoredCredentials
2023-01-03 20:27:46.286866-0800 AmplifyAuthSample[38816:428902] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Retreiving credential deviceMetadata(username<EMAIL_ADDRESS>2023-01-03 20:27:46.288962-0800 AmplifyAuthSample[38816:428902] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Sending event CredentialStoreEvent.throwError
2023-01-03 20:27:46.289038-0800 AmplifyAuthSample[38816:428907] [AWSCognitoAuthPlugin] Credential Store state change:

error(KeychainStoreError: Unable to find the keychain item
Recovery suggestion: This should not happen. There is a possibility that there is a bug if this error persists. Please take a look at https://github.com/aws-amplify/amplify-ios/issues to see if there are any existing issues that match your scenario, and file an issue with the details of the bug if there isn't. Issue encountered at:
file: /Users/royji/work/iOS/amplify-swift/AmplifyPlugins/Core/AWSPluginsCore/Keychain/KeychainStoreError.swift
function: recoverySuggestion
line: 69)
2023-01-03 20:27:46.289038-0800 AmplifyAuthSample[38816:428902] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Starting execution
2023-01-03 20:27:46.289070-0800 AmplifyAuthSample[38816:428902] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Sending event CredentialStoreEvent.moveToIdleState
2023-01-03 20:27:46.289147-0800 AmplifyAuthSample[38816:428907] [AWSCognitoAuthPlugin] Credential Store state change:

idle
2023-01-03 20:27:46.289212-0800 AmplifyAuthSample[38816:428907] [AWSCognitoAuthPlugin] Credential Store state change:

loadingStoredCredentials
2023-01-03 20:27:46.289171-0800 AmplifyAuthSample[38816:428902] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Starting execution
2023-01-03 20:27:46.289258-0800 AmplifyAuthSample[38816:428902] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Retreiving credential asfDeviceId(username<EMAIL_ADDRESS>2023-01-03 20:27:46.291179-0800 AmplifyAuthSample[38816:428902] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Sending event CredentialStoreEvent.completedOperation
2023-01-03 20:27:46.291248-0800 AmplifyAuthSample[38816:428902] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Starting execution
2023-01-03 20:27:46.291300-0800 AmplifyAuthSample[38816:428902] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Sending event CredentialStoreEvent.moveToIdleState
2023-01-03 20:27:46.291857-0800 AmplifyAuthSample[38816:428907] [AWSCognitoAuthPlugin] Credential Store state change:

success(AWSCognitoAuthPlugin.CredentialStoreData.asfDeviceId("1F0AE0A5-1DD8-4CA4-8464-C40C90F3BF45", "xxx@xx.com"))
2023-01-03 20:27:46.291897-0800 AmplifyAuthSample[38816:428907] [AWSCognitoAuthPlugin] Credential Store state change:

idle
2023-01-03 20:27:46.296803-0800 AmplifyAuthSample[38816:428902] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitiateAuthSRP.swift Starting execution
2023-01-03T20:27:46-0800 info CognitoIdentityProviderClient : [Logging] Request: POST https:443
 Path: /
 Content-Length: 6749,
Host: cognito-idp.us-east-1.amazonaws.com,
Content-Type: application/x-amz-json-1.1,
X-Amz-Target: AWSCognitoIdentityProviderService.InitiateAuth,
User-Agent: aws-sdk-swift/1.0 api/cognito-identity-provider/1.0 os/iOS/16.2.0 lang/swift/5.7 lib/amplify-ios/2.2.1,
x-amz-user-agent: aws-sdk-swift/1.0
 Optional([])
2023-01-03T20:27:46-0800 info SerialExecutor : [Logging] Creating connection pool for Optional("https://cognito-idp.us-east-1.amazonaws.com/?")with max connections: 50
2023-01-03T20:27:46-0800 info CRTClientEngine : [Logging] Connection was acquired to: Optional("https://cognito-idp.us-east-1.amazonaws.com/?")
2023-01-03T20:27:47-0800 info CRTClientEngine : [Logging] headers were received
2023-01-03T20:27:47-0800 info CRTClientEngine : [Logging] headers were received
2023-01-03T20:27:47-0800 info CRTClientEngine : [Logging] headers were received
2023-01-03T20:27:47-0800 info CRTClientEngine : [Logging] headers were received
2023-01-03T20:27:47-0800 info CRTClientEngine : [Logging] headers were received
2023-01-03T20:27:47-0800 info CRTClientEngine : [Logging] header block is done
2023-01-03T20:27:47-0800 info CRTClientEngine : [Logging] incoming data
2023-01-03T20:27:47-0800 info CRTClientEngine : [Logging] stream completed
2023-01-03 20:27:47.873586-0800 AmplifyAuthSample[38816:428902] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitiateAuthSRP.swift InitiateAuth response success
2023-01-03 20:27:47.875040-0800 AmplifyAuthSample[38816:428902] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitiateAuthSRP.swift Sending event SignInEvent(data: nil, id: "D6B16423-131D-4A15-9E5C-083C59A36CE0", eventType: AWSCognitoAuthPlugin.SignInEvent.EventType.receivedChallenge(AWSCognitoAuthPlugin.RespondToAuthChallenge(challenge: AWSCognitoIdentityProvider.CognitoIdentityProviderClientTypes.ChallengeNameType.customChallenge, username<EMAIL_ADDRESS>session: Optional("xxxx"), parameters: Optional(["USERNAME"<EMAIL_ADDRESS>"trigger": "true"]))), time: nil)
2023-01-03T20:27:47-0800 info SerialExecutor : [Logging] Connection to endpoint: Optional("https://cognito-idp.us-east-1.amazonaws.com/?") is closing
2023-01-03 20:27:47.875433-0800 AmplifyAuthSample[38816:428902] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitializeResolveChallenge.swift Starting execution
2023-01-03 20:27:47.875476-0800 AmplifyAuthSample[38816:428902] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitializeResolveChallenge.swift Sending event SignInChallengeEvent.waitForAnswer
2023-01-03 20:27:47.875814-0800 AmplifyAuthSample[38816:428907] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configured" =     {
        "AuthenticationState.signingIn" =         {
            "SignInState.resolvingChallenge" =             {
                "SignInChallengeState.notStarted" =                 {
                };
                challengeType = "AWSCognitoAuthPlugin.AuthChallengeType.customChallenge";
                signInMethod = "AWSCognitoAuthPlugin.SignInMethod.apiBased(AWSCognitoAuthPlugin.AuthFlowType.customWithSRP)";
            };
        };
        "AuthorizationState.signingIn" =         {
        };
    };
}
2023-01-03 20:27:47.876035-0800 AmplifyAuthSample[38816:428907] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configured" =     {
        "AuthenticationState.signingIn" =         {
            "SignInState.resolvingChallenge" =             {
                "SignInChallengeState.waitingForAnswer" =                 {
                    challenge = "AWSCognitoIdentityProvider.CognitoIdentityProviderClientTypes.ChallengeNameType.customChallenge";
                    username =<EMAIL_ADDRESS>                };
                challengeType = "AWSCognitoAuthPlugin.AuthChallengeType.customChallenge";
                signInMethod = "AWSCognitoAuthPlugin.SignInMethod.apiBased(AWSCognitoAuthPlugin.AuthFlowType.customWithSRP)";
            };
        };
        "AuthorizationState.signingIn" =         {
        };
    };
}
VC signIn: Result = AuthSignInResult(nextStep: Amplify.AuthSignInStep.confirmSignInWithCustomChallenge(Optional(["USERNAME"<EMAIL_ADDRESS>"trigger": "true"])))
2023-01-03 20:27:50.848391-0800 AmplifyAuthSample[38816:428906] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/VerifySignInChallenge.swift Starting execution
2023-01-03 20:27:50.850362-0800 AmplifyAuthSample[38816:428907] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configured" =     {
        "AuthenticationState.signingIn" =         {
            "SignInState.resolvingChallenge" =             {
                "SignInChallengeState.verifying" =                 {
                    challenge = "AWSCognitoIdentityProvider.CognitoIdentityProviderClientTypes.ChallengeNameType.customChallenge";
                    username =<EMAIL_ADDRESS>                };
                challengeType = "AWSCognitoAuthPlugin.AuthChallengeType.customChallenge";
                signInMethod = "AWSCognitoAuthPlugin.SignInMethod.apiBased(AWSCognitoAuthPlugin.AuthFlowType.customWithSRP)";
            };
        };
        "AuthorizationState.signingIn" =         {
        };
    };
}
2023-01-03T20:27:50-0800 info CognitoIdentityProviderClient : [Logging] Request: POST https:443
 Path: /
 User-Agent: aws-sdk-swift/1.0 api/cognito-identity-provider/1.0 os/iOS/16.2.0 lang/swift/5.7 lib/amplify-ios/2.2.1,
Host: cognito-idp.us-east-1.amazonaws.com,
Content-Length: 1099,
x-amz-user-agent: aws-sdk-swift/1.0,
X-Amz-Target: AWSCognitoIdentityProviderService.RespondToAuthChallenge,
Content-Type: application/x-amz-json-1.1
 Optional([])
2023-01-03T20:27:50-0800 info SerialExecutor : [Logging] Creating connection pool for Optional("https://cognito-idp.us-east-1.amazonaws.com/?")with max connections: 50
2023-01-03T20:27:51-0800 info CRTClientEngine : [Logging] Connection was acquired to: Optional("https://cognito-idp.us-east-1.amazonaws.com/?")
2023-01-03T20:27:51-0800 info CRTClientEngine : [Logging] headers were received
2023-01-03T20:27:51-0800 info CRTClientEngine : [Logging] headers were received
2023-01-03T20:27:51-0800 info CRTClientEngine : [Logging] headers were received
2023-01-03T20:27:51-0800 info CRTClientEngine : [Logging] headers were received
2023-01-03T20:27:51-0800 info CRTClientEngine : [Logging] headers were received
2023-01-03T20:27:51-0800 info CRTClientEngine : [Logging] headers were received
2023-01-03T20:27:51-0800 info CRTClientEngine : [Logging] headers were received
2023-01-03T20:27:51-0800 info CRTClientEngine : [Logging] header block is done
2023-01-03T20:27:51-0800 info CRTClientEngine : [Logging] incoming data
2023-01-03T20:27:51-0800 info CRTClientEngine : [Logging] stream completed
2023-01-03 20:27:51.945814-0800 AmplifyAuthSample[38816:428906] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/VerifySignInChallenge.swift Sending event SignInEvent(data: nil, id: "6CB37A40-3846-4A21-9E5D-F3D6C9D9936D", eventType: AWSCognitoAuthPlugin.SignInEvent.EventType.throwAuthError(AWSCognitoAuthPlugin.SignInError.service(error: ClientRuntime.SdkError<AWSCognitoIdentityProvider.RespondToAuthChallengeOutputError>.client(ClientRuntime.ClientError.retryError(ClientRuntime.SdkError<AWSCognitoIdentityProvider.RespondToAuthChallengeOutputError>.service(AWSCognitoIdentityProvider.RespondToAuthChallengeOutputError.notAuthorizedException(AWSCognitoIdentityProvider.NotAuthorizedException(_headers: Optional(x-amzn-RequestId: xxxx,
Content-Length: 79,
x-amzn-ErrorType: NotAuthorizedException:,
x-amzn-ErrorMessage: Incorrect username or password.,
Date: Wed, 04 Jan 2023 04:27:51 GMT,
Connection: keep-alive,
Content-Type: application/x-amz-json-1.1), _statusCode: Optional(http_status_400), _message: Optional("Incorrect username or password."), _requestID: Optional("xxxx"), _retryable: false, _isThrottling: false, _type: ClientRuntime.ErrorType.client, message: Optional("Incorrect username or password."))),
Status Code: http_status_400
 x-amzn-RequestId: xxxx,
Content-Length: 79,
x-amzn-ErrorType: NotAuthorizedException:,
x-amzn-ErrorMessage: Incorrect username or password.,
Date: Wed, 04 Jan 2023 04:27:51 GMT,
Connection: keep-alive,
Content-Type: application/x-amz-json-1.1)), nil))), time: nil)
2023-01-03T20:27:51-0800 info SerialExecutor : [Logging] Connection to endpoint: Optional("https://cognito-idp.us-east-1.amazonaws.com/?") is closing
2023-01-03 20:27:51.947376-0800 AmplifyAuthSample[38816:428907] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configured" =     {
        "AuthenticationState.signingIn" =         {
            "SignInState.resolvingChallenge" =             {
                "SignInChallengeState.error" =                 {
                    challenge = "AWSCognitoIdentityProvider.CognitoIdentityProviderClientTypes.ChallengeNameType.customChallenge";
                    error = "AWSCognitoAuthPlugin.SignInError.service(error: ClientRuntime.SdkError<AWSCognitoIdentityProvider.RespondToAuthChallengeOutputError>.client(ClientRuntime.ClientError.retryError(ClientRuntime.SdkError<AWSCognitoIdentityProvider.RespondToAuthChallengeOutputError>.service(AWSCognitoIdentityProvider.RespondToAuthChallengeOutputError.notAuthorizedException(AWSCognitoIdentityProvider.NotAuthorizedException(_headers: Optional(Date: Wed, 04 Jan 2023 04:27:51 GMT, \nContent-Length: 79, \nx-amzn-RequestId: xxxx, \nContent-Type: application/x-amz-json-1.1, \nx-amzn-ErrorMessage: Incorrect username or password., \nConnection: keep-alive, \nx-amzn-ErrorType: NotAuthorizedException:), _statusCode: Optional(http_status_400), _message: Optional(\"Incorrect username or password.\"), _requestID: Optional(\"xxxx\"), _retryable: false, _isThrottling: false, _type: ClientRuntime.ErrorType.client, message: Optional(\"Incorrect username or password.\"))), \nStatus Code: http_status_400 \n Content-Type: application/x-amz-json-1.1, \nx-amzn-ErrorMessage: Incorrect username or password., \nContent-Length: 79, \nDate: Wed, 04 Jan 2023 04:27:51 GMT, \nConnection: keep-alive, \nx-amzn-RequestId: xxxx, \nx-amzn-ErrorType: NotAuthorizedException:)), nil))";
                    username =<EMAIL_ADDRESS>                };
                challengeType = "AWSCognitoAuthPlugin.AuthChallengeType.customChallenge";
                signInMethod = "AWSCognitoAuthPlugin.SignInMethod.apiBased(AWSCognitoAuthPlugin.AuthFlowType.customWithSRP)";
            };
        };
        "AuthorizationState.signingIn" =         {
        };
    };
}
VC confirmSignIn: Error = AuthError: Incorrect username or password.
Recovery suggestion: Check whether the given values are correct and the user is authorized to perform the operation.

Hey Jithin, I wasn't able to get any more logs for this flow, but I am still facing this issue. I saw that the PR you made above has been stalled due to some unintended consequences of the changes. Do you have any updates on this?

In a last ditch effort to fix this issue, I removed amplify entirely from my project locally and remotely and recreated every resource from scratch. Even still, the issue persists. I am losing hope.

Thanks, for reaching back. I will give an update today here.

Created another PR to address this issue - https://github.com/aws-amplify/amplify-swift/pull/2687
We are currently reviewing PR and testing the changes. Feel free to try out the changes by pointing to the branch royjit.fixfetchAuthSession2 and let us know if this fixes your issue.

In my experience setting CUSTOM_AUTH in the config is not sufficient, even if the docs say otherwise (they often incorrectly refer to SDK v1 APIs). Adding auth options to the signIn call works though:
let result = try await Amplify.Auth.signIn(username: username, options: AuthSignInRequest.Options(pluginOptions: AWSAuthSignInOptions(authFlowType: .customWithoutSRP)))

Hey Harold - yes I have that exact line in my sign in function. I have been following this documentation almost to the tee (except for changing out the random number generation logic in the lambda).

Created another PR to address this issue - #2687
We are currently reviewing PR and testing the changes. Feel free to try out the changes by pointing to the branch royjit.fixfetchAuthSession2 and let us know if this fixes your issue.

I pulled in this branch and I am still facing the same issue. Just to reiterate, the app starts to hang when the confirm sign in call is made.

I am unable to figure out the root cause of this and also not able to reproduce it I followed the same doc. For custom auth I just used a hard coded value. Would you like to setup a call to debug this? You can reach us via discord or contact via email (royji at amazon.com).

Just to circle back here - by pulling in the main branch of the amplify sdk I was able to resolve this issue. Thank you Jithin for deep diving this issue with me and your support throughout this ticket.

Thank you for the update, the changes will be available in the next release.

Need this in the visionos-preview branch. Facing the same error.


ERROR in The node API for babel has been moved to babel-core.

I am sorry,I am newer to nodejs,
zhuwt@ubuntu:~/rtsphtml/node_modules/html5_rtsp_player/examples$ webpack --config webpack.config.js
Hash: c848527f64a5353b8e14
Version: webpack 1.13.2
Time: 87ms
+ 1 hidden modules
ERROR in The node API for babel has been moved to babel-core.
what should I do?

These two lines solve the problem, but there is another...
sudo npm uninstall babel --save-dev
sudo npm install babel-loader babel-core --save-dev
webpack --config webpack.config.js
Hash: c848527f64a5353b8e14
Version: webpack 1.13.3
Time: 217ms
+ 1 hidden modules
ERROR in ./test.js
Module build failed: Error: Couldn't find preset "es2015" relative to directory "./tmp/node_modules/html5_rtsp_player"

Linked with issue #5
I've made npm install bp_event bp_logger bp_statemachine in html5_rtsp_player and in example
And I still have problem with es2015
Can you update readme with step by step instructions how to run example on new ubuntu installation (you can use vm e.g. from osboxes.org)?

Version you are using is obsolete now. You can try new version of player with rollup bundler and simply add buble plugin to it's config. Note that new player version requires new proxy that can be downloaded from http://streamedian.com/

in your webpack.config.js file make the loader be loader:babel-loader and it would work. no need to uninstall
module:{
    loaders:[
        {
            test: /\.jsx?$/,
            loader: 'babel-loader',
            exclude: /node_modules/
        }
    ]
}


Dwalton/feat/more terraform

Included Changes

update vpc tagging
add ecr resource
add security group definitions
add eks control plane

Not that is should matter, but I approve of these changes.


Implement more EdDSA primitives

Tor is implementing various additions to Ed25519 ref10 to support extended use cases. Similar extensions here would benefit I2P, as well as Java implementations of Tor.
To add:

Key blinding
Conversion of Curve 25519 keys to Ed25519

See Tor ticket 12980 and links therein.

In I2P we decided to use RedDSA instead of EdDSA for key blinding purposes, as RedDSA is explicitly designed with re-randomisation in mind (whereas Ed25519 is not, and the key blinding protocol for it is an ad-hoc construction). So I'm not going to implement the above in this library.


create script to install sublime

Currently the process is described for completely manual execution in the project's README, an area needs to be created where the tool installation scripts will be kept

d77e98fba1760330dc4d08d31e112282a040500e


[WiP] dryRun execution supports schema compatibility checks

An initial first code example to improve the the --dryRun functionality. (with a bit of polishing) It solves
https://github.com/kafka-ops/julie/issues/223
Any suggestions on the code? We can keep this PR open to gradually come to a good production ready solution.

Nel mezzo del cammin di nostra vita
mi ritrovai per una selva oscura,
ché la diritta via era smarrita.

Hope all is well. If you find time to read - or even comment on - my answers that would be greatly appreciated!
If we come to some naming agreement the technical implementation should be easy.

Anyone? If there is no interest in this feature/issue then we might as well close this PR.

Closing this PR due to lack of response.

Back in business!

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.


Implement docker hub

WHY
To support Docker Hub as well as Quay.
WHAT
Implementation to handle Docker Hub API V2 and modification of README.

Just updated for private repos on Docker Hub 😄

LGTM 👍


support LLaMA-Omni

this is github link    https://github.com/ictnlp/LLaMA-Omni

https://github.com/ollama/ollama/issues/6786

Going to close this as a dupe.


Remind days & remind launches not working

Hi,
I was able to pop up the rating dialog at the first day and I pressed later button. When come to the next day it doesn't pop up anymore. Want to know why it doesn't came out after the first day. Below are my setup for RateMyApp.
Init setup :
RateMyApp rateMyApp = RateMyApp(
minDays: 0,
minLaunches: 1,
remindDays: 1,
remindLaunches: 1,
);

Later button onTap :
onTap: () async {
    await rateMyApp.callEvent(RateMyAppEventType.laterButtonPressed);
    Navigator.pop<RateMyAppDialogButton>(context, RateMyAppDialogButton.later);
},

Thanks.

Is this a duplicate of #70 ?

Is this a duplicate of #70 ?

I guess it is because it return true only on the first day.
minDays: 0
minLaunches: 1
After the next day it should return true as well because of  remind but it doesn't return true.
remindDays: 1
remindLaunches: 1
Any idea how to solve this issue ?

If it's a duplicate, I'll close this issue. Let's keep the conversation in #70. Also you may be interested by the message I've just posted.


ddev-webserver: All startup should be managed by supervisord if we're going to use supervisord

From @rfay on March 22, 2018 5:16
What happened (or feature request):
Studying bugs in https://github.com/drud/docker.nginx-php-fpm-local/pull/60 I noted that:
Our current startup for this image is a start.sh that does a bunch of things followed by running supervisord. Before #60 it was just running supervisord, but it needs to exec it so that supervisord receives signals sent to the container (so that changes in #60).
But the reality is... since we have to do all this prework, we should be doing it in a script managed by supervisord, and supervisord should be the CMD for the Dockerfile, not an afterthought.
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else do we need to know:
Related source links or issues:
Copied from original issue: drud/docker.nginx-php-fpm-local#62

We use 3 different supervisord configs now, and it has been quite reorganized. Closing.


[KYUUBI #3295] [FEATURE] Filter other engine configs when build engine process builder

Why are the changes needed?

close https://github.com/apache/incubator-kyuubi/issues/3295#issue-1345447015

How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

Codecov Report

Merging #3296 (0ee8b48) into master (327336f) will decrease coverage by 0.01%.
The diff coverage is 56.25%.

@@             Coverage Diff              @@
##             master    #3296      +/-   ##
============================================
- Coverage     51.38%   51.37%   -0.02%
  Complexity       13       13
============================================
  Files           468      469       +1
  Lines         26220    26237      +17
  Branches       3632     3631       -1
============================================
+ Hits          13473    13479       +6
- Misses        11465    11470       +5
- Partials       1282     1288       +6

Impacted Files
Coverage Δ

...ache/kyuubi/engine/flink/FlinkProcessBuilder.scala
88.52% <0.00%> (ø)

...apache/kyuubi/engine/hive/HiveProcessBuilder.scala
72.88% <0.00%> (ø)

...apache/kyuubi/engine/jdbc/JdbcProcessBuilder.scala
89.79% <0.00%> (ø)

...ache/kyuubi/engine/trino/TrinoProcessBuilder.scala
93.75% <0.00%> (ø)

...n/scala/org/apache/kyuubi/engine/ProcBuilder.scala
82.73% <71.42%> (-0.50%)
:arrow_down:

...kyuubi/engine/spark/SparkBatchProcessBuilder.scala
96.96% <75.00%> (+0.09%)
:arrow_up:

...ache/kyuubi/engine/spark/SparkProcessBuilder.scala
87.50% <100.00%> (ø)

...uthentication/JdbcAuthenticationProviderImpl.scala
73.21% <0.00%> (-6.54%)
:arrow_down:

...apache/kyuubi/engine/JpsApplicationOperation.scala
77.41% <0.00%> (-3.23%)
:arrow_down:

...rg/apache/kyuubi/ctl/cmd/log/LogBatchCommand.scala
78.00% <0.00%> (-2.00%)
:arrow_down:

... and 5 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

This constraint should be added at KyuubiConf.getCurrentEngineConfigs for the default Kyuubi session config.
We can not remove the config which is added by user.


docs: Add tls configuration docs

Surface some internal TLS configuration documentation externally.

Most original authors (from what I could tell) are listed as co-authors in the commit. Also, I think it should be fine to leave some of the OpenShift specific instructions since we do have some OpenShift users. However, we should also create instructions for using a Kubernetes Ingress resource with ModelMesh (as opposed to an OpenShift Route).


Add import pandas as pd to code snippets

see above

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 2f45a6b5-0fea-7fbb-5d4d-37e0e2583fd7
Version Independent ID: 7be6f792-09f8-c22f-86b6-d0f690e9b3a4
Content: Explore data in Azure blob storage with pandas - Team Data Science Process
Content Source: articles/machine-learning/team-data-science-process/explore-data-blob.md
Service: machine-learning
Sub-service: team-data-science-process
GitHub Login: @marktab
Microsoft Alias: tdsp

@jordaniza we will review your feedback and get back to you shortly. Thanks.

@GiftA-MSFT comment is correct, missing that simple line -- I don't know how to connect an edit to this issue

@GiftA-MSFT  I finished a pull request, we may close this ticket

Thank you @marktab.


Implement index removal tooling

Our hosted databases contain a lot of generated indexes, most of which are unused.  These occupy a significant amount of storage, pose overhead on all DML operations (resulting in CPU usage without much worth), and makes things a bit messy overall.
If we could get rid of them, we could move the DBs to instances with smaller storage, thus saving some money, and also relieve the instances from some of the load, which every now and then causes live issues.
In case of DBs with (read) replicas, one has to consider index usage on the replicas as well.  Here we can leverage the already defined foreign servers.
The workflow looks like:

set up the necessary tables, functions, and procedures
collect index usage statistics from pg_stat_user_indexes
remove attribute indexes from deployments that are older than 2 months (we can assume these won't be needed if they haven't seen usage in so many months)
store the definition of the removed indexes in a separate table, as a safety net

After some adjustments of the logic, I started removing indexes from fraction-7727, where there were originally 33k+ indexes eligible for removal.  Will leave it running for a while to assess impact on resource consumption, then turn to removal in prod once the results seem satisfying.

Some more testing and actual usage on production results in more changes (some differences in function definition on Postgres 13 vs 14, more importantly a couple of performance improvements, and using host-specific scripts without pg_service.conf).

Done, closing.


Should ParVec have poisoning behavior for panics?

A thread panicking while operating on a ParSlice could leave an incomplete result, similar to what would happen if a thread panicked while holding a MutexGuard or a RWLockWriteGuard. This suggests that ParSlice should have similar poisoning behavior.
However, poisoning a whole vector just because a thread panicked while holding a subslice seems like overkill. As a compromise, unwrapping a ParVec could return two vectors: one with all the elements from healthy (unpoisoned) subslices, and one with the contaminated elements from poisoned subslices. This would add complexity to the implementation as subslices are currently only tracked via the strong refcount on Arc, and would also require additional allocations where the current API uses existing storage.
But I would also argue that ParVec should not poison altogether, because it does not allow actual concurrent (or mutually exclusive) access to its elements; each is only ever touched by either the originating thread, or the thread that its containing ParSlice was sent to, and never at the same time, mutably or otherwise. In this way, incomplete results seem more like a logic error than undefined behavior, and thus should be handled by the user.
It is clear some discussion is merited here. Is ParVec safe as it is, or is it hiding dangerous, undefined behavior behind a "safe" API?
cc @Gankro, @huonw

It seems reasonable to me to just poison the entire vector, and allow the user to recover from poisoning the same way Mutex and RwLock do.

It should be noted that poisoning is not actually necessary for safety reasons, it's just a nice-to-have as it makes the behavior under panics a bit more reasonable.