XMail.osax Error On Corona Terminal Startup

When I start up the Corona Terminal on MacBook Pro, OS X 10.7.5 I get the following error reported in the terminal:

Corona Simulator[1852:f03] Error loading /Library/ScriptingAdditions/XMail.osax/Contents/MacOS/XMail:  dlopen(/Library/ScriptingAdditions/XMail.osax/Contents/MacOS/XMail, 262): no suitable image found.  Did find:

    /Library/ScriptingAdditions/XMail.osax/Contents/MacOS/XMail: no matching architecture in universal wrapper

Corona Simulator: OpenScripting.framework - scripting addition “/Library/ScriptingAdditions/XMail.osax” declares no loadable handlers.

How can I correct this problem?

Thanks.

That’s odd, I’ve never seen that before.  Let me ask the engineers!

Thanks.

Apparently, at some point in the past someone installed XMail https://code.google.com/p/xmail-osax/ on your machine but it no longer functions correctly.

I believe all you have to do to remove it is to delete the file (and probably restart after doing that):

/Library/ScriptingAdditions/XMail.osax

I’d be surprised if this was affecting only Corona SDK.

Thanks. In fact that did the trick. As far as I can tell, nothing else was affected.

What version of the Corona SDK are you using?

Corona version says:  2013.1076 (2013.43)

Hope this helps.

I can’t reproduce the issue at all so I’m glad my fix worked :slight_smile:

Your advice strikes me as being a modern variation of what our cavemen forefathers used to say, “throw something at it, and see what happens.” :-) 

Well, if by “modern” you mean “google it, choose the least crazy sounding solution, try and see what happens” then, yeah :slight_smile:

That’s odd, I’ve never seen that before.  Let me ask the engineers!

Thanks.

Apparently, at some point in the past someone installed XMail https://code.google.com/p/xmail-osax/ on your machine but it no longer functions correctly.

I believe all you have to do to remove it is to delete the file (and probably restart after doing that):

/Library/ScriptingAdditions/XMail.osax

I’d be surprised if this was affecting only Corona SDK.

Thanks. In fact that did the trick. As far as I can tell, nothing else was affected.

What version of the Corona SDK are you using?

Corona version says:  2013.1076 (2013.43)

Hope this helps.

I can’t reproduce the issue at all so I’m glad my fix worked :slight_smile:

Your advice strikes me as being a modern variation of what our cavemen forefathers used to say, “throw something at it, and see what happens.” :-) 

Well, if by “modern” you mean “google it, choose the least crazy sounding solution, try and see what happens” then, yeah :slight_smile: