Thanks. I searched on the terms in your response and ended up going with this solution (not the same, but it worked to get ant installed):
http://gauravstomar.blogspot.com/2011/09/installing-or-upgrading-ant-in-mac-osx.html
So, now ant works, but I’m seeing other issues. Sigh, sadly I’ve used Windows for so exclusively for the last two years that my ‘Linux/Unix/OS X’ kung fu is very weak.
Regardless, thanks again for the quick response!
What other issues are you having Ed?
I’m not sure if it’s related, but I cannot publish to the app store any longer no matter what I try. I persistently get :
Error ITMS-9000 :Invalid Code Signing entitlements. The entitlements in your app bundle signature do not match the ones that are contained in provisioning profile. According to the provisioning profile, the bundle contains a keyvalue that is not allowed “[BG2J43EA88.com.coronalabs.template]’
And I’ve tried everything. Details are in this thread: http://forums.coronalabs.com/topic/41367-comcoronalabstemplate-app-store-publishing-error/#entry215238
Richard
I seem to be having trouble with native.newTextBox. It is unresponsive in Mavericks on the Mac simulator. It works for one of my developers, who is using Lion. By “unresponsive”, I mean the callback is not getting called at all (as evidenced in a debugger) and I cannot edit text.
If I change to newTextField, it does work (even as multi-line, surprisingly), but that is not consistent with how it works on the device (or on my other developer’s machine), so it is not really a solution.
Is anyone else having this problem? It’s important to me because I use the Mac simulator for online demos for clients.
Hi @yo1,
Can you please specify a Corona build # for this, so we can investigate and attempt to replicate the issue?
Thanks,
Brent Sorrentino
Yes, my apologies, I should have mentioned the build number. This behavior occurred in 2013.1260 and 2013.1202. We have not moved to Graphics 2.0 yet.
The native.newTextBox issue on Mavericks is a known issue and was fixed in Graphics 2.0, 2076 release. It is not in any of the Graphics 1.0 builds.
See if this post can be helpful: http://forums.coronalabs.com/topic/42508-was-bundle-id-distorted-during-an-ios-build/
No, the problem is not related.
Looks like you are overriding he Bundle ID in build.settings and it doesn’t match what you have in your provisioning profile. It’s that or you App Name doesn’t match the provisioning profile. You can look at the info.plist file in the App bundle to see what the bundle ID is.
My first guess is you shouldn’t be using com.coronalabs in your bundle ID.
I didn’t want to start a whole new thread for this (since this is a Corona + Mavericks issue), but I’ve noticed the Corona Simulator has a delay sometimes before outputting content to the terminal. Not a big issue, but it can get rather frustrating. It never did this before I upgraded to Mavericks.
See if this post can be helpful: http://forums.coronalabs.com/topic/42508-was-bundle-id-distorted-during-an-ios-build/
No, the problem is not related.
Looks like you are overriding he Bundle ID in build.settings and it doesn’t match what you have in your provisioning profile. It’s that or you App Name doesn’t match the provisioning profile. You can look at the info.plist file in the App bundle to see what the bundle ID is.
My first guess is you shouldn’t be using com.coronalabs in your bundle ID.
I didn’t want to start a whole new thread for this (since this is a Corona + Mavericks issue), but I’ve noticed the Corona Simulator has a delay sometimes before outputting content to the terminal. Not a big issue, but it can get rather frustrating. It never did this before I upgraded to Mavericks.