Shortly after you form a connection, Interface Builder unexpectedly quits.
Solution
For developers not building EOF applications
If you do not plan to use Interface Builder to create EOF applications, the best workaround is to remove or disable the EOF palette. To disable it, follow these steps:
2. Open a Terminal window, then copy and paste in these lines:
cd /Developer/Palettes
mv EOPalette.palette EOPalette.palette.disabled
3. Open Interface Builder.
4. Dismiss the alert with this message "Unable to load palette..."
5. From the menu, choose Tools > Palettes > Palette Preferences...
6. Select "EOPalette" from the list.
7. Click Remove .
8. Close the Preferences window.
If you later want to use the palette, you can follow these steps to re-enable it:
2. Open a Terminal window, then copy and paste in these lines:
cd /Developer/Palettes
mv EOPalette.palette.disabled EOPalette.palette
3. Open Interface Builder.
4. From the menu, choose Tools > Palettes > Palette Preferences...
5. Click Add.
6. Navigate to /Developer/Palettes, choose EOPalette.palette, and click Open.
7. Close the Preferences window.
If you plan to use Interface Builder to create EOF applications, there is no simple workaround.
One approach is to avoid using the EOPalette functionality in Interface Builder and instead programmatically create connections, typically in your implementation of awakeFromNib.
Another approach is to do non-EOF work in Interface Builder by temporarily disabling EOPalette using the above steps, then re-enable it to perform EOF-specific tasks. During the time the palette is enabled, Interface Builder may quit each time you create a connection (or do anything which shows the Connections inspector). If you save your work immediately after making each connection, quit and reopen Interface Builder, you can use EOPalette, although you must reopen Interface Builder quite often.