avoiding iOS 7 crashes

GamePizza

What do we have to do to avoid Game Salad Apps from crashing on iOS 7. Is updating to latest GS Creator enough? 0.10.4.1?

slowcut

Why do you expect your Apps crashing on iOS7? All of my games work like hell on iOS7. No problem at all

jonmulcahy

yes i forget the exact release, but there was a special release shortly after iOS7 came out that addressed legacy apps from crashing. upgrading to the latest will take care of it.

GamePizza

so we need to update with the latest release all Apps that crash?

jonmulcahy

yes

GamePizza

Ok, thanks for the help!

GamePizza

I updated to GS Creator 0.10.4.1 beta and the apps are still crashing. Any other suggestions?

slowcut

@GamePizza
Maybe it has nothing to do with GS or iOS7. Maybe it's your code.
I never had any crashes with iOS 7.

When does your app crashes?
Can you reproduce the crash?
Have you run your app in xCode instruments and watched its performance?

Mayhemmmarty

@GamePizza check out youtube Very good video on using Xcode instruments. Many of us rookies didn't know about Xcode instruments !!! That includes me. Very essential tool to check your app memory consumption.

GamePizza

The apps were working fine before iOS 7, but now are crashing. The crashes will usually occur on scene 1 going to scene 2. It seems Apps that were updated with GS 0.10.4.1 will crash less, but still crash. You may get 10 or 11 scenes in and then it will crash. Or if there is only one scene, it will work for a while, but then may experience a random crash at some point in time. I never had crashes like this before iOS 7. Not quite sure how to fix the problem.

Mayhemmmarty

I had a similar issue where my app would crash after "x" number of scenes. It was caused by sound files that were missing. For example my game called on a sound to be played when something happened... The sound file was missing or corrupt. Once I corrected the sound issue my game stopped crashing.

GamePizza

The sound files are definitely there since I can hear them playing. On one iPad App for example, it tends to crash on scene 1 or 2. But occasionally I can get to scene 6 before it will crash.

The_Gamesalad_Guru

Are you using tables? One of the other issues was you can no longer look to a table row 0. So let's say you have a expression in a change attribute and you use an attribute to determine the row or colum. If that attribute starts as a zero you need to add a condition to the rule that governs any of those pieces of code. To the rule you would add (when variable x > 0) this way the change attribute or other condition that uses an attribute to check for a row or colum won't be active until that variable is greater than 0. Since in reality there is no row zero when that code is scanned it returns a null error and causes a crash. The new engine they put in creator is now more exacting that before and will pick up errors the previous ones let slip by such as addressing a variable wrong like changing an integer by mistake with true or false by mistake et..