I have a game that I built out only 3 levels, with checkpoints, to test out the play/look/etc. It has no sound It has no ads It barely has 2 atlases It crashes like a demolition derby on iPhone 6S 2 of the scenes have an abundance of spawning tails behind objects 1 scene has an abundance of logic Spoiler Alert: I deleted the scene with all the logic and it STILL crashes frequently on the device My next step is to remove the spawners and leave the 'logic' scene in... Edit: Update: Removed all the spawners and still had crashes. While I am on this witch hunt through my game, do you folks have any idea what ELSE could be causing the problem? If I can't figure it out tonight, I will probably just send to support@buildbox.com Thanks!
Look for empty placeholders in levels. They might be hidden somewhere and cause crashes. And usually if it crashes on a comp - it will crash on a device.
@defonten Thanks for your response! Can you clarify - what is an example of an empty placeholder? Thanks!
It's those little orange striped boxes that are sometimes left after you remove unused graphics in your scenes. I had a few of them and they kept crashing the game both on a comp and on a device. So check it first!
I just came to know after the week that .... it was admob which was crashing the game when internet was connected. you should definitely test it. Coz i just removed all ad parts and tested and it works. Now i have to figure out how to insert ads without making it crash.
@trudnai Thanks for the response! My game runs in simulator, but not on the device itself. Is there a way to get those error messages? I'm definitely 'Xcode challenged' I also haven't updated my OS (Yosemite) or Xcode (6.4) for some time due to fear of compatibility issues with BB1.3.6
Xcode 7 is now preferred for 1.3.6 and higher. You can keep both Xcode 6 and 7 installed at the same time. I would make a copy of Xcode 6.4 (you can rename the Icon to "Xcode 6.4" in a separate location) and update to Xcode 7 to see if that solves the issue. More than likely though both versions SHOULD be working though. If the crash persists you can open a support ticket.
Thanks @Andy - for the Xcode update info! In order to save me the 'initial ticket delay' of asking via email... - can you tell me what I should send? Is the buildbox file sufficient, or something else... Thanks!
Send a BBDOC, the crash report, and specific instructions on duplicating the crash (or as much info as you can).
Yes, while device ID connected hit run button in Xcode and you should see all messages just as it was running in the simulator.
@Andy Sorry for being a noob. This appeared in Xcode when the game crashed on the device. Is this the kind of into that is expected as a 'crash report' or am i getting the info from the wrong window. See below // // main.m // iphone // // Created by Walzer on 10-11-16. // Copyright 2010 Kayabit. All rights reserved. // #import <UIKit/UIKit.h> int main(int argc, char *argv[]) { NSAutoreleasePool * pool = [[NSAutoreleasePoolalloc] init]; int retVal = UIApplicationMain(argc, argv, nil, @"AppController"); Thread1: EXC_BAD_ACCESS (code=1, address=0x100000010) [pool release]; return retVal; }
Just start with a screenshot of your entire Xcode window if you are unsure what to do... then we can go from there.
Wrong window... Go to View -> Debug Area -> Show Debug Area and then you should see the logs in the All Output Window (I have just deliberately made BB to crash so you will see some crash info in there, and then highlighted the problem -- but for you the problem might be somewhere else...): Copy Paste the entire All Output window, if that is too long then better to zip it up and attach...
Hey is it possible you did what I did....update your Xcode recently and have to manually change "remove metadata from .png" to no....which by default is yes? This is done in Xcode. This helped a crash issue I had.
@blufology I have no idea what that means lol! I will give it a try however and let you know how it worked out! Thanks!