This is a staging forum for AgileBits, not an official support forum. Visit http://discussions.agilebits.com instead.
1Password throws exception with search
I mentioned this in the Safari 5.0 thread, but I figured I should post it here.
This problem cropped up in the 3.2.0 and 3.2.1 builds. Whenever I try to use the search field in 1Password, I get the following error:
[attachment=67:1pass_error.png]
Other than this, filling and submitting forms (and using the extension in general) seems to work fine. This only occurs in the 1Password application.
This problem cropped up in the 3.2.0 and 3.2.1 builds. Whenever I try to use the search field in 1Password, I get the following error:
[attachment=67:1pass_error.png]
Other than this, filling and submitting forms (and using the extension in general) seems to work fine. This only occurs in the 1Password application.
Flag
0
Comments
-
Yep, same problem here! Everytime I try to use search the following exception is thrown:Flag 0
-
Same problem here:
NSInvalidArgumentException
-[NSCFNumber isEqualToString:]: unrecognized selector sent to instance 0x1004112c0
on OSX 10.6.3, macbook pro build 10D578Flag 0 -
Anyone here from Agile? Some feedback would be nice...Flag 0
-
Just "upgraded" to version 3, getting the same message
NSInvalidArgumentException
-[NSCFNumber isEqualToString:]: unrecognized selector sent to instance 0x1004112c0
Mac Pro, 10.6.3Flag 0 -
Searching results in this error:
NSInvalidArgumentException
*** -[NSCFNumber isEqualToString:]: unrecognized selector sent to instance 0x212d70
Started after upgrading to 1Password 3.2.1 (from a 2.x version)
Mac OS X 10.5.8
Safari 4.0.5
so it's not a Safari 5 or Snow Leopard bugFlag 0 -
Darn, I've kept 1Password v2 on my Leopard machine for EVER, and stupidly decided today to finally upgrade it to version 3.
I am now also getting the same errors...
specifically:
*** -[NSCFNumber isEqualToString:]: unrecognized selector sent to instance 0x212e40
On ANOTHER machine (I have the family license) running 10.6.3, which was moved to 1Password3 a long time ago, there is no bug!
So both machines are running the same 1Password version (3.2.1 build 30653), but only the Leopard "[B]freshly upgraded to 1Password v3[/B]" is exhibiting the search fault. Maybe that info will help the devs fix the bug.
Hope a fix comes soon.Flag 0 -
No, I'm running 10.6.3 and (see above), getting same error message, so it's not just Leopard.
I'm also having no joy from Agile support...and they don't seem to be reading this.
Don't like complaining, but this is kinda annoying.Flag 0 -
[quote name='davidplans']No, I'm running 10.6.3 and (see above), getting same error message, so it's not just Leopard.
I'm also having no joy from Agile support...and they don't seem to be reading this.
Don't like complaining, but this is kinda annoying.[/QUOTE]
If you're saying that to me - I didn't mean to say it was only Leopard - that just happens to be my issue. I did read the whole thread before posting. My point is that the very latest 1Password version works on some environments and not on others. From my experience, it's an upgrade from v2 to v3 glitch.
re: Support - you know, it's funny that I didn't even think of doing that. I'm so used to troubleshoot myself (with the help of Google that got me to this thread), that I often forget one of the benefits of paying for software is the support that comes with it.Flag 0 -
Hi folks,
I'm really sorry to hear you're all experiencing this issue, our developers are currently looking into what could be causing the problem and we hope to have a fix for this soon. Once we know more about when this will be available we'll make sure we post something here to let you all know. I know it's frustrating to have to wait, but if you can be patient with us we'll get this resolved ASAP.
Thanks,Flag 0 -
Ah I see, no worries.Flag 0
-
i was experiencing the same issues. i migrated to 1password 3 when i got my new macbook pro a few weeks ago. no problems at that time, but then had to reinstall my os yesterday for a separate issue and my problems began. after backing up my data file, i removed 1password and supporting files, i reinstalled the earlier version of 1password 3 (version 3.1.3) and everything works great again. i'm guessing there is a bug in the june 07 release somewhere...Flag 0
-
Thanks for using 1Password everyone! It seems this problem hit a number of customers but not all or this thread would be even longer. :) As Stu said, the developers are looking into the cause and hopefully we'll hear some good news about it quickly.
Welcome to the forums, pswdhelp, Eric, rubysue and SteelSerpent!Flag 0 -
I reinstalled me Mac yesterday and had the same issue. I then downgraded to 3.1.3 and the issue was resolved. Then I upgraded by using the Check for Updates... option within the program. Now I have 3.2.1 without the search exception. If I installed using the 3.2.1 DMG file, I had no luck. Not the ideal solution, but it might work for some.Flag 0
-
[quote name='Starburst76']I reinstalled me Mac yesterday and had the same issue. I then downgraded to 3.1.3 and the issue was resolved. Then I upgraded by using the Check for Updates... option within the program. Now I have 3.2.1 without the search exception. If I installed using the 3.2.1 DMG file, I had no luck. Not the ideal solution, but it might work for some.[/QUOTE]
Confirmed - that's a valid work around.
I had originally jumped straight from v2 to v3.2.1 using the DMG file and was having the problem.
By downgrading - installing v3.1.3 DMG available here:
[url]http://agile.ws/products/1Password/versions[/url]
and then updating through the "1Password > Check for updates..." menu, I'm now using the latest version without any problems.
:grin:
thanks Starburst76!Flag 0 -
Thanks, team!Flag 0
-
Welcome to the forums, benerbot, Minium and zach384738!
Please upgrade to 1Password 3.2.2 instead of back-tracking to 3.1.3 or another lower build in the 1Password 3 series. We discovered a problem with first-time upgrades from 1Password 2 to 1Password 3.2.1 (maybe even 3.2.0). The 3.2.2 release fixes this problem. We appreciate your patience and hope this helps out anyone else experiencing this exception in 3.2.1.Flag 0