Xcode Export Problem

General
1

I’ve always been able to muddle my way through exporting to Xcode enough to sideload from a Mac to an iPad but I’ve started getting errors that /Libs/libtools.a.gz and /Libs/libcodea.z.gz are not in gzip format. Also, Xcode cannot parse the debug map for /Debug-iphoneos/[AppName].app/[AppName] when trying to generate [AppName].app.sSMY and doesn’t find -lcodea in the same directory. I’ve tried attaching a screenshot but it doesn’t show in Preview so I’m not sure it’s there. I’m using Xcoce 8.1 and exporting through DropBox.

thanks

2

@DaveW I don’t know what that error means exactly, but exporting still works for me, and instead of Dropbox, I use google drive, that might work better

3

@DaveW Surprisingly, today I exported my project to xCode and I was getting a similar error and it was a problem with the Codea Runtime Library. I don’t know exactly how to fix it right now though, I’ll tell you when I get it to work

4

@DaveW Yeah image attachments aren’t working right now. Can you try uploading it to imgur and post a link so I can see exactly whats going on?

5

@John I’m not an imgur user but can start an account. Do you want the zipped Xcode file? I can also put it on OneDrive and post a link.

@CamelCoder I’ve thought of a couple things to try. I’m only at school on Mondays and that’s where the Mac with Xcode is.

Thanks

6

I tried two things with no success. I unzipped the file on both a PC and a Mac in case there was an issue with the unzipper.

I also created a new project, made no changes to it, exported, and got the list of errors so I’m confident it isn’t something in my code.

7

@DaveW it isn’t a problem with the code. Something may have changed in either XCode, or how the file is exported. I had a project from last week, same game that I was making, just not as much code. I opened that one and it worked perfectly. Then, I exported this more updated version of my game, and it doesn’t work. I’m pretty sure that means it’s a problem with the codea export process.

8

@CamelCoder My thinking is that neither Codea or Xcode has been updated recently. That’s why I was testing the unzipper. The only thing that has changed on the Mac in the past 30 days was iMovie. I believe there was a recent IOS update on my iPad but I can’t remember where that was in relation to this problem starting.

9

Same error on everything I try today.

gunzip: /Users/XXXX/Downloads/SiteManager-2/Libs/libtools.a.gz: not in gzip format
Command /bin/sh failed with exit code 1

10

@DaveW That’s the same error I got, I didn’t use an unzipper though, instead I just double tapped on the libtools.a.gz and it gave me another file like libtools.a.crgz. The error went away, but then a new error, linker error failed with exit code 1 started popping up and i couldn’t fix it

11

I suspect it’s a change in the back end code linked when you export a project. Any news, @John?

12

@Mark Do you mean there are remote files linked during export? I was wondering how Codea could have changed when there hasn’t been an update.

13

Here’s a temporary fix if you have a recent project file that worked. Copy over libcodea.a and libtools.a from the previous project, to the same directory where the .gz versions are found. Your project should compile without an issue.

14

@Mark I actually did that already, and then it still gave me an error, I might’ve done something wrong tho, I’ll try it again, but that’s probably your best bet right now. Thanks.

15

@CamelCoder don’t grab the .gz versions, just the .a versions.

16

@Mark Alas, I don’t have working versions of those files but school will be out until after New Years Day and I’ll hope for a fix by then. I updated Xcode today to no avail.

Thanks for the help.

17

I was also having the same issue. When I used a lib folder from last year, it builds fine. I have included a link to my lib folder from last year, just in case there is anyone else that does not have one:

https://drive.google.com/open?id=0BxJplyUFPhf-RDRkVnJZY0tjbEU

18

So …
Now that the build error is fixed, I also have the problem that the “assets” are not showing up once you build in Xcode. Take a brand new project in Codea, add some images from the built-in images, export, see the images in the assets folder but they do not show up in the simulator.

Anyone else have this issue or even better a solution?
Thanks

19

I’m now getting a message that Xcode is blocking a clear text HTML request for security reasons. My app is just coming up with a blank screen when there are no errors in my code

20

@bocaaust that’s Apple’s new transport security. If you google that error you’ll find the fix. You need to add a key to the apps info.plist allowing requests to any web site. At some point in the new year though, Apple is apparently going to start requiring that all apps use only HTTPS (rather than just HTTP).