Sudden Exception loading group errors
 

I am suddenly experiencing multiple errors like this one when opening recently created documents:
[INDENT][I]Exception loading Group: -[Group disallowNotifications]: unrecognized selector sent to instance 0x107d91140[/I][/INDENT]
And then the docs are malformed.

Any ideas what might cause this?

Cheers,
Massimo

I've got the same problem. This seems to be caused (for me at least) by the latest beta of OSX Mountain Lion. The problems started occurring when i did the DP4 software update that appeared today.

With my documents it causes a lot of images (but not all) not to load in existing documents. New documents don't seem to experience this issue...

I'm having same error with OmniGraffle Pro 5.4 (v139.7 r167456) with OS X Mountain Lion update released yesterday. Problem also happening with OmniGraffle Pro 5.4.1 beta (v139.8 r167949).

Seems like anything grouped not handling well. Can't open properly, can't copy/paste, etc.

Also having this issue - Omnigraffle 5.4 v139.7 r167456 - OSX 10.8 (Build 12A248) -- There was a Java update for OSX that could have been involved? We are using beta version software but is anyone not on mountain lion experiencing similar issues?

Confirmed here as well - looks like a new bug or issue with the latest build. :(

Same exact bug for me (with a slightly different instance address) when opening an existing recent document.
[INDENT]"build Exception loading Group: -[Group disallowNotifications]: unrecognized selector sent to instance 0x101c43160"
[/INDENT]I am on Mountain Lion DP4 (10.8 build 12A248). I just downloaded OmniGraffle Pro v5.4 from the OmniGroup website. Here's the build info:
[INDENT]Product: OmniGrafflePro-5.4.x
Tag: OmniGraffle/5.4/GM-v135.7
Date: 2012-05-24 12:40:08 -0700
Builder: omnibuild
Host: tb107a.private.omnigroup.com
Revision: 167456
[/INDENT]

Same exception for me as well. Latest build of ML DP4.

Update: I grabbed the latest 5.4.1 beta and the problem is resolved.

[QUOTE=ahenriksen;111938]Update: I grabbed the latest 5.4.1 beta and the problem is resolved.[/QUOTE]

What version are you using? Because for me with r168675 i still have the problem. Anyone any luck after installing the DP4 security update?

Good news - this seems to be fixed in the security update that Apple posted yesterday - build 12A256.