MacOSX 10.10 and Corona 2014.2189. Can't open projects

Hi,

Im recently donwload last OSX Version 10.10 (Yosemite) but I cant even open projects. When do you will program a fix for that.

Thanks in advance!

We’ve determined that there’s an issue with the MacOSX 10.10 beta which is affecting our OpenGL views and we can reproduce it using an Apple sample.

We’ve filed a bug at https://bugreport.apple.com but it would help if you could too as the squeaky wheel gets the grease.

The details are as follows:

Title:
Layer-backed views do not render in OS X 10.10 (Yosemite). [NSOpenGLView prepareOpenGL] also not called.

Summary:
The Apple sample LayerBackedOpenGLView does not render on 10.10.

Steps to Reproduce:
0. Download Apple’s LayerBackedOpenGLView sample: https://developer.apple.com/library/mac/samplecode/LayerBackedOpenGLView/Introduction/Intro.html

  1. Choose an OS:
    1a. For OS X 10.8.4/XCode 5.0, go directly to Step 2
    1b. For OS X 10.10-beta/Xcode6-beta, you will need to add the OpenGL headers to Texture.m to avoid compile errors.
  2. Build the sample.
  3. Run the binary.

Expected Results:

  1. Observe that the spinning globe appears.
  2. AppKit calls [NSOpenGLView prepareOpenGL]

Actual Results:

  1. On OS X 10.10 Beta, spinning globe does *not* appear.
  2. [NSOpenGLView prepareOpenGL] does *not* get called.

Version:
OS X 10.10 (14A238x)

I submitted it too late :frowning:

We’ll build a makeshift shelter until help arrives…

We’ve determined that there’s an issue with the MacOSX 10.10 beta which is affecting our OpenGL views and we can reproduce it using an Apple sample.

We’ve filed a bug at https://bugreport.apple.com but it would help if you could too as the squeaky wheel gets the grease.

The details are as follows:

Title:
Layer-backed views do not render in OS X 10.10 (Yosemite). [NSOpenGLView prepareOpenGL] also not called.

Summary:
The Apple sample LayerBackedOpenGLView does not render on 10.10.

Steps to Reproduce:
0. Download Apple’s LayerBackedOpenGLView sample: https://developer.apple.com/library/mac/samplecode/LayerBackedOpenGLView/Introduction/Intro.html

  1. Choose an OS:
    1a. For OS X 10.8.4/XCode 5.0, go directly to Step 2
    1b. For OS X 10.10-beta/Xcode6-beta, you will need to add the OpenGL headers to Texture.m to avoid compile errors.
  2. Build the sample.
  3. Run the binary.

Expected Results:

  1. Observe that the spinning globe appears.
  2. AppKit calls [NSOpenGLView prepareOpenGL]

Actual Results:

  1. On OS X 10.10 Beta, spinning globe does *not* appear.
  2. [NSOpenGLView prepareOpenGL] does *not* get called.

Version:
OS X 10.10 (14A238x)

I submitted it too late :frowning:

We’ll build a makeshift shelter until help arrives…

Any progress on corona sdk and yosemite? we’re now a couple of versions into the beta…

As of the last developer preview of Yosemite, the bug is still present.  However, we have put in a work around, which should be in the  latest public build and daily builds afterwards that allows Corona SDK to run on Yosemite, but with the penalty that native.* objects that did work (i.e. native.newTextField, native.newTextBox) will not work.

We are continuing to work with Apple to get this issue resolved.

Rob

And a DP7 has just been released. Since I’m not using it, could anyone check if issues with coronaSDK have been resolved? I really want to test out 10.10, but can’t since CoronaSDK can’t do it’s magic :frowning:

Am using 10.10 now, Rob’s answer was good enough for me as I don’t use the native controls at the moment. So 10.10 works and my game in progress works as well on the simulator as on ios and android devices.

I’m sure engineering is staying on top of this issue, but I’ve not heard any new news about the latest beta. 

But the only thing not working are native.* objects in the simulator.  Most of them didn’t do anything there anyway (other than newTextField and newTextBox). 

Rob

Any progress on corona sdk and yosemite? we’re now a couple of versions into the beta…

As of the last developer preview of Yosemite, the bug is still present.  However, we have put in a work around, which should be in the  latest public build and daily builds afterwards that allows Corona SDK to run on Yosemite, but with the penalty that native.* objects that did work (i.e. native.newTextField, native.newTextBox) will not work.

We are continuing to work with Apple to get this issue resolved.

Rob

And a DP7 has just been released. Since I’m not using it, could anyone check if issues with coronaSDK have been resolved? I really want to test out 10.10, but can’t since CoronaSDK can’t do it’s magic :frowning:

Am using 10.10 now, Rob’s answer was good enough for me as I don’t use the native controls at the moment. So 10.10 works and my game in progress works as well on the simulator as on ios and android devices.

I’m sure engineering is staying on top of this issue, but I’ve not heard any new news about the latest beta. 

But the only thing not working are native.* objects in the simulator.  Most of them didn’t do anything there anyway (other than newTextField and newTextBox). 

Rob

When I launch Corona Composer, it used to ask me which scene i want opened. But now its giving me a pop-up about the native.* openGL bug and opens nothing (at least a pop up for opening my scene ?)

But my scenes do get opened from the Composer “open” icon :slight_smile:

What version of Corona SDK are you using?  Daily Builds since 2437 work fine with OS X 10.10

I can’t open Corona up either right now. I just upgraded to Yosemite 10.10 and when I try launch the latest daily of Corona (and the last 5 dailys as well) it says I need JAVA SE 6 Runtime in order to launch Corona, and then it closes. It refuses to open the SDK at all.

Yosemite uninstalls Java 6 when you install it.  You need to get it reinstalled.  When you get the dialog there should be  “More Info” link you can click on that will take you to a place to install it.  Engineering is looking at ways to improve that experience, but we don’t have a solution yet other than re-installing Java 6.  You likely had to do this once upon a time as well.

Rob

Perry , 

I am using 2393 build (starter version). No functional impact as such (other than native element issue). Just that it used to prompt to open a “ccscene” right away. 

regards,

Joel