onSelected() Not reliably called on Android Nougat

[ahclipse]

Hello,

First off thanks for the library, it looks great! I think I have found an issue affecting only Android 7.X Nougat devices.

Scenario

• The first Fragment in my stepper has an EditText field that needs focus and to display a soft keyboard when user navigates to it.

My code to accomplish this looks like:

@Override
public void onSelected() {
    templateNameEditText.post(new Runnable() {
        @Override
        public void run() {
            templateNameEditText.requestFocus();
            InputMethodManager inputMethodManager = (InputMethodManager) getActivity().getSystemService(Context.INPUT_METHOD_SERVICE);
            inputMethodManager.showSoftInput(templateNameEditText, InputMethodManager.SHOW_IMPLICIT);
        }
    });
}

This is working wonderfully on every android device down to Android 4.4 KitKat but inconsistently on Android 7.X.

Suspected Cause

• Line 774 in onUpdate(...) of StepperLayout.java has Step step = mStepAdapter.findStep(newStepPosition); and I have seen only on Nougat devices that this method is sometimes returning null

Steps to Reproduce

• Add a Fragment that implements Step
• Add a Log statement or line of code to attach debugger in @Override public void onSelected() {}
• Verify onSelected is not called on every navigation to Fragment

Expected Result

• mStepAdapter.findStep(newStepPosition); should not be null and onSelected should be called each time user navigates to Fragment on Android Nougat devices

[zawadz88]

Hi @ahclipse,
Thanks for reporting this and the detailed description.
Could you confirm that you're using the latest library version i.e. 3.3.0?
This was fixed in 3.2.3 (issue #127) but it's possible that for some reason this does not work on Nougat: https://github.com/stepstone-tech/android-material-stepper/releases/tag/v3.2.3

[ahclipse]

Hey @zawadz88

I really appreciate the prompt response. My apologies for not doing my due diligence in checking the bug log and release versions. Turns out we were on 3.1.0 still. Strange it was only appearing for me on Nougat devices but a quick update and testing on 3.3.0 shows this is indeed fixed for 4.4-7.0. This may be closed out.

Thanks again