…Error upon first opening, after install on OSX Yosemite.
Please see the picture attached. Is anyone else getting this error? Any solution?
Hi @Joe C.,
It seems the picture didn’t get uploaded. Can you attach it by using the “More Reply Options” button, then using the attachment options below the message input box?
Thanks,
Brent
Oh. Sorry about that. I thought it got uploaded. I used the browse button then clicked post…I guess I forgot to click the “attach this file” button. :lol:
Thanks.
This is not an error, but a reminder. When we put out the last public release, Yosemite was still in beta and had a nasty bug that prevented Corona SDK from working correctly (and a bunch of other apps). We wanted to make sure that the public build would work, so we short-circuited the native.* API’s that were causing the problem. You can still build for device and have them work correctly, but until you either upgrade to Pro/Enterprise and can grab a later daily build (after Apple fixed it) or wait on the next public release (coming soon), you will have to just click that dialog away. If you’re using any native.* API’s you can only test them on device with that build.
Rob
Oh - I was sort of wondering if that was the case. I saw the “Apple bug #” part in the popup… That’s what made me think it was some sort of error, I guess. Anyway, thanks for the clearing that up for me. 
Hi @Joe C.,
It seems the picture didn’t get uploaded. Can you attach it by using the “More Reply Options” button, then using the attachment options below the message input box?
Thanks,
Brent
Oh. Sorry about that. I thought it got uploaded. I used the browse button then clicked post…I guess I forgot to click the “attach this file” button. :lol:
Thanks.
This is not an error, but a reminder. When we put out the last public release, Yosemite was still in beta and had a nasty bug that prevented Corona SDK from working correctly (and a bunch of other apps). We wanted to make sure that the public build would work, so we short-circuited the native.* API’s that were causing the problem. You can still build for device and have them work correctly, but until you either upgrade to Pro/Enterprise and can grab a later daily build (after Apple fixed it) or wait on the next public release (coming soon), you will have to just click that dialog away. If you’re using any native.* API’s you can only test them on device with that build.
Rob
Oh - I was sort of wondering if that was the case. I saw the “Apple bug #” part in the popup… That’s what made me think it was some sort of error, I guess. Anyway, thanks for the clearing that up for me.