Can't share created instances about chrome-ssb-osx

[lhl]

Nope. That's new to me. I'll run a check to see if recent merges have
caused regressions...

I just tried to share an instance of an SSB I created with a colleague.
Both of us are running up-to-date versions of Mountain Lion. When he tries
to open the app, he gets the following error dialog:

[image: 402256745229]https://f.cloud.github.com/assets/19457/1239421/32417626-29fa-11e3-93aa-1d806aa58dba.png

Is this expected behavior?

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/19
.

[lhl]

FYI I just checked this out, didn't have any problems launching w/ the latest code.

2 things you can do:

1. Open Console.app and see if you can capture/paste up what shows up when you launch

2. go in the Terminal and echo [YourSSB].app/Contents/MacOS/[YourSSB] - this is the shell script that is generated that is the heart of your app. You want to specifically see exec '/[Location of]/Google Chrome.app/Contents/MacOS/Google Chrome' and try running that directly and see what that says.

What version of Chrome are you running?

[lhl]

No response? Closing. Reopen if you have an update.

[jeffpoulton]

I totally dropped the ball. I started digging into the questions you asked,
but got distracted and never finished. My apologies, Leonard.

On Sun, Oct 20, 2013 at 5:37 PM, Leonard [email protected] wrote:

No response? Closing. Reopen if you have an update.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/19#issuecomment-26686018
.

Jeff Poulton
Founder & Managing Partner
435.215.1769 | [email protected]

[lhl]

No worries, just re-open if this is still a problem/priority and you are ready to revisit, but I couldn't replicate it so I closed it for now - there's no reason anything should be trying to use the classic environment, so it is quite puzzling.