Hi, Seems this library is not supported on Windows. I continuosly see this error when trying to build my app on a windows machine.

Can someone please check.

Thanks Manmeet Chadha

Logs.txt

Build fails for Android on M1 Macs with the following error:

Execution failed for task ':flutter_locker:generateDebugProto'.
> Could not resolve all files for configuration ':flutter_locker:protobufToolsLocator_protoc'.
   > Could not find protoc-3.9.1-osx-aarch_64.exe (com.google.protobuf:protoc:3.9.1).
     Searched in the following locations:
         [https://jcenter.bintray.com/com/google/protobuf/protoc/3.9.1/protoc-3.9.1-osx-aarch_64.exe]()

After some googling, the issue is that there are no binaries for M1 Macs, there are however x86 compatible binaries, this github issue explains how to make protobuf select the appropriate binary, I did it locally and it worked successfully.

Can't build Android version on Flutter 3

* What went wrong:
Some problems were found with the configuration of task ':flutter_locker:extractDebugProto' (type 'ProtobufExtract').
  - In plugin 'com.google.protobuf' type 'com.google.protobuf.gradle.ProtobufExtract' property 'destDir' is missing an input or output annotation.

    Reason: A property without annotation isn't considered during up-to-date checking.

    Possible solutions:
      1. Add an input or output annotation.
      2. Mark it as @Internal.

    Please refer to https://docs.gradle.org/7.4.2/userguide/validation_problems.html#missing_annotation for more details about this problem.
  - In plugin 'com.google.protobuf' type 'com.google.protobuf.gradle.ProtobufExtract' property 'isTest' is missing an input or output annotation.

    Reason: A property without annotation isn't considered during up-to-date checking.

    Possible solutions:
      1. Add an input or output annotation.
      2. Mark it as @Internal.

    Please refer to https://docs.gradle.org/7.4.2/userguide/validation_problems.html#missing_annotation for more details about this problem.

Hi

This is another pre-9 Android error, this one is generated on closing fingerprint dialog.

Just run plugin example on any android version < 9, f.e. 8.1

E/FingerprintDialogFrag(14973): Failed to dismiss fingerprint dialog fragment. Fragment manager was null.

Getting this error:

/ios/Pods/Locker/Sources/Locker/Helpers/LockerHelpers.swift:11:8: error: failed to build module 'System'; this SDK is not supported by the compiler (the SDK is built with 'Apple Swift version 5.5.2 (swiftlang-1300.0.46.202 clang-1300.0.29.30)', while this compiler is 'Apple Swift version 5.5.2 (swiftlang-1300.0.47.5 clang-1300.0.29.30)'). Please select a toolchain which matches the SDK. import System ^ remark: Incremental compilation has been disabled: it is not compatible with whole module optimization Command CompileSwiftSources failed with a nonzero exit code note: Using new build system note: Planning note: Build preparation complete note: Building targets in dependency order

Environment flutter_locker version 2.0.3 XCode version 13.2.1 Apple Swift version 5.5.2 Flutter Channel stable, 2.8.1, on macOS 12.0.1

in my project , run

FlutterLocker.save(SaveSecretRequest("passCode", "passCodeSecret", AndroidPrompt("Authenticate", "Cancel")));

but get exception under error

Unhandled Exception: PlatformException(error, com.bibtel.MainActivity cannot be cast to androidx.fragment.app.FragmentActivity, null, java.lang.ClassCastException: com.bibtel.MainActivity cannot be cast to androidx.fragment.app.FragmentActivity

how fix it.

me noob in the flutter.

There are a lot of changes here. The example was producing errors since it was using v1 Android embedding. I recreated the example project to fix the errors (deleted the example/android and example/ios folders and re-run flutter create).

The only changes relevant to M1 support are in android/build.gradle.

I've been trying for a while to check for which exception the user gets (as in he cancelled the auth, doesn't have biometrics, etc) but I can't see anywhere if there are ways to compare which exception has been catched (such as LockerException: Authentication canceled by user. or PlatformException(3, co.infinum.goldfinger.NoEnrolledFingerprintException: User has no enrolled fingerprint., null, null). Is there an easier way to do this other than comparing strings and checking what word it has?

And on the subject of it, shouldn't a popup open to configure fingerprints if there aren't any configured in the android?

Thanks in advance

Error:

SwiftFlutterLockerPlugin.swift:61:23: error: initializer for conditional binding must have Optional type, not 'String'
                    guard let secret = secret else {

This is because after Locker was migrated to swift in v3.0, the retrieveCurrentSecret success callback is now not optional source.

Hey :) I was wondering whether you have plans to release a version of your package supporting the new null safety feature of dart.

Thanks in advance for your reply!

There is no way to import those symbols and check on the reason for a failed retrieve.

(Also documentation to FlutterLockerException when it should be LockerException)

When using Touch ID, after 3 wrong attempts the prompt is closed and a LockerException with the authenticationFailed reason is thrown. After 2 wrong attempts more, Touch ID will be locked for all apps (it may be unlocked using PIN). After that, every time I call FlutterLocker.retrieve, an exception with the authenticationFailed reason is thrown - it's ok, but now my question is how I can differentiate between those two cases. It must be possible in some way, as there are apps that are showing a dialog with a message that Touch ID is locked and cannot be used right now.

With Face ID it behaves similarly, but in the first case an exception with the authenticationCanceled reason is thrown.

There is error reported to log running app using plugin, including plugin example itself, on Android version less than 9.

Just run plugin example on any android version < 9, f.e. 8.1

Could you please have a look?

Hi, Thank you for this very useful plugin!!!

There is one feature missing, as for me, to identify the biometric type, for sure it is needed for iOS only (at this moment). Use case of this feature - to show user appropriate text in settings to enable Touch/Face ID.

Could you please try to implement such functionality?