WARNING: Pontification Ahead!!!The "name" the 1PW entry is saved as is usually the highest level domain name (
www.techsurvivors.net for example). All the information the app can use is in the html, which is plain text, of course. Your "name=xyz"/"ID=xyz"/whatever=xyz and the password are usually in a simple html form. A form has several standard items in each entry request. One item is the "name" or "label" for that item, the "xyz" is what the server stores as your entries. 1PW simply reads the html text, just like a human can, and captures identifying 'label' as well as your entry for that item, be it name/label/whatever. If the site changes anything that is saved in 1PW (such as the change in tech survivors domain name some years ago), the name of the label, etc., your 1PW entry will simply not work.
Of course, you can edit the actual data that 1PW uses, including the name of the label. But I highly recommend changing the name that appears in the list of possible log-ins list to something completely different than the normal domain name. Including a date or other identifying info will greatly aid in selecting the correct entry for any site. You can do this the first time you log in to a site that doesn't already have a 1PW entry, of course. But you can also do this when the 1PW entry fails and you have to enter the info a second time. Usually, you are offered a chance to create a new entry or change a current one. Obviously, changing any current one is better, since 1PW keeps a record of the dates/times the info was edited.
1PW has been one of the best working and useful apps I've ever used. One of the developers/employees was a local acquaintance. He is no longer working there, as far as I know. Other things have changed at Agile, I'm sure. Some of it may be caused by Apple's security improvements, API's or something else. I do know that they are extremely particular about what an app can do as far as communicating/changing data in other apps, at least in apps that it allows in the (Mac) App Store.
The above info is not a request for you to make modifications to your 1PW data. It is not a defense of Agile. It is not even an explanation of what is wrong with 1PW. It is simply an attempt to explain that many apps have to look at what is available from sources that they have no control over. It may help to stop and realize that these machines we so take for granted, are nothing short of 'miraculous,' (in the secular sense!).
That we become so upset (and I certainly fit that description!) by the operation of such an inanimate object reflects the faster pace we all try to live and the tools we use to accomplish that task.
You mentioned at least three different word processors that you depend on. Is that a reflection of the fact that none of them do something that only one of the others does better? And, word processing is a much, much more developed 'technology.' They have been around almost from the beginning of computers. Saving and encrypting passwords and inserting them into another app is much newer and, in my opinion, much more complicated than using the built-in services of the OS to make words look and behave in certain ways.
My only suggestion is to notify Agile that you will no longer be recommending their app and that you return to the built-in password capabilities of the OS, being aware that you will lose one level of security in the process. Nothing speaks louder to developers than loss of reputation and word-of-mouth recommendations.
We now return you to real Life, already in progress.
