Weird, I can’t do device builds in mine 
Take note though that if you have excluded some important folder in your Time Machine, you won’t be able to do a full restore… as with my set up.
@bfintal: I see that you appear to be a starter user - are you using the last public build? I’m using the latest daily, which might account for our different experiences (i.e. making a device build). Does the simulator open up at all for you? Can you attempt to open up a project, or does it just crash right away?
@schroederapps, yeah didn’t reach the grandfather time limit to renew lol!
When I open it, it doesn’t show anything, no welcome screen. When you open a project, it partially shows a zoomed in simulator then crashes.
I made the mistake of updating my primary iPhone to iOS 8… Now when testing my published corona apps all of them flash black screens about three times a second. Does anyone know how to a) make my apps compatible or b) revert my iPhone back?
I tried erasing everything off of my phone, but that did not work.
@schroederapps Do you know when it might be released?
And how can I create device builds? When I open the app main.lua file it automatically opens the simulator and crashes.
Hi KarioKong1,
I’ve also seen this “flashing” behavior on-device in one of my currently-in-production apps, but it only seems to happen on launch, and only for a few seconds. My previously-published apps are not showing this behavior on my iOS 8 iPhone (iPhone 5S/Verizon, in case that helps - Apple uses different firmwares for each phone model & carrier). Especially if you are seeing this for published apps, you should definitely file a bug report with Apple. It’s definitely a regression bug that will likely get squashed in a future beta release…that’s what the beta period is for, after all! But it won’t get squashed if people don’t report it, so be sure to file a bug. At least now we’ve got the Bug Reporter app so we can send a report from the device.
As for downgrading, I think you are probably out of luck. But you could always try downloading an iOS 7 update file from http://www.jailbreakeye.com/download-ipad-ios-firmwares, which has links to official Apple firmware DMGs. Then try to restore from that file in iTunes…but again, I don’t anticipate that this will work. Apple’s official stance is that once you’re in the beta, you’re committed.
As for creating device builds, I am beginning to think I’m just plain lucky, because others have reported that they aren’t able to. I managed to make it work by opening up a project (command-O) and once it opens, even though the simulator window is blank, hit command-B and tell it to create a build. Like I said, it’s still crash-prone, but I managed to get one of projects to build, and it did work on-device. Your mileage may vary.
I can’t say when Corona Labs will get around to making a build that works in Yosemite, but don’t hold your breath. It’s a barely-in-beta OS, and CL can’t devote too much time to checking compatibility with a not-yet-released operating system. My guess is that we’re probably a month or two away from them really devoting much energy towards Yosemite compatibility. And any fixes on the CL side of things will almost certainly be available exclusively in daily builds, at least for a while (it looks like you are a starter edition user?). Hopefully whatever screwed up the compatibility will get fixed in a future beta revision.
We wont be supporting Yosemite for production use until it is officially released (but you knew that).
However, having said that, I can confirm that the Mac Simulator mostly doesn’t work on Yosemite (a couple of other third party apps I tried didn’t either). The fact that one can do device builds actually implies that the Java part *is* working.
I’ll look into the issues but, if history is any guide, the WWDC betas of MacOSX are pretty flaky (the first beta of Mavericks was almost unusable) but new ones come out fairly quickly so it’s not worth spending much effort chasing issues at this stage.
While I’m here, a couple of tips on playing with OS betas …
On the Mac, only ever install betas on an external hard disk ($30 and up at Amazon), on an SD card (ditto), or for the adventurous, on a separate partition of your main disk (I’ve even done it on a TimeMachine backup disk while it was still in use as a TM backup but I wouldn’t recommend that).
On iOS, despite what Apple says, downgrading isn’t very hard (I’ve done it) you just need to get the device into “recovery mode” though you will lose all the data that is only on the device (your mileage may vary, I’m not recommending you install beta OSes on any device you can’t afford to brick). There’s a good guide here.
I run 10.9.3 and would like to install xCode 6 only. Now I have read it can co-exist with xCode 5 on my machine and they both work but I still want to be able to use Corona and build apps the store using xCode 5.
Will this be ok and has anyone tried it ?
Dave
It “should”. Usually Xcode previews are separate apps and your existing Xcode stays in place. However having not tried it, I won’t give this a 100% thumbs up.
Rob
I can confirm that Xcode 5 and Xcode 6 beta can exist side-by-side in Mavericks. If you were compiling a native app for release then it’d be very easy to compile using Xcode 5. But since Corona handles the build process for us, there is definitely room for confusion to creep in. At the very least, when it comes time to build for distro, you could uninstall Xcode 6 to ensure you build against Xcode 5. I’d venture a guess that there’s not much potential for real harm by installing Xcode 6 on Mavericks - it might make extra work for you, but it shouldn’t “break” anything. Worst-case scenario, you may have to uninstall all Xcode versions and reinstall 5, but that’s unlikely.
@Perry: thanks for chiming in! Curious about your experience downgrading from iOS betas: did you try it during the iOS 7 beta? I only ask because I’m familiar with DFUing phones to restore in difficult cases, and I successfully went from iOS6 beta to iOS5 with that method back in 2012, but when I tried to downgrade from iOS7 beta to iOS6 in 2013, unless my memory fails me, it didn’t work, even in DFU mode. Apple seems to have really cracked down on what iOS versions it will digitally sign these days…did you know that you can’t upgrade or downgrade any iOS devices to anything earlier than 7.1 anymore? Not without some fancy hacky workarounds, at least. Only today I had a coworker ask me to upgrade an old disused iPad 2 from iOS 4 to iOS6 (he wanted a newer version but hates the “flat design” look), and even though I had the firmware file, the upgrade failed because it couldn’t be digitally signed. Mind you, this was a simple, non-jailbreak upgrade, but Apple still wouldn’t allow it. That’s why I suspect they may make it very tough to downgrade.
If you want or need to know precisely what version of iOS or Xcode your app is built for you can find it in the app’s Info.plist.
Run a command like:
defaults read ~/Desktop/MyApp.app/Info.plist
(note that you have to give the full path to the app, a relative path wont do).
Look for entries like DTSDKName and DTXcodeBuild to confirm you’re building for what you intended to.
That’s exactly what I did. I tried the first beta and after it dropped a couple of calls on me I decided I needed to go back to iOS 6 (and thoroughly kicked myself for putting a beta on a device I needed to get work done).
The thing I think that trips up most people is that they decide they want to go back to what they had before rather than what is currently allowed which, as you mention, isn’t possible unless they were fully up to date. People also get themselves into trouble by accidentally (or deliberately) backing up the device with the beta on it and, since they have to erase all their data to downgrade, can’t get back to where they were (because backups generally wont restore to an earlier OS version). My approach is to accept all the defaults iTunes offers when trying to restore in “recovery mode” and it’s always worked for me (tempting fate there, I know) both for downgrades and cases where the OS decides the device is “full” despite there only being enough data on it to fill 50% of available space.
Really, the best advice is to not put yourself in the position of needing to downgrade by installing the beta on a device that you can do without until whatever issue you run up against is fixed in a beta refresh. And if you don’t have such a device, just read about the beta online and smile when you hear reports of beta testing horrors 
When you have 2 versions of Xcode installed on your system just make sure that xcode-select --print-path points to the Xcode version you want to use. Even though Corona compiles on their build servers the signing takes place with your Xcode locally, so you should ensure that the proper Xcode version is active.
You can change where it points with xcode-select --switch <path>
Only today I had a coworker ask me to upgrade an old disused iPad 2 from iOS 4 to iOS6 (he wanted a newer version but hates the “flat design” look), and even though I had the firmware file, the upgrade failed because it couldn’t be digitally signed.
This is a practice that Apple has had it place for a long time. After a new major version is released, soon after, they stop signing the old one making it impossible to even *upgrade* a device to the older version of iOS. Unfortunately, Jailbreak is the only answer in these cases.
Same problem here. I updated to Yosemite OS X 10.10 beta and my iPhone 5S to iOS 8 beta.
I got the same results as others here. Simulator loads, empty Welcome window, and simulator has gray background and if you click it then it throws an exception.
It looks like it’s just the JAVA that’s causing problems for the simulator. I installed the old Java 6 Runtime as instructed, which allowed the simulator to run.
My iOS apps still work great on the new iOS 8 beta (built while i still have Mavericks and Xcode 5).
It looks like it should be relatively painless for Corona Labs to fix this minor problem. Otherwise, I’m DOA. Kinda suck as i’m developing 2 games at the same time.
Update: when the simulator is up, putting it in Sleep mode actually works and draws the orange animation.
Take it out of sleep and it explodes.
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. This is not uncommon with OS betas and it’s good to catch it early. You can do builds so long as you don’t click in a Simulator window (the app or the Welcome window) though there’s not a lot of point to that.
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:
(Duplicate of rdar:17202371) 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
- 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. - Build the sample.
- Run the binary.
Expected Results:
- Observe that the spinning globe appears.
- AppKit calls [NSOpenGLView prepareOpenGL]
Actual Results:
- On OS X 10.10 Beta, spinning globe does *not* appear.
- [NSOpenGLView prepareOpenGL] does *not* get called.
Version:
OS X 10.10 (14A238x)
Submitted a bug report to Apple Hopefully beta 2 fixed this