Using Corona with new release of OS X Yosemite.

Solar2D General Questions/Discussion
#21

I am having an issue with Yosemite and Native textfields. I am on daily build  2468 and on my first screen I have a native.textfield and now get an error:

“attempt to index upvalue ‘searchTxt’ (a string value)”

searchTxt looks like this in my code:

searchTxt = native.newTextField( searchBkg.x-searchBkg.width/2+135, searchBkg.y, 230, tHeight,textListener ) searchTxt.font = native.newFont( native.systemFont, inputFontSize ) searchTxt:setTextColor(1,1,1) searchTxt.hasBackground = false searchTxt.placeholder = "Search..."

so its not a string at all. Code and everything worked fine prior to upgrading to Yosemite, and I have read about the OpenGL bug but that was taken care of after daily build 2437. Can someone else confirm/not confirm that native.newTextField is working with Yosemite and a daily build after 2437?

*UPDATE: All my apps that contain native.newTextField all crash with the same error. So there seems to definitely be something wrong with native display objects still

#22

@murrough.obrian, I’m not 100% sure I follow.  We have native things turned off for the simulator in the public build, but you can still test on device.   As far as to when we will get out a new public build, well we shoot for every 3-4 months.  We put out the last public build on 8/5.  It’s not 10/19, so its a little over 2 months old.  Yes, Apple has put out new stuff, but it’s been buggy, so buggy they put out 8.1 within a month of releasing 8.0.  We’ve been working to make sure Corona SDK is stable with the new operating system and now we have another new one to make sure we are good with.  I’m sure we will work towards a public build sooner than later.  But we have to make it solid.

If native textfields are important to you, then you probably should stay with Mavericks for now. 

Rob

#23

I’m not sure if this is yosemite related, but since updating I’ve had problems with audio in the simulator that I hadn’t had before

The sound stutters (loops) for sounds that shouldn’t loop and I get this error

17dTesting Error with clearing buffer from source: Invalid OperationWarning: audio error: Failed to clear buffer from source: Invalid Operation
Warning: audio error: Could not bind data to source: Invalid Operation

This is CoronaSDK Version 2014.2454 (2014.10.6)

Attempts at playing new sounds returns a sound channel of 0

I’m testing on iOS and do not seem to be getting this issue, just in the simulator.  I’ve run old builds of my game and the issue comes up. 

#24

@Ernest

I haven’t seen this issue myself. I use M4A (AAC) for background audio and WAV for short sound effects.

I use Audacity to convert my files to their respective encodings.

What audio encoding do you use?

#25

I use audacity as well variable 80-120kbps .mp3  (11025-22050 HZ) mono

I never had any problems with this before, although every rare once in a while the sound will stutter or loop but it’s incredibly rare.   

#26

Corona Guys need to do a blog post on the current state of Yosemite. When I first read this thread I thought it was ok to upgrade, turns out it isn’t and I need to send my client a new build. Looks like I am reverting back to Mavericks until we hear some new news.

#27

@chevol

What are the issues you’re seeing?

#28

I am having issues with Native textfields, here was my post earlier in this thread:

#29

Engineering will need a bug report.  Have you tried running either of the two sample apps to see if they have the issue?   When you file a bug report you will need a minimal project that has this issue.   Please make sure to include your config.lua and build.settings as well as any assets needed to compile the demo project.  Compress it into a .zip archive (please no other format) and use the “Report a bug” link at the top.  If one of our sample projects has that issue, then you can just zip it up instead.

You will get an email with your bug ID in it.  Please post that back here for future reference.

Rob

#30

Hey Rob, thanks for the post. I have found the issue…

Creating a native textfield like this throws an error:

searchTxt = native.newTextField( 0, 0, 230, 30,textListener )

But separating the listener like this runs fine:

searchTxt = native.newTextField( 0, 0, 230, 30 ) searchTxt:addEventListener( "userInput", textListener )

*NOTE: I just saw that using the listener argument like that is deprecated, so the issue was all me

#31

Great. Glad you solved it.

Rob

#32

Since Yosemite update the native textfields are invisible in the simulator. I can click them and they got focus but no border or background is drawn. Is this a known problem or maybe only a local problem on my machine?

Using Corona build 2014.2393a

#33

Hi Raye.  When we produced the public build you are using (2393a), there was an OpenGL bug in the Yosemite beta at that time that we had to put a work around in to allow Corona SDK to run on the beta version of Yosemite.  We hoped (and they did) that Apple would eventually fix it, but because our public builds have to be good for a few months, we had to disable the native.* api’s in the Corona simulator in that build.  They still work on the device.  Now that Apple has fixed that bug, we’ve removed it in a recent daily build (which is available to Pro and Enterprise subscribers).   When we put out a new public build, the native.* API’s will start working again for Starter and Basic accounts.

So yes, this is a known limitation of Yosemite and 2393a.

Rob

#34

Ok, thank you for the info, Rob.

#35

@Rob

any news on new public build release ?

Is the iOS simulator issue for Xcode 6 already fixed in actual daily build ?

I need to generate iPhone6 and 6plus screenshots and iOS simulator use would be very welcome .

Thank you for any info.

st

#36

We have identified the bugs that have to be fixed and engineering is working on closing them.  We have an expected code freeze date.  But too many variable still exist to give out these dates.  Once we are past the code freeze, then we start testing the product heavily.  If we see any regression bugs, we have to fix them which resets testing back to ground zero. 

Yes, the Xcode issues are fixed (well there is still a weird time out issue when you first launch it, but that seems to be Xcode related).

Rob

#37

mmm…thanks for your answer.

:rolleyes: I will try again to get a time frame in the (very) next future.

st

#38

Hi, I upgraded to Yosimite last night and encountered an error with Java that required me to redownload Java SE 6 from Apple. Has anybody else experience this error?

#39

Hi Matthew,

yes I got that same error.

The Corona simulator stopped working.

I then downgraded to Java SE 6 and it resumed proper functions.

IMHO: life could be easier, sometimes. But most of times it’s worse than this !

Cheers

st

#40

@Matthew

I’m pretty sure that every time you upgrade OSX it wipes your Java install, so you always need to reinstall it.