Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Former Member
4 years agoHundreds of duplicates
Made the decision to upgrade to version 8 and immediately regretted it. Probably 80% of my (hundreds of) logins were duplicated with no obvious pattern as to which were duplicated and which were not....
Former Member
4 years agoSimilar issues to the rest of you with 1P8. Duplicates at random, unclear why.
SOLUTION as noted above - Had to uninstall the new Safari web browser app and 1P8, then reinstall 1P7, use the Help tools menu to remove those duplicates that were exact duplicates. However, many duplicates showed up of earlier versions of a log in, so I had to use the dates last used/modified information to figure out which was the most current/or oldest in order to manually delete the duplicates. A tedious process but easy.
The new Apple OS update to 12.6 and Safari 16.0 also sems to have been the issue. This happened to me on two separate desktops, and I have only one vault set up and visible. Using OS 12.6 and Safari 16 with the latest versions of 1P8, or 1P7 and the two associated web browsers.
Has anyone noticed the next issue?
I could not get the 1P7 version of the Safari browser extension to work (with SAFARI 16) ie the one labelled as "7.9.6 from 1P 7". It would install, the icon showed up for a second, then vanished from the Safari bar despite several resets, log outs of 1P7.
I had to use the 1P8 version of the Safari browser extension for proper integration, this version is labeleld as" 1P for Safari 2.3.7 from 1P for Safari". This seems to be an issue with SAFARI 16, which just came out. Using 1P7 and the IP for Safari extension, provided the prior easy Safari integration, although the duplicate issue remains for those duplicates I have yet to get to.
I have been using 1P since version 2 and it has been pretty much flawless. This one upgrade has ruined the excellent record so far. Hopefully, they will see the issues and release an update soon. 1P is essential if it works as it used to.
Is there a separate issue with compatibility with the latest Apple system updates to 12.6 and Safari 16 as I appear to have?
Thanks.