First of all, thank you for this awesome package! This is a feature request.

In case when I`m setting pin code first time and miss clicked then I can not enter the same code one more time. It is not a problem if I trying to change old pin code. But if setting of pin code is mandatory on first run, I should unload app to make a new try. It is not clear for many users. So, I need to write much code to make it work my way. I guess, not only mine.

Thank you!

If user on confirmation screen and he presss back button then how to navigate to previous screen means first password screen. Suppose a user on the first screen where he enter a password after that he navigates to confirm password screen so how user go back from confirm password screen to set password screen. please help

checkPassword() async{
    SharedPreferences _preferences = await SharedPreferences.getInstance();
    _password = _preferences.getString(_key);
    _isFingerprintEnabled = _preferences.getBool(_fingerprintKey);
    showLockScreen(
      context: context,
      title: "Enter vault password",
      digits: 5,
      correctString: _password,
      cancelText: "Close",
      showBiometricFirst: true,
      canCancel: false,
      onUnlocked: () => Navigator.pushReplacement(context, MaterialPageRoute(builder: (_) => Home())),
      canBiometric: _isFingerprintEnabled,
      biometricAuthenticate: (context) async {
        final localAuth = LocalAuthentication();
        final didAuthenticate = await localAuth.authenticateWithBiometrics(
            localizedReason: 'Please authenticate');

        if (didAuthenticate) {
          return true;
        }

        return false;
      },
    );
  }

This is my code but fingerprint not working means after clicking on Fingerprint icon nothing is happening.

• Fixed ScreenLockConfig Title styling from ThemeData
• Added KeyPadButtonConfig for Actions and assigned reasonable default
• Renamed config parameters
• Corrected some documentation typos
• Fix #91

The way I changed ScreenLockConfig in the last update showed that there is an issue with this:

ScreenLockConfig(
  theme: ThemeData.of(context),
)

The user would get a very large title because it was using headline1. I changed it to headline6 (appbar size) which is more reasonable. The above usage is intended, so it is expected to have a sane standard.

I also changed the hardcoded font size for the cancel button, which is now configurable in the KeyPadConfig as actionButtonConfig. This also influences the delete and fingerprint button.

I also renamed the screenLockConfig parameter to just config, as it is clear what we are configuring.

Currently, we are using HeadingText to apply the right style to our Text when they are displayed above the Secrets. This also means we have to export HeadingText for users to specify their own Text with the same style. That is inconvenient.

Instead we can do what AppBar does for its title property. We let the user provide a normal Text and then wrap it in a DefaultTextTheme which applies our text style. If the user wants to opt out of that, they just have to provide a text style to their Text widget.

I will make a merge request for this, once other things are merged, so that there will be no conflicts.

When I type quickly on the password input panel, it can not response timely. For example, I typed four number quickly, but only two were inputed, there were two types not being corresponded. And when user inputs a familiar password, it's common to input quickly. I suspect that Flutter set a least interval between gesture actions, but I can't find related doc or code. Do you have any idea about that?

I want some extra features, like many app which uses lock screen contains options like lock app after 30 sec or 1 min when user doesn't interact with and after screen lock after particular time lock the app, so can we add this features in our package?

First of all, thank you for this awesome library. But i want to know that can i change the alignment of this screen? like when we show this screen it starts from top of the screen so on the end much more space remaining empty. So, my question is that how to start the screen from bottom of my application so if any space remain it remains at top not at bottom.

It's a very popular scenario when max retries is exceeded and user should be waiting, for example: 5min, before next retry. didMaxRetries is quite complex to handle that scenario. it's will be great if you can support that scenario out of the box, I appreciate that.

fix #75

merge request #76 but without a breaking oversight.

cannot be merged into fix/delay-screen because of conflicts by the revert.

(sorry, I forgot a tiny change on a line and it caused the issue!)

Hi I'm observing the following issue with Android. As far as I remember there were no issue before. This seems related to a bug you fixed recently. I observe this on Android emulators 8.1 and 11.

I tried your versions 5.0.9 and 5.0.10, both have same issues. This happens when the Lock Screen is dismissed after the code was entered.

Any idea about this ? Thanks

E/flutter ( 6937): [ERROR:flutter/lib/ui/ui_dart_state.cc(209)] Unhandled Exception: A ValueNotifier<String> was used after being disposed.
E/flutter ( 6937): Once you have called dispose() on a ValueNotifier<String>, it can no longer be used.
E/flutter ( 6937): #0      ChangeNotifier._debugAssertNotDisposed.<anonymous closure> (package:flutter/src/foundation/change_notifier.dart:114:9)
E/flutter ( 6937): #1      ChangeNotifier._debugAssertNotDisposed (package:flutter/src/foundation/change_notifier.dart:120:6)
E/flutter ( 6937): #2      ChangeNotifier.notifyListeners (package:flutter/src/foundation/change_notifier.dart:288:12)
E/flutter ( 6937): #3      ValueNotifier.value= (package:flutter/src/foundation/change_notifier.dart:412:5)
E/flutter ( 6937): #4      InputController.dispose (package:flutter_screen_lock/src/input_controller.dart:119:25)
E/flutter ( 6937): #5      _ScreenLockState.dispose.<anonymous closure> (package:flutter_screen_lock/src/screen_lock.dart:240:29)
E/flutter ( 6937): #6      new Future.microtask.<anonymous closure> (dart:async/future.dart:276:37)
E/flutter ( 6937): #7      _rootRun (dart:async/zone.dart:1418:47)
E/flutter ( 6937): #8      _CustomZone.run (dart:async/zone.dart:1328:19)
E/flutter ( 6937): #9      _CustomZone.runGuarded (dart:async/zone.dart:1236:7)
E/flutter ( 6937): #10     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:1276:23)
E/flutter ( 6937): #11     _rootRun (dart:async/zone.dart:1426:13)
E/flutter ( 6937): #12     _CustomZone.run (dart:async/zone.dart:1328:19)
E/flutter ( 6937): #13     _CustomZone.runGuarded (dart:async/zone.dart:1236:7)
E/flutter ( 6937): #14     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:1276:23)
E/flutter ( 6937): #15     _microtaskLoop (dart:async/schedule_microtask.dart:40:21)
E/flutter ( 6937): #16     _startMicrotaskLoop (dart:async/schedule_microtask.dart:49:5)

I am using your package well. Thank you.

In confirmation:true I want to be able to customize the keyPadConfig of the confirmation screen. I would like to have different keypads for the two screens of confirmation:true.

Thank you.

It would be great if the package supported input via a physical keyboard.

I have already tested a rough implementation of this:

final FocusNode _focusNode = FocusNode();

bool _canInput = true;

void _blockInput() {
  _canInput = false;
  Timer(const Duration(milliseconds: 100), () => _canInput = true);
}

@override
void initState() {
  super.initState();
  _focusNode.requestFocus();
}

@override
void didChangeDependencies() {
  super.didChangeDependencies();
  FocusScope.of(context).autofocus(_focusNode);
}

@override
void dispose() {
  _focusNode.dispose();
  super.dispose();
}

@override
Widget build(BuildContext context) {
  return KeyboardListener(
    focusNode: _focusNode,
    onKeyEvent: (key) {
      if (!_canInput) {
        return;
      }
      if (widget.inputButtonConfig.inputStrings.contains(key.character)) {
        widget.inputState.addCharacter(key.character!);
        _blockInput();
      }
      if (key.logicalKey == LogicalKeyboardKey.backspace) {
        widget.inputState.removeCharacter();
        _blockInput();
      }
    },
    child: widget.child,
  );
}

It can be used as a widget wrapped around a keypad to enter a PIN code from the keyboard. There are some issues with delays. KeyEvent can be triggered very fast. Maybe only add delay on backspace? not sure.

I probably won't make a pull request. I don't want to change the structure of your project too much. But I think this feature is a great addition.