AuthUI ForceChangePasswordView Form Name Mismatch

[dennisunderwood]

Describe the bug
There is a mismatch between two variable names inside of the two associated files:
aws-sdk-android/aws-android-sdk-auth-userpools/src/main/java/com/amazonaws/mobile/auth/userpools/ForceChangePasswordView.java
and
aws-sdk-android/aws-android-sdk-auth-userpools/src/main/res/layout/activity_force_change_password.xml

The following mismatch is present, causing runtime crash:
activity_force_change_password.xml in line 37:
android:id="@+id/force_change_password_form"
ForceChangePasswordView.java in line 133:
forgotPassForm = (FormView) findViewById(R.id.forgot_password_form);

The second mismatch is the following:
activity_force_change_password.xml in line 50:
android:id="@+id/force_change_password_button"
ForceChangePasswordView.java in line 142:
confirmButton = (Button) findViewById(R.id.forgot_password_button);

To Reproduce
Steps to reproduce the behavior:

1. Create new user in Cognito, or set state of user to FORCE_CHANGE_PASSWORD
2. Login with temporary password, so that the AuthUI attempts to use the code path for force change password.
3. Unhandled runtime crash of the app.

Which AWS service(s) are affected?
AWS Cognito - client side, not server
AWS AuthUI

Expected behavior
User should be redirected to the page asking for a new password to be set.

Environment(please complete the following information):

• SDK Version: 2.7.6 - 8.0.3

Device Information (please complete the following information):

• Device: Samsung Galaxy S7
• Android Version: Nougat 7.1.2

Additional context
This is currently fixed via manually editing the xml files to match the UI fields requested in the Java files above.

[minbi]

Hi @dennisunderwood ,

Thanks for pointing out the issue. We are looking at it and aiming to resolve this in a future release.

[minbi]

Hi @dennisunderwood ,

We have released a fix in version 2.8.5 of the SDK. Please see if this fixes the issue for you.

[minbi]

Hi,

We are closing this issue because there has been no activity. Please feel free to open a new issue if the problem persists. We ask this because closed issues are not actively monitored.

Thanks