3.4.0 Internal Inconsistency Exception [Should be fixed in 3.4.2 β1]]

Jabberwock

Hello,

I just downloaded 3.4.0 I am running Snow Leopard. When I open 1P3 I get the spinning beachball that locks up the computer until I force quit 1P3. But while 1P3 is still running and the beachball is spinning a dialogue box pops up that says:



NSInternalinconsistencyException

Exception: (null) Should not be expanded already!



I just reinstalled the previous version I had (3.3.1). It is running fine...no beachball and no error.



What is wrong and what should I do? Thanks.

kastorff

Same problem here.

khad

Thanks for the heads up! We are beginning to look into this. Have you tried anything to troubleshoot yet? Restart the computer, etc.



I don't have much information to share right now, but I just wanted to make sure you know we are aware of this.



Any additional information you have can help us fix the problem since we can't seem to duplicate this yet in the lab.

vandy

Same here, except the message for me was "Exception: Invalid parameter not satisfying itemEntry-> children = = NULL". I thought I would just replace 3.4.0 with 3.3.1 from my backup and launched the 3.3.1 backup just to make sure it would run. It did. Then, for the heck of it, I launched 3.4.0. Guess what? It launched and ran perfectly and has been running just fine for several hours now.

MikeT

Hi guys,



This should be fixed in 3.4.1, we are trying to push this out as soon as possible.



[b]Update[/b]: We just published 3.4.1, could you update to it and let us know if it fixed your issues.



Thanks!

Lorne

Not fixed in 3.4.1: my error message is



NSInternalConsistencyException



Exception: (null) should not be expanded already



Browser extension (in Firefox) still seems to work.

vandy

No problems on update to 3.4.1, but I didn't have any after I launched my 3.3.1 backup and then launched 3.4.0 so I may not be a good test.

MikeT

[quote name='Lorne' timestamp='1284308530' post='10937']

Not fixed in 3.4.1: my error message is



NSInternalConsistencyException



Exception: (null) should not be expanded already



Browser extension (in Firefox) still seems to work.

[/quote]

Thanks for the report, we're continuing to look into it some more. We might need some information from you soon.



[quote name='vandy' timestamp='1284308644' post='10938']

No problems on update to 3.4.1, but I didn't have any after I launched my 3.3.1 backup and then launched 3.4.0 so I may not be a good test.

[/quote]



Thanks for checking it for us. This crash is limited to a small number of our users, if you didn't get a crash in 3.4.0, you're likely not to be affected by this bug.

kitmos

No problem here with 3.4.0 (hopefully didn’t just jinx it)



Cheers,



Kit

vandy

[quote name='MikeT' timestamp='1284309432' post='10940']

Thanks for checking it for us. This crash is limited to a small number of our users, if you didn't get a crash in 3.4.0, you're likely not to be affected by this bug.

[/quote]



But I *did* have the problem with 3.4.0. See my post from yesterday at 9:33 PM. After not being able to get 3.4.0 to run without crashing, I launched 3.3.1 from my backup drive. Then, for the heck of it, I tried 3.4.0 again and it launched without problem. Maybe that is a clue?

kastorff

First launch after updating to 3.4.1 produced the original error message, but did not lock up 1Password as before. I was able to quit 1Password. On subsequent launches the error was gone.

MikeT

[quote name='vandy' timestamp='1284315911' post='10960']

But I *did* have the problem with 3.4.0. See my post from yesterday at 9:33 PM. After not being able to get 3.4.0 to run without crashing, I launched 3.3.1 from my backup drive. Then, for the heck of it, I tried 3.4.0 again and it launched without problem. Maybe that is a clue?

[/quote] Ah, sorry, I didn't see the previous post from you. This internal inconsistency bug is very specific, it could definitely be related to yours. We'll look into it.





[quote name='kastorff' timestamp='1284316640' post='10961']

First launch after updating to 3.4.1 produced the original error message, but did not lock up 1Password as before. I was able to quit 1Password. On subsequent launches the error was gone.

[/quote] The fix we included in 3.4.1 would reduce the chances of 1Password being crashed completely, so your report will help narrow it down for us. Thank you.

chashulme

Unbeknownst to me, I just tried the 3.4.1 update (from 3.3.1) on one of my machines and got two successive crashes (too quick to read the error) on launch, then after rebooting I got the error (which is actually):

_____________



[b][/b]NSInternalInconsistencyException



Exception: (null) should not be expanded already!

_____________



I also get a bunch of sync errors (which I canceled) and closed the app down.



If I want to fall back to 3.3.1 can I just install over, or do I need to trash the app (et al) and reinstall?

Lorne

I get similar behaviour now, screen flickers a lot, contents of side panel disappear, synch errors, but I can quit the application, whereas previously it hung and I had to kill it. No errors until I actually sign into the application, it seems.

roustem

Please try download and install [url=http://aws.cachefly.net/aws/dmg/1PW3/English/1Password-3.4.2.BETA-1.zip]3.4.2.BETA-1[/url].

Lorne

Thanks, no problems so far, after five minutes or so. I'm using DropBox (probably should have mentioned that before) and got a couple of Growl notifications which I haven't noticed before, they closed before I could read them properly. Something like '_lock_ added ...', then '_lock_ deleted ...'.

chashulme

Installed 3.4.2 ß1 and it seems to work, but the sync conflicts remain. There really shouldn't even be any conflicts, so this must have been a result of running 3.4.1 in some way. There are none (conflicts) on my other 3.3.1 machines, so I'm a bit unsure of how to proceed.

roustem

[quote name='chashulme' timestamp='1284330266' post='11005']

Installed 3.4.2 ß1 and it seems to work, but the sync conflicts remain. There really shouldn't even be any conflicts, so this must have been a result of running 3.4.1 in some way. There are none (conflicts) on my other 3.3.1 machines, so I'm a bit unsure of how to proceed.

[/quote]



Thank you for the update!



We just added a conflict resolver for Dropbox-generated conflicts in 3.4. Before 3.4 the conflicted copies were simply ignored.

whooba

Same here. Upgraded to 3.4.1 (from 3.3.1) as prompted and received the [i]NSInternalInconsistencyException | Exception: (null) should not be expanded already![/i] message.



Downloaded the 3.4.2 beta and the same thing happens: get the above error, spinning beach ball and have to force quit.



Downgraded to 3.3.1 and that seems to be working fine. To confirm, yes I'm using Dropbox.

chashulme

OK, my problem machine offered me 3.4.2ß2 which I installed and proceeded to resolve all conflicts... So far, so good (although I still don't get why there were any conflicts in the first place... Esp the multiples of the same record...).



But now my other 3.3.1 machines, which I expected would offer me ß2, are trying to ‘sell me’ 3.4.1 - the version that started this whole episode (don't really wanna go there~). And yous guys haven't posted a link to ß2 - only ß1... So, should I stay pat, with one machine at ß2 and the others at 3.3.1 for now? Or, do you plan to post access to ß2? Or something new and completely different? <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_wink.png' class='bbc_emoticon' alt=';-)' />

roustem

[quote name='chashulme' timestamp='1284399762' post='11058']

OK, my problem machine offered me 3.4.2ß2 which I installed and proceeded to resolve all conflicts... So far, so good (although I still don't get why there were any conflicts in the first place... Esp the multiples of the same record...).



But now my other 3.3.1 machines, which I expected would offer me ß2, are trying to ‘sell me’ 3.4.1 - the version that started this whole episode (don't really wanna go there~). And yous guys haven't posted a link to ß2 - only ß1... So, should I stay pat, with one machine at ß2 and the others at 3.3.1 for now? Or, do you plan to post access to ß2? Or something new and completely different? <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_wink.png' class='bbc_emoticon' alt=';-)' />

[/quote]



I wasn't sure that 3.4.2.BETA-1 fixes the problem and didn't make it available for the auto-updater.



For now it can be downloaded using this link:

http://aws.cachefly.net/aws/dmg/1PW3/English/1Password-3.4.2.BETA-1.zip

lcottrell

[quote name='roustem' timestamp='1284322788' post='10984']

Please try download and install [url=http://aws.cachefly.net/aws/dmg/1PW3/English/1Password-3.4.2.BETA-1.zip]3.4.2.BETA-1[/url].

[/quote]



I am seeing the same problem. Just installed the beta.

[indent]NSInternalInconsistencyException

Exception: (null) should not be expanded already![/indent]



I emailed in the full crash report. I see this about 5 seconds after I enter my password on launching 1Password.



.....



Ok, just got another update. Now I am seeing lots of different errors, some conflicts, then it crashed.

roustem

[quote name='chashulme' timestamp='1284399762' post='11058']

OK, my problem machine offered me 3.4.2ß2 which I installed and proceeded to resolve all conflicts... So far, so good (although I still don't get why there were any conflicts in the first place... Esp the multiples of the same record...).



But now my other 3.3.1 machines, which I expected would offer me ß2, are trying to ‘sell me’ 3.4.1 - the version that started this whole episode (don't really wanna go there~). And yous guys haven't posted a link to ß2 - only ß1... So, should I stay pat, with one machine at ß2 and the others at 3.3.1 for now? Or, do you plan to post access to ß2? Or something new and completely different? <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_wink.png' class='bbc_emoticon' alt=';-)' />

[/quote]



We have 3.4.2.BETA-3 now available. Please use 1Password > Preferences > Updates to enable betas and then click "Check Now" button to install the latest build.

leicaman

[quote name='kastorff' timestamp='1284316640' post='10961']

First launch after updating to 3.4.1 produced the original error message, but did not lock up 1Password as before. I was able to quit 1Password. On subsequent launches the error was gone.

[/quote]



Exact same thing happened to me. First start up of 3.4.1 (I sent in the force quit report before restarting 1Password) had the error. Subsequent start ups do not.



(Edit: Just updated to the beta 3 and seems to be going smoothly.)

NovaScotian

Running 3.4.2ß2, I find that I'm asked to resolve conflicts when I start the application every time a password is actually used or has been recently. When I compare the two (my G5 and Dropbox) there is only a few minor differences in the "more information" sections (the hash, for instance) but none at all in the actual useful data. Shouldn't it be the data that counts?

MikeT

[quote name='NovaScotian' timestamp='1284508660' post='11170']

Running 3.4.2ß2, I find that I'm asked to resolve conflicts when I start the application every time a password is actually used or has been recently. When I compare the two (my G5 and Dropbox) there is only a few minor differences in the "more information" sections (the hash, for instance) but none at all in the actual useful data. Shouldn't it be the data that counts?

[/quote]Hi NovaScotian,

The data integrity requires that even the smallest change (like a space appended) be kept in order to ensure no data is lost at all.



The way Dropbox does this is likely by hashing the whole file and the way hash works is that even a time difference or a small change like removing a space can change the entire hash at once. Dropbox does not look inside and determine which part is useful for you. There's no way to say which detail is useful and which isn't. We can't automate that decision.



It shouldn't be common to have conflict copies but it happens when Dropbox could not tell which file has changed last and so it keeps the previous copy as a conflict.



Could you first update to the final version of 1Password, 3.4.2 and rebuild your data file on your Mac? It should take a few minutes for it to be done and then Dropbox should start to sync the rebuilt data file back up to the cloud.



Try again and let me know if the conflicts are still appearing.

chashulme

[quote name='roustem' timestamp='1284473448' post='11123']

We have 3.4.2.BETA-3 now available. Please use 1Password > Preferences > Updates to enable betas and then click "Check Now" button to install the latest build.

[/quote]



FYI, even with Beta's enabled in Prefs, my 3.3.1 clients still offer me only the 3.4.2 update, with no mention of ß's.



[s]To get to ß3, I installed from your ß1 link, then updated via ‘Check for Updates...’.[/s]



I spoke too soon, since nothing will permit me to get to ß3. The in-app update check worked for my problem machine, but will not get me to ß3 - only back to 3.4.2. Do I have to trash prefs or something? This is weird... <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/wacko.gif' class='bbc_emoticon' alt=':wacko:' />



Thought you should know.



ß3 seems to work just fine... <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/smile.gif' class='bbc_emoticon' alt=':)' /> (on my singular machine that I have it running on)

chashulme

[quote name='MikeT' timestamp='1284570773' post='11233']

...

Could you first update to the final version of 1Password, 3.4.2

...

[/quote]



Given my current issue, and on close read of this, are you saying that two (or multiple) versions of 3.4.2 have seen the light of day? And, if true, that might explain why all my attempts to get to ß3 end up at 3.4.2?



If this is so, its certainly got me confused... <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/huh.gif' class='bbc_emoticon' alt=':huh:' />



Please advise.



Thanks.

roustem

[quote name='chashulme' timestamp='1284580320' post='11247']

Given my current issue, and on close read of this, are you saying that two (or multiple) versions of 3.4.2 have seen the light of day? And, if true, that might explain why all my attempts to get to ß3 end up at 3.4.2?



If this is so, its certainly got me confused... <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/huh.gif' class='bbc_emoticon' alt=':huh:' />



Please advise.



Thanks.

[/quote]



We had four beta builds for 3.4.2 and then the final release.

geekchick

The final build doesn't seem to fix the issue for me. I log in to the app, and immediately crash.

NovaScotian

[quote name='MikeT' timestamp='1284570773' post='11233']

Hi NovaScotian,

The data integrity requires that even the smallest change (like a space appended) be kept in order to ensure no data is lost at all.



The way Dropbox does this is likely by hashing the whole file and the way hash works is that even a time difference or a small change like removing a space can change the entire hash at once. Dropbox does not look inside and determine which part is useful for you. There's no way to say which detail is useful and which isn't. We can't automate that decision.



It shouldn't be common to have conflict copies but it happens when Dropbox could not tell which file has changed last and so it keeps the previous copy as a conflict.



Could you first update to the final version of 1Password, 3.4.2 and rebuild your data file on your Mac? It should take a few minutes for it to be done and then Dropbox should start to sync the rebuilt data file back up to the cloud.



Try again and let me know if the conflicts are still appearing.

[/quote]



I just updated to 3.4.2, logged in, and was presented with two conflicts right off the bat on my G5 (10.5.<img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/emoticon-0103-cool.gif' class='bbc_emoticon' alt='8)' /> and on my MBP (10.6.4) so it's got to be rather minor differences. I resolved one in favor of Dropcopy on the laptop and a conflict on the PM immediately showed up. Perhaps the more comfortable and only marginally more risky way to go is to turn off conflict resolution and live with the minor differences.