Question about the continuous builds...
Is anyone able to build properly off of them? I've cleared out my /build/iphone/ folder.. restarted Ti.. etc.. they build and push to the simulator fine, but crash immediately upon launch.
I have to go back to 1.4.1 to get it to run in the simulator.
And yeah… I have been switching the build in my project options..
anyway.. I was just curious…
6 Answers
-
Accepted Answer
I started with iOS SDK 4.2 and 1.5.0 and it did not work. I went back to iOS 3.2/4.1 and 1.5.0 and I can get clean builds that work and my current project runs fine. To me it looks like a problem running the beta iOS 4.2.
-
I've been having the same problem, glad it's not just me. Luckily 1.4.1 works for me too.
-
I just tried creating a new mobile project using 1.4.2 and copied my Resources folder into it and it works fine there. I guess deleting the build folder isn't always enough (though not sure why it wouldn't be).
Try making a new project and copy your Resources folder into that new project and see if that fixes things for you.
-
Just tried creating a /new/ project.. copied my /Resources/ folder over to it..
still a no go. Launches.. then crashes.. with this in the Ti. Console..
Detected an attempt to call a symbol in system libraries that is not present on the iPhone:
mmap$UNIX2003 called from function _Z20TCMalloc_SystemAllocmPmm in image ctz9d.
If you are encountering this problem running a simulator binary within gdb, make sure you 'set start-with-shell off' first. -
Are you guys working with the newest continuous builds? They've just upped it to 1.5.0 and I would get an exception when starting up my app with Android (a 1.4.2 build from about a week ago works fine). My bet is because of the recent refactor branch merges in the past few days, the dev builds are a bit unstable right now.
Robby
-
Hey Robby..
I just tried the 1.5. No go.. Even creating a new blank project in any of the builds fails for me..
however, if I go back to 1.4.1, then everything works as it should..
shrug