No longer set the biometrics user default if the user can't use biometrics. Reason for doing this is because it can cause confusion. If the user doesn't have biometrics set up on their device, opens Pilot, then goes and sets up biometrics on their device, then uses Pilot again, they may never know that they have the option to log in with biometrics. We want to present the option the first time they are able to use biometrics, so we should not set the UserDefault until they are presented the option.
Fix (possible) bug with UserDefaults extension. Possible bug: if you call contains(key:) on an instance of UserDefaults that is not UserDefaults.standard, it would only look for if the key is contained in UserDefaults.standard. Now it will look on the object you call it on.
Quick PR to fix #68.
Info.plistbiometricsuser default if the user can't use biometrics. Reason for doing this is because it can cause confusion. If the user doesn't have biometrics set up on their device, opens Pilot, then goes and sets up biometrics on their device, then uses Pilot again, they may never know that they have the option to log in with biometrics. We want to present the option the first time they are able to use biometrics, so we should not set the UserDefault until they are presented the option.UserDefaultsextension. Possible bug: if you callcontains(key:)on an instance ofUserDefaultsthat is notUserDefaults.standard, it would only look for if the key is contained inUserDefaults.standard. Now it will look on the object you call it on.