App lock not working

that and the fact that it was working before the update which seemed to break it….

3.3.245.2448 on phone

same on playstore dated 29 Jul 2024

looking at the start of this thread it says

1. Go to Settings and scroll down to Installed Apps;
2. Tap on Bitdefender Security;
3. Tap on Permissions;
4. Make sure that the Display pop-up window permission is enabled; if not, please tap on it and set it to Accept.

I do not have the pop up window setting…….could that be why its not working?

edit…. I have now set it to use biometrics and my bank app (RBS) is going mental….using facial recognition it is intermittently telling me there is a technical error (attached) ….sometimes it works first time sometimes not at all….. very frustrating

I changed from PIN to biometrics and the applock does sometimes work but my banking app then throws an error suggesting I am not connected properly…..

Here is what I know:

1. The App Lock app was still having issues on August 20, 2024, when I posted my first message.
2. I took a screenshot, for my records, on that date so I could confirm if an update was ever completed and installed. That version on August 20, 2024, at 2:15 PM EST was 3.3.245.2448.
3. I checked for updates on my phone around and after September 1, 2024, but it was not updated.
4. I checked the Google Play Store on my phone on September 6, 2024, to see if there was an update in case the auto-update did not get pushed. It still showed the old version with a July 29, 2024 date.
5. I checked the version on the Google Play Store on my laptop on September 6, 2024, and while it showed an update on August 30, 2024, the version was still the same as before.
6. My BitDefender product on my phone shows version 3.3.245.2448 as of this message.
7. We receive no updates to our concerns when we post messages on this issue.
8. I posted images in an earlier message on this thread, as of September 6, 2024, as to what is on the Google Play Store on my phone and what is shown on my laptop. I do not know why there is a discrepancy in the "updated" date, but they both show the version from July 29, 2024. The August 30, 2024 date shown in the Google Play version on my laptop does not make any sense as it is what was on my phone on August 20, 2024.

I suggest moving the debate about the issue of versioning to separate topic. This topic is about non-woking feature which is still not functional. Mixing different issues will break the thread.

To btomaz:

I only mentioned my version numbers to prove the software I have on my phone is still the same today as it was on August 20, 2024. This conversation is still about the Aop Lock feature not working all of the time and how we were told on August 20 that a fix was found and it would be pushed out around the end of August.

I tried biometrics (was using PIN) and the app lock does intermittently work….but then using facial recognition I get this

I just checked my phone, and my app still has the same version as before. I also checked to see if any updates in the Google Play Store have not been pushed to me yet. Unfortunately, the Google Play Store still shows July 29, 2024, and the version I have as the most up-to-date one available. I have a Galaxy S23.

We are just users posting here. There is no interest in fixing this issue. The money comes from the Brand, BitDefender is already established. As annoying as it is, that this feature is not working, I am not looking forward to change to a different antivirus right now, and they know it.

Most users are not interested in the feature and if they were, they gave up already.

I have the exact same version as you. My screenshot would be exactly the same

Everything, for the most part, I wrote in my September 6, 2024 post with attachments is still the same. Version 3.3.245.2448 (the one on my phone since at least July 29, 2024) is still showing as the most up-to-date one in the Google Play Store on both my phone and my laptop. However, while the version has not changed the updated date has as it now shows September 6, 2024, just on my laptop. Four days ago, it showed August 30, 2024. On my phone, it still shows July 29, 2024. See attachments.

I am in the U.S. so I do not know if that matters when accessing the Google Play Store.

.

BTW, I had version 3.3.245.2448 on my phone on August 20, 2024. I know this because I took a screenshot of it when I first posted on this board, so I could verify if/when an update was pushed to my phone. See the two attachments.

I am frustrated as we now have a flood of screenshots showing versions reported on different devices. The only important thing is whether AL is working or not. When someone will discover that AL is actually working, then the version will matter.

Hello,

I realize you've been waiting a long time and It must be frustrating. I know I said the fix was scheduled for the end of August, but it's not ready yet and there are still some tests that need to be completed. Testing an app, feature or fix across the multitude of Android devices and configurations poses a significant challenge for the developers, as you can imagine. There are so many different Android devices, each with unique screen sizes, resolutions, processors, RAM, storage, sensors, and more. This hardware diversity makes it difficult to ensure that a feature performs well on ALL devices ALL of the time, so as a developer you need to make sure of that. Otherwise, any problem you think you've fixed now may resurface later on and this is exactly what they wish to avoid.

Also, I think we must take into account that although Google releases new versions of Android regularly, not all devices receive updates at the same pace. This leads to a variety of OS versions in use, and developers must ensure compatibility across older and newer versions. Many Android device manufacturers (e.g., Samsung, Xiaomi, Huawei) customize the Android OS with their own user interfaces, features, and optimizations. These custom ROMs can introduce variations in how apps/features behave, adding to the complexity of testing.

And the list goes on, really. Now, I'm not making excuses for them, nor pointing a finger elsewhere, but I wanted to show you the bigger picture. Yes, the feature doesn't work and yes, it's frustrating and you are right to be upset about it, but there's really nothing myself or anyone else here can do about it at this time, since there are no news yet. That's why I didn't post any updates on this thread. I do follow the thread, of course, but unfortunately I had nothing new to say and all we can do now is wait..

Thank you all for your patience.

Bitdenfender should hire staff who can solve the problem and not leave it to interns or ******.

Bitdefender is supposed to be a professional service, not a high school tech project..Anyone who works for BotDefender should be ashamed of the kindergarden schiol level of tech skills.