[RESOLVED] Daily Builds and Public Releases > 2013.2076 Strange behavior when running on iOS device

OSX Mavericks

Xcode 5.0.2

Corona 2013.2076

I have a fully converted Graphics 2.0 app that runs perfectly when running in the Corona Simulator and when compiled for Android. However when compiled for iOS I get all sorts of strange behavior. (tested on iPad mini and iPod Touch 5 both on iOS 7.0.4)

Objects on-screen suddenly disappear, and then sometimes come back. A majority of objects are invisible, but are apparently still there as they accept touch events if you know where to tap.

The Storyboard sample compiles and runs fine on the same iOS devices.

I’m trying to isolate what’s going on, but I’m just wondering if anybody else has seen such behavior with their apps?

Hi Ingemar.  Engineering has asked if you can send them a project that’s doing this so they can try to track it down.

Thanks

Rob

Hi Rob,

I’m trying to investigate where the problem may be. I’m able to run the Corona samples and also my Graphics 2.0 waving flag contest entry without problems.

I know that I’ve been able to get iOS builds with this particular app to work before, but I’m not sure if that was before I upgraded to Mavericks or not. Even if I go back to earlier 2.0 builds now, I get the same issues on iOS…but the weird thing is the problems are on iOS only. Android and Corona Simulator all both OK.

I’m trying to create a sample project that exhibits the behavior I’m seeing, but so far it’s a no-go.

I’ll update this post once I have more info.

@Rob

I’m still trying to get a test project to behave this way. I get black screen issues, but not what I’m seeing with my actual app.

Here’s a Youtube video to show what’s happening.

http://youtu.be/XOG1WOOBJXI

Can you have your guys have a look at it. It might trigger some thoughts as to why it’s happening.

The app’s code is fully converted to Graphics 2.0 syntax (no V1 compatibility mode).

You can see in the video that the app is responsive when I touch where the “invisible” buttons are. It’s just that the display doesn’t update properly. You can also see that if I quit the app and then start it again, the screen refreshes and displays the “hidden” objects/buttons.

Just to emphasize: The is *not* the Corona Simulator. I used AirServer on my iMac to record the iPad screen.

The behavior seen above happens on any iOS device (iOS6 and 7).

The app runs perfectly fine on the Corona Simulator and on a Samsung Galaxy S1. Only iOS devices are affected with this weird behavior. 

An interesting thing is that the Corona Storyboard sample app runs fine on all my iOS devices. So it looks like it’s something specific with my code and Graphics 2.0 that triggers the problem. I *have* been able to run Graphics 2.0 builds of this particular app without problems on iOS before, however I think that was before I upgraded to Mavericks.

Another thing is that the weirdness only happens with Graphics 2.0. If I compile and run the same app (G1 branch of my code) with the last G1.0 build 1260, all is fine when running on iOS.

My Setup:

iMac 27", OSX Mavericks

Xcode 5.0.2

Corona SDK 2013.2076

I FOUND THE REASON!  :lol:

It was the setting antialias=true in config.lua that causes all sorts of problems! 

I changed it recently since it worked on smaller test projects I made. However setting it to true on larger projects wreaks havoc with the display on iOS (see video in previous post).

I really want it to work though. Do you guys at CoronaLabs think there’s something that can be done about it?

PS.

I had exactly the same behavior today while I was updating one of my business apps (mainly uses widgets), so it’s not particular to just one app.

As an example, take the Corona Sample ListView3 and set antialias=true in config.lua.

Compile for iOS and transfer to a device (I tried with an iPad mini and iPod Touch 5th generation).

The display will start with a black screen (at least it did for me), but try scrolling up/down anyway. You’ll see the list appear and disappear as you scroll.

@ingemar  Thanks - we will look into this further.

I had the same issue here using 10.7.5, Xcode 4.6.2, and 2013.2076. It affects both iOS7 and iOS6.1 devices I tested on.

@fosforus Antialiasing is now disabled and the issue resolved in the latest daily builds.

Thank you Bryan.

Hi Ingemar.  Engineering has asked if you can send them a project that’s doing this so they can try to track it down.

Thanks

Rob

Hi Rob,

I’m trying to investigate where the problem may be. I’m able to run the Corona samples and also my Graphics 2.0 waving flag contest entry without problems.

I know that I’ve been able to get iOS builds with this particular app to work before, but I’m not sure if that was before I upgraded to Mavericks or not. Even if I go back to earlier 2.0 builds now, I get the same issues on iOS…but the weird thing is the problems are on iOS only. Android and Corona Simulator all both OK.

I’m trying to create a sample project that exhibits the behavior I’m seeing, but so far it’s a no-go.

I’ll update this post once I have more info.

@Rob

I’m still trying to get a test project to behave this way. I get black screen issues, but not what I’m seeing with my actual app.

Here’s a Youtube video to show what’s happening.

http://youtu.be/XOG1WOOBJXI

Can you have your guys have a look at it. It might trigger some thoughts as to why it’s happening.

The app’s code is fully converted to Graphics 2.0 syntax (no V1 compatibility mode).

You can see in the video that the app is responsive when I touch where the “invisible” buttons are. It’s just that the display doesn’t update properly. You can also see that if I quit the app and then start it again, the screen refreshes and displays the “hidden” objects/buttons.

Just to emphasize: The is *not* the Corona Simulator. I used AirServer on my iMac to record the iPad screen.

The behavior seen above happens on any iOS device (iOS6 and 7).

The app runs perfectly fine on the Corona Simulator and on a Samsung Galaxy S1. Only iOS devices are affected with this weird behavior. 

An interesting thing is that the Corona Storyboard sample app runs fine on all my iOS devices. So it looks like it’s something specific with my code and Graphics 2.0 that triggers the problem. I *have* been able to run Graphics 2.0 builds of this particular app without problems on iOS before, however I think that was before I upgraded to Mavericks.

Another thing is that the weirdness only happens with Graphics 2.0. If I compile and run the same app (G1 branch of my code) with the last G1.0 build 1260, all is fine when running on iOS.

My Setup:

iMac 27", OSX Mavericks

Xcode 5.0.2

Corona SDK 2013.2076

I FOUND THE REASON!  :lol:

It was the setting antialias=true in config.lua that causes all sorts of problems! 

I changed it recently since it worked on smaller test projects I made. However setting it to true on larger projects wreaks havoc with the display on iOS (see video in previous post).

I really want it to work though. Do you guys at CoronaLabs think there’s something that can be done about it?

PS.

I had exactly the same behavior today while I was updating one of my business apps (mainly uses widgets), so it’s not particular to just one app.

As an example, take the Corona Sample ListView3 and set antialias=true in config.lua.

Compile for iOS and transfer to a device (I tried with an iPad mini and iPod Touch 5th generation).

The display will start with a black screen (at least it did for me), but try scrolling up/down anyway. You’ll see the list appear and disappear as you scroll.

@ingemar  Thanks - we will look into this further.

I had the same issue here using 10.7.5, Xcode 4.6.2, and 2013.2076. It affects both iOS7 and iOS6.1 devices I tested on.

@fosforus Antialiasing is now disabled and the issue resolved in the latest daily builds.

Thank you Bryan.