I can't open my vault anymore!
Hello Agilebits,
From my Android device running 1Password 7.0.5 I was asked to update my database each time I started the app. At some point I went a bit annoyed and clicked yes instead of skipping. The consequence were not clearly presented to me.
The update was done quickly and successfully and I am able to use my vault on Android.
But now I cannot access it anymore on my Mac ! 1Password 3 cannot find the vault file in Dropbox. I now have two folders, 1Password.opvault and 1Password.legacyagilekeychain. But neither of them will be recognized by 1Password 3.
I paid a hefty price for the 1Password 3 licence. I undestand it's "legacy" software for you but it's fine for me. Now that I was surreptitiously upgraded to the new vault format, I can't access my data with the software I bought.
This looks like planned obsolescence to me.
What am I supposed to do?
Thank you.
1Password Version: 3.8.22 (build 32010)
Extension Version: Not Provided
OS Version: 10.14 (Mojave)
Sync Type: Dropbox
Comments
-
@jmetillon: Thanks for getting in touch. I'm sorry for the confusion. Rather than "planned obsolescence", the world — including your Mac and mobile devices — have moved on since we released the AgileKeychain format in 2007 or so and 1Password for Mac version 3 in 2009. The latter was retired half a decade ago, but we've only this year finally finished the transition to OPVault, which was released in 2013 or so.
While I'm glad that you've gotten so much milage out of our old software, I can't imagine you're using anything else from a decade ago. You're free to continue to use 1Password the way you were previously (your original vault is still right where you left it), but it isn't something we can recommend, both for usability and security, since 1Password 3 will not work with any recent browsers: it predates the existence of Google Chrome, after all. You can learn more details in the announcement at the top of this forum category:
1Password 3: Modern browsers and OS X
1Password 7, one the other hand, fully supports macOS Sierra, High Sierra, and Mojave, along with the latest web browsers. You'll have a much better experience there, so you may want to consider upgrading to that. You can get that and the latest version of all of the apps as part of a 1Password.com membership. I hope this helps. Be sure to let us know if you have any other questions! :)
0 -
Hello @brenty thank you for the quick reply.
You're free to continue to use 1Password the way you were previously (your original vault is still right where you left it)
I don't see that. When starting 1Password 3 on Mac I have the Welcome to 1Password screen. I click Find Existing. The Mac file picker opens and I can see in my Dropbox I have two folders, 1Password.opvault and 1Password.legacyagilekeychain.
Previously, the vault was just one file and 1Password would recognize it immediately.
So where is my original vault please?
Thank you.
0 -
@jmetillon: 1Password vaults have always been a folder made up of many files.
1Password.legacyagilekeychainis your original vault. You can rename it to1Password.agilekeychain.I hate to be a pain, but you started having compatibility issues over three years ago. So I'll just say that it would really be better to move forward rather than backward. But it's your prerogative.
0 -
Hello,
After finding out how to access again my legacy agile keychain, 1Password is now crashing when opening my vault.
The initial screen with the master password is displayed. I type my master password. Type Enter. And it crashes immediately.
Here are the details from the crash report:
Process: 1Password [2901] Path: /Applications/1Password.app/Contents/MacOS/1Password Identifier: ws.agile.1Password Version: 3.8.22 (32010) Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: 1Password [2901] User ID: 501 Date/Time: 2018-10-09 14:54:09.375 +0200 OS Version: Mac OS X 10.14 (18A391) Report Version: 12 Time Awake Since Boot: 23000 seconds Time Since Wake: 1400 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Application Specific Information: ¿G∫4ˇ Assertion failed: (0), function compress_data_to_8_bit, file /BuildRoot/Library/Caches/com.apple.xbs/Sources/CoreGraphics/CoreGraphics-1245.8.4.8/CoreGraphics/Images/CGImage.c, line 640. Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x00007fff63c1fb86 __pthread_kill + 10 1 libsystem_pthread.dylib 0x00007fff63cd5c50 pthread_kill + 285 2 libsystem_c.dylib 0x00007fff63b891c9 abort + 127 3 libsystem_c.dylib 0x00007fff63b51868 __assert_rtn + 320 4 com.apple.CoreGraphics 0x00007fff36fc7d9f CGImageMaskCreate + 1185 5 ws.agile.1Password 0x0000000100026276 0x100000000 + 156278 6 ws.agile.1Password 0x00000001000268e5 0x100000000 + 157925 7 ws.agile.1Password 0x00000001000237ce 0x100000000 + 145358 8 com.apple.AppKit 0x00007fff33f99e12 -[NSIBObjectData nibInstantiateWithOwner:options:topLevelObjects:] + 1697 9 com.apple.AppKit 0x00007fff3412f6bf -[NSNib _instantiateNibWithExternalNameTable:options:] + 679 10 com.apple.AppKit 0x00007fff343bdd94 -[NSNib instantiateNibWithOwner:topLevelObjects:] + 233 11 ws.agile.1Password 0x0000000100027335 0x100000000 + 160565 12 ws.agile.1Password 0x000000010000c829 0x100000000 + 51241 13 ws.agile.1Password 0x0000000100008f11 0x100000000 + 36625 14 ws.agile.1Password 0x000000010000c26c 0x100000000 + 49772 15 com.apple.CoreFoundation 0x00007fff36ab1306 __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12 16 com.apple.CoreFoundation 0x00007fff36ab1280 ___CFXRegistrationPost_block_invoke + 63 17 com.apple.CoreFoundation 0x00007fff36ab11a1 _CFXRegistrationPost + 398 18 com.apple.CoreFoundation 0x00007fff36ab95ed ___CFXNotificationPost_block_invoke + 87 19 com.apple.CoreFoundation 0x00007fff36a2013a -[_CFXNotificationRegistrar find:object:observer:enumerator:] + 1633 20 com.apple.CoreFoundation 0x00007fff36a1f4fd _CFXNotificationPost + 742 21 com.apple.Foundation 0x00007fff38da1bab -[NSNotificationCenter postNotificationName:object:userInfo:] + 66 22 ws.agile.1Password 0x00000001000fbaf7 0x100000000 + 1030903 23 com.apple.Foundation 0x00007fff38e41cdb __NSThreadPerformPerform + 327 24 com.apple.CoreFoundation 0x00007fff36a69405 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17 25 com.apple.CoreFoundation 0x00007fff36a693ab __CFRunLoopDoSource0 + 108 26 com.apple.CoreFoundation 0x00007fff36a4ce51 __CFRunLoopDoSources0 + 195 27 com.apple.CoreFoundation 0x00007fff36a4c3fa __CFRunLoopRun + 1219 28 com.apple.CoreFoundation 0x00007fff36a4bce4 CFRunLoopRunSpecific + 463 29 com.apple.HIToolbox 0x00007fff35ce5895 RunCurrentEventLoopInMode + 293 30 com.apple.HIToolbox 0x00007fff35ce54d4 ReceiveNextEventCommon + 371 31 com.apple.HIToolbox 0x00007fff35ce5348 _BlockUntilNextEventMatchingListInModeWithFilter + 64 32 com.apple.AppKit 0x00007fff33fa295b _DPSNextEvent + 997 33 com.apple.AppKit 0x00007fff33fa16fa -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1362 34 com.apple.AppKit 0x00007fff33f9b75d -[NSApplication run] + 699 35 com.apple.AppKit 0x00007fff33f8ae97 NSApplicationMain + 780 36 ws.agile.1Password 0x0000000100001dd4 0x100000000 + 7636 Thread 1: 0 libsystem_pthread.dylib 0x00007fff63cd2408 start_wqthread + 0 1 ??? 0x0000000054485244 0 + 1414025796 Thread 2: 0 libsystem_pthread.dylib 0x00007fff63cd2408 start_wqthread + 0 1 ??? 0x0000000054485244 0 + 1414025796 Thread 3: 0 libsystem_pthread.dylib 0x00007fff63cd2408 start_wqthread + 0 1 ??? 0x0000000054485244 0 + 1414025796 Thread 4: 0 libsystem_pthread.dylib 0x00007fff63cd2408 start_wqthread + 0 1 ??? 0x0000000054485244 0 + 1414025796 Thread 5:: CVDisplayLink 0 libsystem_kernel.dylib 0x00007fff63c1d1b2 __psynch_cvwait + 10 1 libsystem_pthread.dylib 0x00007fff63cd65fe _pthread_cond_wait + 775 2 com.apple.CoreVideo 0x00007fff38887837 CVDisplayLink::waitUntil(unsigned long long) + 237 3 com.apple.CoreVideo 0x00007fff38886db8 CVDisplayLink::runIOThread() + 506 4 libsystem_pthread.dylib 0x00007fff63cd333d _pthread_body + 126 5 libsystem_pthread.dylib 0x00007fff63cd62a7 _pthread_start + 70 6 libsystem_pthread.dylib 0x00007fff63cd2425 thread_start + 13 Thread 6:: com.apple.NSEventThread 0 libsystem_kernel.dylib 0x00007fff63c19c2a mach_msg_trap + 10 1 libsystem_kernel.dylib 0x00007fff63c1a174 mach_msg + 60 2 com.apple.CoreFoundation 0x00007fff36a4d05e __CFRunLoopServiceMachPort + 337 3 com.apple.CoreFoundation 0x00007fff36a4c5ad __CFRunLoopRun + 1654 4 com.apple.CoreFoundation 0x00007fff36a4bce4 CFRunLoopRunSpecific + 463 5 com.apple.AppKit 0x00007fff33fab581 _NSEventThread + 160 6 libsystem_pthread.dylib 0x00007fff63cd333d _pthread_body + 126 7 libsystem_pthread.dylib 0x00007fff63cd62a7 _pthread_start + 70 8 libsystem_pthread.dylib 0x00007fff63cd2425 thread_start + 13 Thread 7: 0 libsystem_pthread.dylib 0x00007fff63cd2408 start_wqthread + 0 1 ??? 0x0000000054485244 0 + 1414025796 Thread 0 crashed with X86 Thread State (64-bit): rax: 0x0000000000000000 rbx: 0x000000010e5f75c0 rcx: 0x00007ffeefbfd148 rdx: 0x0000000000000000 rdi: 0x0000000000000307 rsi: 0x0000000000000006 rbp: 0x00007ffeefbfd180 rsp: 0x00007ffeefbfd148 r8: 0x0000000000000280 r9: 0xcccccccccccccccd r10: 0x0000000000000000 r11: 0x0000000000000206 r12: 0x0000000000000307 r13: 0x0000000109df3000 r14: 0x0000000000000006 r15: 0x000000000000002d rip: 0x00007fff63c1fb86 rfl: 0x0000000000000206 cr2: 0x00007fff95b7d188 Logical CPU: 0 Error Code: 0x02000148 Trap Number: 133
(too long, edited)
1Password Version: 3.8.22 (build 32010)
Extension Version: Not Provided
OS Version: 10.14 (Mojave)
Sync Type: Dropbox0 -
Thanks to this message from @MikeT I simply renamed the folder 1Password.legacyagilekeychain to 1Password.agilekeychain and now it's instantly recognized by 1Password 3!
But it's crashing :(
0 -
@brenty sorry our messages crossed each others. Thanks for the renaming tip.
Oh regarding the Can't see text issue under El Capitan beta, I don't have it anymore. It's still ok under Mojave. Though I have another issue that persists: when trying to resize the main window or even a column, 1P crashes. But I've learned to leave with it.
Btw, I have a new issue regarding opening my vault, which I can't live with and I detailed here but the message is waiting for your moderation.
0 -
@jmetillon: 1Password 3 has not been under active development since 2012, and many of the macOS OS X technologies it depends on have been changed, deprecated, or removed outright. So the issues you have today will not get better with successive OS updates. You'd have to go back to Snow Leopard or Lion for 1Password 3 to truly work properly.
0 -
But it was working very fine just before your Android app sneakily made me change my vault format, that is shared with my Mac desktop and laptop through Dropbox!
Or is it just a coincidence that, while I could not access my vault, I also updated my Mac computers from High Sierra to Mojave? And now that I fixed my vault (renaming it), 1Password is totally crashing when opening the vault because of a compatibility issue with Mojave? Not because vault has been corrupted by the 1Password Android app operation on my vault?
0 -
But it was working very fine just before your Android app sneakily made me change my vault format, that is shared with my Mac desktop and laptop through Dropbox!
@jmetillon: You mean before you upgraded the app and then chose to convert to the new format we introduced half a decade ago?
Or is it just a coincidence that, while I could not access my vault, I also updated my Mac computers from High Sierra to Mojave? And now that I fixed my vault (renaming it), 1Password is totally crashing when opening the vault because of a compatibility issue with Mojave? Not because vault has been corrupted by the 1Password Android app operation on my vault?
I'm not following you here. Literally two things happened when you chose to convert your data to OPVault format:
- Data was put into the new OPVault
- Old AgileKeychain vault was renamed from
.agilekeychaintoo.legacyagilekeychain
If you look in this forum, you'll see that other people have been experiencing crashes on not only Mojave, but other less-recent macOS releases. If you weren't having any issues prior upgrading to Mojave, that's surprising to me, as this has been coming up for years now. I'm sorry if this has come as a surprise to you, but you've been very lucky if that is the case. There is no "fix" coming for this, as the four major 1Password releases (and literally hundreds of minor updates) over the years are the result of our work maintaining compatibility with OS and browser updates. :blush:
0 -
Thank you Brenty.
You mean before you upgraded the app and then chose to convert to the new format we introduced half a decade ago?
Not exactly. Conversion happened from the latest version of 1Password on Android. I run the latest (non-Pro) mobile app since years now. But it's only since a few weeks that the app started bugging me each time I launch it, asking me to upgrade my database. While not stating clearly that this would render my other 1Password client unusable.
Old AgileKeychain vault was renamed from .agilekeychain too .legacyagilekeychain
Yes, that I understood recently and that's nice.
you've been very lucky if that is the case.
Maybe, yeah. I just tried to create a new vault from 1P3 and see if it works. If so, it would have demonstrated that my legacy vault has been corrupted in some ways. But after creating a new vault, trying to add a new password crashes it instantly. And I can't re-open it without crashing. So yes, my copy of 1P3 is not compatible with Mojave. And I won't rollback my Apple computers to an older Mac OS X / macOS / MacAroni.
So I'm ready to move forward.
0 -
Not exactly. Conversion happened from the latest version of 1Password on Android. I run the latest (non-Pro) mobile app since years now. But it's only since a few weeks that the app started bugging me each time I launch it, asking me to upgrade my database. While not stating clearly that this would render my other 1Password client unusable.
@jmetillon: Hmm. The app wouldn't update at all if you hadn't set it to, and the conversion process is something you'd have to initiate yourself, as you described. Regardless, you've still got your original data as discussed above, so that helps.
Yes, that I understood recently and that's nice.
:) :+1: If nothing else, we want to make sure 1Password is not destructive.
Maybe, yeah. I just tried to create a new vault from 1P3 and see if it works. If so, it would have demonstrated that my legacy vault has been corrupted in some ways. But after creating a new vault, trying to add a new password crashes it instantly. And I can't re-open it without crashing. So yes, my copy of 1P3 is not compatible with Mojave. And I won't rollback my Apple computers to an older Mac OS X / macOS / MacAroni.
I hear you. I wouldn't want to do that either. The new stuff is just too cool for me to pass up!
So I'm ready to move forward.
Sounds good. Let's continue the conversation there. :)
0
