Codea 1.3.1 is approved!

@Simeon I replicated the problem on my iPad 1. I had an almost clean install on it. All I had to do to get it crashing was to add a saveProjectInfo to a new project with the correct “Description” key, and run it once. I couldn’t get the crashing to stop, even by removing the project. In the end I removed Codea and reinstalled it. I’m dreading doing that on my fully loaded Codea on my iPad 2!

Here is the crash log from the iPad 1:

Incident Identifier: 77344EDA-0190-4BF2-A65C-9E007E70B907
CrashReporter Key: c762ea62d95b57b0c89f1d1556772875cb2b1eeb
Hardware Model: iPad1,1
Process: Codea [29138]
Path: /var/mobile/Applications/148E012B-A82F-4427-9B84-8DF14D7AB1E9/
Identifier: Codea
Version: ??? (???)
Code Type: ARM (Native)
Parent Process: launchd [1]

Date/Time: 2012-02-29 11:02:42.491 +0100
OS Version: iPhone OS 5.0.1 (9A405)
Report Version: 104

Exception Codes: KERN_INVALID_ADDRESS at 0xd004a39b
Crashed Thread: 0

Thread 0 name: Dispatch queue:
Thread 0 Crashed:
0 libobjc.A.dylib 0x35333fbc 0x35330000 + 16316
1 Codea 0x000f3206 0xf0000 + 12806
2 UIKit 0x34cb95ee 0x34c87000 + 206318
3 UIKit 0x34c8a95a 0x34c87000 + 14682
4 UIKit 0x34c8a3b8 0x34c87000 + 13240
5 UIKit 0x34c89d26 0x34c87000 + 11558
6 GraphicsServices 0x357b4dec 0x357b0000 + 19948
7 CoreFoundation 0x33bf154c 0x33b64000 + 578892
8 CoreFoundation 0x33bf14ee 0x33b64000 + 578798
9 CoreFoundation 0x33bf033c 0x33b64000 + 574268
10 CoreFoundation 0x33b734d6 0x33b64000 + 62678
11 CoreFoundation 0x33b7339e 0x33b64000 + 62366
12 GraphicsServices 0x357b3fc6 0x357b0000 + 16326
13 UIKit 0x34cb873c 0x34c87000 + 202556
14 Codea 0x000f2880 0xf0000 + 10368
15 Codea 0x000f2840 0xf0000 + 10304

Thank you Herwig — could you email me the actual crashlog file? simeon [at]

I think you have to go into Xcode and go under device manager to send a file though. Just trying to limit confusion.

@Simeon - Hey there, love the black theme. Great addition and very relaxing for the eyes :wink:
I’m here to whine though, as I’m having a few glitches on Codea 1.3.1 :stuck_out_tongue:

Basically, from time to time, when deleting selected code, the focus goes away (as in, no cursor left on the page), so If i press delete again it will jump to the end of the code, and start deleting whatever is there. It’s very very (very) frustrating hehe :slight_smile:

I’m having a few random crashes when switching tabs or stopping the execution of a program after using codea for a few hours. Restarting the app buys me a few more :stuck_out_tongue:

I had a few crashes when trying to buy the black theme/backgrounds, but it was fixed on restarting the device. However, I noticed that you cannot go back to the original background, or ever just not use any background at all.

Keep up the great work !



@Xavier I’ve had your deleting issue as well. I’ve triggered it when selecting and then deleting a method call parameter.

  • Double-tap to select parameter
  • Backspace once to delete parameter
  • Backspace again to delete space
  • Cursor jumps to the bottom of the document

Doesn’t happen every time in every file, but I have had it happen quite a lot.

So it’s not just me!

I assumed that I’d been accidentally tapping the code near the bottom and resolved not to be so thick-fingered in future.

hehe yeah that’s it ) I can’t remember the amount of “ends” i deleted :stuck_out_tongue:

I noticed it too when keeping the delete pressed to delete a bunch of stuff, and it suddenly started deleting stuff at the end of the file!

@Xavier do you mean the original blue background from 1.3 and earlier? If so then yes, I had to remove it as it doesn’t scale up to retina iPad resolution (1536x2048). The new backgrounds scale up to this resolution.

Thanks for letting me know about the delete bug. So you just hold the delete button to continuously delete, and at some point it will start deleting from the end? Will look into it. Thanks for the reproduction steps, @frosty.

I think some of the crashes could be due to the threaded autocomplete builder. I’m looking into this with @Dylan.

Ok - First I would like to comment that I had assumed that the new settings were going to be on the all app settings page (settings/apps area) so it took me a few minutes to find it. No issue, just confusion on my part.
Second, I bought the the dark theme to help support 2LL, and have found that it is so much easier to focus on the task at hand, and its so much easier onthe eyes, and easier to see different commands (variables, constants, etc.) that it makpe me much more productive. Thanks!


But not apparently a better speller…

Glad you like it, @jlslate! Thanks for the feedback. Hopefully we can make the dark theme come with a dark keyboard some time in the future as well.

FYI - A ton of the backgrounds don’t work and give me a blue background.

@Zoyt it sounds like they aren’t downloading — are you on a stable WiFi connection? Or perhaps the Two Lives Left server wasn’t responding, I’ll look into it.

Once they download they should save locally from that point on.

Oh… I didn’t know I needed Internet connection, but I understand why you did it due to hacking. Works now! Thanks!

Not at all due to hacking, @Zoyt. It’s actually to keep the size of Codea small (it’s about ~10 MB at the moment). Codea’s size blows up as follows when adding the backgrounds:

  • 40 MB with all iPad backgrounds
  • 81 MB with all iPad + iPad 3/Retina backgrounds

I didn’t want to waste all that size on just background images.

Oh… (Holly crap that’s large images!) I agree.

@Simeon - @Frosty - Not sure if this was mentioned before. Found the way to reproduce the bug 100% of the time.

Double tap to select a word, then delete.
If there is a space before, it will glitch and remove the cursor. If not, it works fine.

Double tapping “value” and pressing delete will glitch

t = { value=nil }

Double tapping “value” and pressing delete will work fine

t = {value=nil }

During testing Codea crashed twice, but this might not be linked



Thank you @Xavier, that’s very helpful! Will sort this out.

Just because I wanted to and I love Codea so much, I quickly created this little animation right here.
Hope you like it!

Thanks, @Zoyt!