New Entry Layout
CompletedThe text of this post has been moved to a support article:
https://support.huvisoft.dev/hc/en-us/articles/32672310996628-New-Entry-Layout
as this feature will be the new default for 10.6.
-
If I try the new layout can I easily switch back to the current layout? Or do I have to use ONLY the new layout going forward?
0 -
Good question. Yes, you can switch back to the current layout if you don't like the new one.
Please provide feedback here if you do, so we can improve the new layout before it becomes the new default.
0 -
I can see entries with TOTP I entered using the Windows version of Password Safe. But when I try to create a NEW entry or add a shared secret to an EXISTING entry using an iPhone 6s with pwSafe 2 v10.5.3 (50064), and I try to add an OTP shared secret key using the “+” and “One-Time Password,” it gives me a dialog box:
- - - - - - - - - - - - - -
One-Time Password
Enter the one-time password shared secretCancel Ok
- - - - - - - - - - - - - -
Pressing either “Cancel” or “Ok” makes the dialog box disappear, but I’m not given an opportunity to enter or paste the shared secret anywhere.
Thanks.0 -
Thanks for raising this. Just reproduced the issue in a simulator, looks like iOS 15 related (the latest for iPhone 6s). I also noticed that the “Done” button is not appearing, which is also needed to actually save the change to the database.
Will try to solve both for the next update.
0 -
Here is a screenshot from an iOS 16 device, showing how it should look like:
0 -
Haha, yes, that is what I expect to see. Thanks for accommodating we who have not gotten around to getting a newer iPhone.
0 -
Yeah, will probably do so for a few more months, the number of iOS 15 devices using pwSafe is getting really low..
Dropping iOS 15 support means also dropping macOS 12 support, which is the main reason why iOS 15 is still supported, since macOS 12 is more used.
I've added extra code to fix the two issues mentioned above, will be in the next update (likely to be released next week).
0 -
Just updated to the latest. Thank you for your efforts so far, and I appreciate the state of support for iOS 15.x.
I noticed some other strange behavior: I am able to successfully create OTPs now, but after locking the entry back up and moving on to the next entry that I need to enter the OTP seed, if I go back to the previously edited (i.e., the one to which the OTP seed was added), that entry reverts it being unlocked. On some occasions, not only does it become unlocked, the OTP entry disappears. I will dig deeper to find out if there’s a rhyme or reason for it and will get back to you in a couple of days. However, if this quirk is due to the old iOS, then no worries as I don’t think it is right to put you out for a niche issue: I have an alternative means of getting things working, kludgy as it is, by saving the seed codes in the pwSafe 2 Notes, and using iOS keychain to generate the codes. It is not ideal – working with two apps – but until I get a new device it will have to do. Regardless of whether you identify the issue before I get back to you with additional details, thank you for the awesome customer service over the years. Now, if I can just figure out why iPhone is back to identifying a pwSafe 2 file as merely a Macbinary archive, thus preventing my replacing my copy with an updated file I share with my wife.
0 -
Thanks for confirming that adding OTP works for iOS 15.
The new quirk you describe sounds not related to iOS release, so let's get this fixed.
In fact, I already found the cause for the entry reverting to unprotected (the final change in protection status is never saved). The fix for that will be in the next update.
The OTP disappearing is something I cannot explain at this point, so yes, please let me know if you find any sequence of steps to reproduce this. Also, in case it happens again, please create a support request using these steps immediately after it happens (without terminating the app) so I get some logging:
- Go back to the main view (listing your safes)
- Tap the gear icon (top left)
- Select Support request
I will do some testing myself to see if I can reproduce this in any way.
0 -
Oh, wrt the Macbinary archive, please check the file extension of the safe, it should be .psafe3 to be properly identified as pwSafe database.
You could also follow these steps to automatically synchronize the database with your wife:
0 -
I think I found the cause of the disappearing OTP (better: OTP not being shown even if available).
Will send version 10.5.5 for approval today, please give it a try when it is released (normally within one or two days). Both items you raised should be fixed.
0
Please sign in to leave a comment.
Comments
11 comments