![]() This indicates the input file is probably using Western (Mac OS Roman) text encoding. ![]() ![]() 6:32:23.463 AM 1Password 4: 430012 E importFileAtURL:ofType:subtype: | Failed to read import data: Error Domain=NSCocoaErrorDomain Code=261 "The file “SplashID_Export.vid” couldn’t be opened using text encoding Unicode (UTF-8)." UserInfo=0圆00000876980 With All Messages selected in the Console application, look for a message like this that appears during a failed import attempt: I've merged your topic with a related one and am happy to help with each of your specific problems: Hi really sorry you've gotten off to a rough start with 1Password by having so much trouble with importing your data from SplashID. I don't expect that this honest indictment will be published with solutions in your forum. I will express my opinions about the poor quality of 1Password in every forum available to me. I've already posted a warning for all my friends on Facebook against purchasing "1Password". I'm a software engineer myself who also spent many years in SQA at Apple, so I am VERY much aware of what egregious oversights these are. so now I'm stuck with ALL my records being little yellow "Secure Notes" regardless of the category assigned in SplashID. so the user can't even manually change the category of the hundreds of records imported. Problem #3: 1Password provides no facility for the user to change the category of any of its records. Problem #2: 1Password imports all SplashID records as "Secure Notes" regardless of the category assigned in SplashID. Really!?!? I am flabbergasted for many reasons, the main one being "Quality Assurance" and "Testing". This one symbol, in one record was causing the entire import to fail?!?!?! vid file, it just "beeps" with no further explanation or help to the user.Īfter scouring online forums and trying all the silly workarounds suggested by others, including AgileBits, I tried just exporting/importing a few records at a time, (from over a hundred), and discovered that there was just one record that had a "tm" trademark symbol in the notes. When 1Password fails to import from SplashID. Problem #1: 1Password fails to import from SplashID, even though the marketing claims it can. Suddenly SplashID is looking like a dream-come-true in comparison to "1Password". What a mistake! Now I just wish I had my money back from purchasing 1Password for my Mac and iOS devices. Today I decided to switch from using "SplashID", ( for many years), to "1Password" because I never felt the quality of SplashID was very good. I would suggest that you wait for a reply from a support person, who may well have some tips to help you. If you have a highly customized SplashID database like I had, it will be a chore to move. I don't know why you can only import a few records at a time, but I thought perhaps this would be useful perspective from another migrant to 1Password. I guess this doesn't really solve your problem. This means there is real inertia working against switching among the various options for password management. As you observe, there is quite a bit of editing to be done, even if the importer works. Others have many more and my approach might not be suitable for them. That wasn't fun, but I regard the time as having been well spent. Later I realized that I couldn't expect my idiosyncratic data to be handled smoothly by a generic importer, so when I finally did move, I reentered my data by hand. I had imported my database into 1Password a few years earlier, when I first thought of moving, but I found that my highly customized categories and records weren't handled very well. I moved from SplashID to 1Password last spring.
0 Comments
Leave a Reply. |