Restoring menu access to TextExpander snippets

I use SmileOnMyMac’s TextExpander program to generate snippets of text that I use frequently, such as my email address. I recently encountered a problem where I no longer had access to the TextExpander snippets via the drop-down menu that is normally available from the OS X menu bar.

While standard OS X functions such as AirPort Status and Volume control appeared in their normal locations on the menu bar, the ‘te’ icon had vanished completely.

The bug became noticeable immediately after I applied the latest TextExpander update (2.7.1). The change occurred even though the “Show TextExpander in menu bar” option was set as active in the TextExpander pane of System Preferences. Toggling this checkbox off and on failed to restore the menu to its previous state.

It was at this point that I contacted SmileOnMyMac support by email.

I received a reply from a support rep named Greg who asked to see the crash log (textexpanderd.crash.log) located in my home folder:


I emailed the crash log, of which a portion is included below:

Process: textexpanderd [9242]
Path: /Library/PreferencePanes/TextExpander.prefPane/
Identifier: com.smileonmymac.textexpander.daemon
Version: ??? (2.7.1)
Code Type: X86 (Native)
Parent Process: launchd [187]

Date/Time: 2009-11-17 09:33:30.754 -0800
OS Version: Mac OS X 10.5.8 (9L30)
Report Version: 6
Anonymous UUID: 9FF7868C-303E-40BB-A6CB-6C8EAC18CE0D

Exception Codes: KERN_INVALID_ADDRESS at 0x00000000c2692dcb
Crashed Thread: 7

Thread 0:
0 libSystem.B.dylib 0x948bfa24 szone_free + 1546
1 0x9592937e
__CFStrDeallocateMutableContents + 78
2 0x95929484 __CFStringDeallocate + 180
3 0x95913538 _CFRelease + 216
4 0x958e0729 __CFDictionaryDeallocate
+ 313
5 0x95913538 _CFRelease + 216
6 0x958a23cd __CFArrayReleaseValues +
7 0x95913538 _CFRelease + 216
8 0x958e0709 __CFDictionaryDeallocate
+ 281
9 0x95913538 _CFRelease + 216
10 …onmymac.textexpander.daemon 0x000075b5 -[SMTEDaemonController
reloadSettings:] + 98
11 …onmymac.textexpander.daemon 0x00008348 -[SMTEDaemonController
updateParametersForSettingsChange:] + 54
12 0x9207752c _nsnote_callback + 364
13 0x958f21bb
__CFXNotificationHandleMessage + 587
14 0x958f22ae
__CFXNotificationReceiveFromServer + 238
15 0x958ecff5 __CFMachPortPerform + 117
16 0x959116b8 CFRunLoopRunSpecific +
17 0x95911aa8 CFRunLoopRunInMode + 88
18 0x95af12ac
RunCurrentEventLoopInMode + 283
19 0x95af10c5 ReceiveNextEventCommon +
20 0x95af0f39
BlockUntilNextEventMatchingListInMode + 106
21 0x907206d5 _DPSNextEvent + 657
22 0x9071ff88 -[NSApplication
nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
23 0x90718f9f -[NSApplication run] + 795
24 0x906e61d8 NSApplicationMain + 574
25 …onmymac.textexpander.daemon 0x00002b8d main + 260
26 …onmymac.textexpander.daemon 0x00002412 _start + 216
27 …onmymac.textexpander.daemon 0x00002339 start + 41

Thread 1:
0 libSystem.B.dylib 0x948e99c6 kevent + 10
1 0x92077dfd -[NSThread main] + 45
2 0x920779a4 __NSThread__main__ + 308
3 libSystem.B.dylib 0x948ea155 _pthread_start + 321
4 libSystem.B.dylib 0x948ea012 thread_start + 34

Greg wrote back and said that TextExpander was crashing in an attempt to sync with MobileMe. He told me that I might be able to restore the menu by making a minor change to my MobileMe settings in System Preferences.

He said that if I wasn’t using MobileMe to sync my TextExpander snippets, that I should review the MobileMe Sync settings to ensure that none of categories on the list (e.g., Bookmarks and Calendars) are checked. Since I am a MobileMe subscriber, he said I should push the data from my Mac and replace what’s currently stored on MobileMe. From the MobileMe Sync menu, click Advanced, choose Reset Sync Data, then choose TextExpander as the type of data.

After performing these steps and rebooting my Mac, I restored access to my TextExpander snippets via the drop-down menu.


1 Comment

Filed under Third Party Software, Troubleshooting

One response to “Restoring menu access to TextExpander snippets

  1. Dear Author !
    You are mistaken. I can prove it. Write to me in PM, we will discuss.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.