Apps using the biometric login overlay generally dismiss the overlay if the app is switched/closed.

When switching/closing Authenticator, the biometric login overlay stays in the foreground until the user taps the dead space above the biometric login request. This makes for an awkward action when cancelling the process in comparison to what apps usually do.

Hello again, sorry I've been busy with life, hence the delay. I'll break this up starting with the minor changes down to the more subjective changes.

2 New Icons

• bugzilla@mozilla
• Ente (+ Dark Mode)

Issues #515 and #519 can be closed.

Updated README.md

• Added header image
• Updated 'Get It On' buttons to new logos and equal padding around each image
• Updated 'Buy Me A Coffee' button to also have equal padding to be the same size.
• Minor changes to the layout such as slightly changed 'Features' format to increase readability. If you want to preview it you can look at a live version on my fork

Ever so slightly changed 'colorLightBluePrimary' within the app to match updated branding

It's changed from #40C4FF to #2CB1EC. Old colour on the left, new colour on the right.

Updated app icons

I have updated the app icon and all the necessary scales within the AuthenticatorPro.Droid/Resources/mipmap folders and the AuthenticatorPro.WearOS/Resources/mipmap folders.

Rebranding Assets

And finally I have added all the updated assets I feel you might like, again these don't have to be set in stone, if there's, anything you want differently then don't hesitate to ask. For now they are within the directory doc/Rebranding/. I have also done a correctly scaled Playstore icon and Feature graphic. The idea is to have the 'showcase_image' be the first screenshot image on the Playstore followed by any order of the regular screenshots that you prefer.

One emission is WearOS. I couldn't get the emulator to play nicely and get codes added, that's why in the rebranding folder there's a couple unused assets involving WearOS. If you want to use them then just let me know and send me some high res wearOS screenshot.

Without further ado:

Describe the bug

I installed the app both to OnePlus8 phone and Suunto 7 Android wear watch. I added a token to phone, which is tested to work. But when I open the android wear app it just says "No Authenticators - Nothing here. Add some authenticators from the phone app.". So in short, app in mobile and watch do not sync.

To Reproduce Steps to reproduce the behavior:

1. installed application to phone
2. added and tested a token, it works
3. install application to Suunto 7
4. open the application, and get the above text.

Expected behavior

I'd expect the token entry be available from the watch.

App Version

Phone: 1.14.3 Suunto: 2.2.3

Additional context

I re-installed the app on the watch, made no difference. The phone and watch use bluetooth to talk to eachother.

First, let me thank you for this amazing app. It is, in my honest opinion, the best authenticator app on the google store, and should get way more attention then it currently does. I have a few small issues/requests that I would like to suggest/inquire about. I quickly browsed through all the opened and closed issues to make sure none of these have already been discussed so apologies if I missed a similar issue. Also, if you'd like me to separate these into separate issues just let me know.

1. Can you please add 2 icons:

   • Bethesda ---> https://1000logos.net/bethesda-logo/ (the square icon at the bottom)
   • Windscribe ---> https://twitter.com/windscribecom (use their profile icon)

2. Can you add a sorting button at the top right corner, across from the category name, that will open a sorting menu when clicked upon. The menu will include 3 options:

   • Issuer (A--->Z)
   • Issuer (Z--->A)
   • Custom (this will be automatically selected if the user drags and drops any of the entries)

This will allow the user to quickly revert his/her entries back to alphabetic order if they moved a lot of them around using drag and drop

3. In Settings ---> Theme, can you please add 2 more options:

   • System default (AMOLED)
   • Dark mode (AMOLED)

If those options are selected the home page, Main Menu, and "+" menu will look just like the settings page. In the home page, just replace the grey background of each entry with pure black background and separate them with thin dimmed grey lines. In the Main Menu and "+" menu, replace the grey panel with pure black panel as well.

4. Can you add an option in the setting for the authentication codes to be hidden until the user taps on the one he/she wants to reveal. Also, add an option that will allow the user to chose how long the code will stay revealed after the user tapped on it.

5. If the user already entered a password in the Security section of the Settings and then uses the "Backup to encrypted file (recommended)" option, then, in addition to having a password field presented to them where they need to enter a password, they should also be presented with an option below that field that will allow them to use the same password from the Security section of the Settings. This will save the user from typing if they want to use the same password.

6. In each entry's 3 dots menu, can you add an option that will allow the user to change the 30 sec timer before a code changes. Also, add an option to change it for all entries at once.

7. In each entry's 3 dots menu, can you add an option(s) to display the QR code and/or secret key for that entry. That would be a nice alternative to the HTML file backup (though I'm not sure how complicated this would be to implement)

8. If the user has set up the Biometric Unlock option, can you change its implementation so that every time the fingerprint prompt appears on the screen it will not have the prompt to enter a password or fingerprint appear behind it. Instead, the user should only see the fingerprint prompt. Only if the user fails to enter a valid fingerprint (or hit the back button) should the prompt to enter a password appear on the screen.

9. Finally, I encountered a small bug. Sometimes (in most cases actually), after the successful scanning of a QR code and the subsequent creation of a new entry, an overlay appears on top of the entries in the home page. That overlay is the place holder that the user sees after launching the app for the first time. I don't have a screenshot so I'll just describe it in words:

(icon in the form of a blue key on grey circle)

Nothing Here! 

If you're new to Authenticator Pro, view the 
getting started guide by clicking below


GETTING STARTED GUIDE
IMPORT FROM OTHER APPS

This overlay can easily be dismissed by going to the Settings and then returning to the home page, so it's not that big of deal. Just though you'd like to know.

Alright, that's all I've got. Thanks for listening to my long rant and keep up the good work the makes this such an amazing app!

Hi there I have been using this App for a couple of months and everything works perfectly. Especially the WearOS App is the reason I chose this Authenticator. Unfortunately for about one or two months (I guess since the last update) the app won't start as usual. When I open it, it shows me the "Scan your finger" window as usual, but it closes immediately and I need to type in my password instead. When I press on "Use biometry" it shows up again and it scans my finger well. It does not show me my OTP tho, it is just an empty app with the Authenticator Pro Icon. If I go back to my Android home screen and open it up again, it finally opens up unlocked and it works fine. So everytime instead of 1) open app 2) scan fingerprint I have to 1) open App 2) Press "use biometry" 3) scan fingerprint 4) let it load an empty screen 5) close app 6) open app again.

Here's a video on how it looks. At the end when the screen is black, it shows the passwords as usual. https://i.imgur.com/lbMK6M5.mp4

Expected behavior I should be able to use the fingerprint sensor immediately and unlock my OTPs

App Version 1.14.10

Additional context Huawei P10 VTR-L09 Build 9.1.0.275 Android 9, EMUI 9.1.0

Describe the bug Every time I open the Wear OS app on my TicWatch 3 I only see the the loading animation. Initially I thought it just needs to fetch data from the phone but it didn't stop. Even minutes later only the animation is shown. Phone is connected. Now I discovered by accident I can swipe down and select a different category and immediately all the entries (of that category) are visible again. I can go back to show all entries and it works until I leave the app and come back, the same loading animation is shown again. This worked before. To be fair - not sure if this was introduced by an app update or by H-MR2, which I recently received.

To Reproduce See above.

Expected behavior "real time" visibility of all entries (at least after initial fetching)

App Version Wear OS: 2.3.1 Phone: 1.14.6

Hello,

I've been using this app for a while now and I'm super happy with it, especially compared to other authenticator apps. Thanks for making it!

One pain point I encounter tho is long startup times when the app isn't cached. On a Nexus 6 running Android 8 (yes, it's a bit old by now) with version 1.9.0 and 14 entries in the app, I count 5 seconds until the app shows anything, and another 2-3 seconds until the authenticators appear.

Can something be improved here?

Thanks!

Describe the bug Upon unlocking the app with fingerprint, I'm immediately returned to the phone's home screen. App continues to run in the background so I need to swipe up and bring the app to the foreground in order to access the TOTP codes. This is fairly recent behavior...within the last couple or three weeks.

To Reproduce

1. Unlock the app with your fingerprint Result: I'm taken back to my phone's home screen

Expected behavior This is relatively new behavior. Previously, the app would remain in the foreground after fingerprint unlock. It's entirely possible that I've inadvertently changed an Android system setting that's causing this; however other apps that use fingerprint unlock don't exhibit this behavior.

App Version 1.14.10

Additional context Pixel 3XL running Android 11 with the 06/2021 security patches

Describe the bug This is a similar bug to #34 however it's specific to the Wear OS app. Cold starting the app (i.e. starting it after a long time of not using it) can take 6-10 seconds, which is rather annoying and unresponsive. The authenticator is a relatively simple app and shouldn't take this long to start in my opinion. I expect it to start within 1-2 seconds. I think the issue is caused by it needing to sync with the phone before it starts up, which can take a while. However, I think the priority should go to start up because 99% of the time a sync is not needed.

However, once its started up, closing it and then starting it becomes fast again.

Other Notes:

• I have 4 keys stored at the moment.
• I'm running it on a Huawei Watch 2 0195 with Wear OS version 2.26

This is the error I received:

System.Exception: Shared connection not open at AuthenticatorPro.Droid.Data.Database.GetSharedConnection () [0x00081] in <8ccd3beddf5942399980abce6980c996>:0 at AuthenticatorPro.Droid.Activity.MainActivity.OnCreate (Android.OS.Bundle savedInstanceState) [0x00268] in <8ccd3beddf5942399980abce6980c996>:0 at System.Runtime.CompilerServices.AsyncMethodBuilderCore+<>c.b__7_0 (System.Object state) [0x00000] in :0 at Android.App.SyncContext+<>c__DisplayClass2_0.b__0 () [0x00000] in :0 at Java.Lang.Thread+RunnableImplementor.Run () [0x00008] in :0 at Java.Lang.IRunnableInvoker.n_Run (System.IntPtr jnienv, System.IntPtr native__this) [0x00008] in :0 at (wrapper dynamic-method) Android.Runtime.DynamicMethodNameCounter.37(intptr,intptr)

Would it be possible to add translations to the App? I could contribute to German and Thai localization.

Crodwin/.po files/strings whatever floats your boat @jamie-mh :smile:

Thanks for this awesome app!

Is your feature request related to a problem? Please describe. I would like to ask if you can please add the logo

Describe the solution you'd like Sample URL: https://a.screenconnect.com/

Google play app: https://play.google.com/store/apps/details?id=com.screenconnect.androidclient

Additional context

Bumps Microsoft.NET.Test.Sdk from 17.3.2 to 17.4.1.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Bumps protobuf-net from 3.1.22 to 3.1.26.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Bumps Xamarin.Essentials from 1.7.3 to 1.7.4.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Please fill out the fields below where applicable:

Name of website / service: DS Logon https://myaccess.dmdc.osd.mil/identitymanagement/app/login

PS: This is the DoD and Veterans universal login. Here is the icon: https://www.myhealth.va.gov/mhv-portal-web/documents/314545/444503/DS-Logon-Icon-Large.png/3b6c4fa5-d257-617a-451d-63f6372e8f89?t=1628528295771

Bumps Microsoft.CodeAnalysis.NetAnalyzers from 6.0.0 to 7.0.0.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.