Unlocking takes 20s but instantaneous from App Extensions
Comments
-
Hi @diligiant
Our developers are aware of the issue and have a fix implemented in beta. If all goes well hopefully that fix will be included in the next update. :)
Ben
0 -
Great. Thank you
0 -
Anytime. I'm sorry for the inconvenience. Thanks for your patience!
0 -
I've complained about this issue countless times. They keep promising a forthcoming update will fix it. It's been more than four months and nothing despite several updates. After walking you through tech 101 questions and pretending it's the first they've heard of it, they finally acquiesce that it is indeed a known issue. It doesn't seem promising that it will be fixed anytime soon. When I inquired as to when we may expect a fix I received no reply. Considering the cost of the suite, you'd think they'd be a little more responsive. It's really frustrating and annoying, and honestly unprofessional to make promises they're clearly not keeping.
0 -
@Jerry_Diaz: We haven't promised anything actually, and it's dishonest to say otherwise. We've mentioned that we're working on a fix, and that's absolutely true. We've had several "fixes", many of which didn't pan out. The difficulty lies in the fact that the issue does not originate in 1Password, and does not affect everyone. This means that we need to find a workaround that helps those affected, without causing issues for others. It may be that today's update helps you, but not others. Have you tried it? Please let me know! I know that it has helped in some cases, but there is no panacea. :(
Personally, I encountered similar issues with a handful of apps on my iPhone 6 after updating to iOS 9. Apple's suggestion was first to Reset All Settings (not as bad as it sounds) and see if that helped. It didn't. The next option was to restore factory settings and set up as a new device. This is not something I'm willing to do. I ended up buying a new phone, and the problems (including power issues) went away, but I wouldn't wish any of this on anyone else, as it cost me a great deal of time, money, and frustration. I know it's been frustrating for you too, but it has been for us as well, as we don't benefit from our customers having a bad experience with 1Password, regardless of the cause. Or do you really think that we're happy that you and some of our other awesome customers are suffering? I wouldn't wish that on anyone. :unamused:
We're not giving up. And our track record shows that we're never content to leave things as they are, so we'll continue to do whatever we can to fix issues like this, along with improvements and other features as well.
0 -
@brenty Does the phrase "thou dost protest too much" ring a bell? Perhaps you're right. I misunderstood a software company's mentioning "we're working on a fix" to be a promise. (Never mind that I also stated I received no response when inquiring about a timeframe. Let's just focus on semantics).
I should have said "claiming to be." That would be more accurate. And yes, clearly my frustration at your lack of addressing the issue for at least 4 months must be indicative that what I really, and melodramatically think is that you're happy that I and other customers are suffering. Because this just MUST be a personal attack on us—I'm simply that darn petty and paranoid and assume everyone else is as well. Feel free to put words in my mouth while you call me (or my statement) "dishonest" for allegedly doing the same.
I realize it's much more productive to spend time pedantically splitting hairs about everything but the actual issue at hand, but all that aside, this is actually the 2nd device I've experienced the identical problem with. An iPhone 6 and a 6S with a clean install of iOS and the app. (Even though the issue "doesn't originate in 1Password," it seems it's the only app experiencing any such problem). Luck of the draw, huh?
Yes I installed yesterday's update, hence my post (much as it would have made more sense to just play irate angry customer and irrationally complain without having done so first). Would it surprise you to learn that it didn't fix it? After all, you never promised it would … or even might. Aw, look at that. Now I've protested too much.
0 -
Sorry to hear v6.2 has not addressed this issue for you. We do have a radar (bug) filed with Apple. Were hopeful that we can work together to resolve the root problem.
Ben
0 -
That would be the same non-promise promise you made in November (https://discussions.agilebits.com/discussion/52337/freeze-on-unlock-touch-id-since-update#latest) that I was referring to in my initial post on this thread
0 -
We filed the radar with Apple on December 18th. We did have a fix that we were testing back in November, which is now included in the stable release of the app, but as you've pointed out it did not resolve the issue for everyone. Rather than continue to try and patch around the issue (which thus far has had only very limited success), we've reached out to Apple directly to see if we can assist with resolving the issue on their end, or if they can point us in a different direction.
I'm sorry I don't have more encouraging news, but that is the latest information on the subject.
Ben
0
