LiveCode Forums.

Hmm. This workaround doesn't seem to work any more in 8.0.0 rc1.

If you apply the change to the script of of revSaveAsIOSStandalone and hit command-S you get

"Can't save stack revSaveAsIOSStandalone due to an error: can't open stack script file"

Also, I have the exact combination of resources (and only those) as described in Thierry's helpful update of his official versions for LC-Xcode-iOS:

LiveCode 8.0.0 RC1 – Xcode 7.3 -Mac OS 10.10/10.11 – iOS 9.3

...and I can't even test on the simulator any more. I just get an alert "iPhone simulator 9.2".

Any ideas? I have to say that at the moment this just seems to be one ****ing thing after another...

Cheers

@creepyTowel

Yep with LiveCode's new installation-by-dmg we can no longer mess with stuff in the app bundle (http://thread.gmane.org/gmane.comp.ide. ... ser/225061) - so until they bring out a new version that fixes the MachO bug you need to apply Panos' work-around each time you launch LiveCode - see comment 13 at http://quality.livecode.com/show_bug.cgi?id=17292

It actually works fine - onwards and upwards!

EDIT: that should read "you need to apply Panos' work-around each time you want to build for iOS"

I see the same error as CreepyTowel. However, as long as you apply the change, the save error doesn't seem to matter: an iOS standalone builds fine.

Cheers,

Adrian.

dave.kilroy said Yep with LiveCode's new installation-by-dmg we can no longer mess with stuff in the app bundle

So does this mean the hack to allow iOS apps to run in the background will also no longer work? Oh lordy...

My take on it is that we can hack things like we used to, but can't expect to save them

So in-memory hacks = good - attempting to save hacks to the app bundle = bad

Damn - I hadn't realised this. I guess there's no way now to do the iOS running in the background change at all now?

I suppose we need to start lobbying for the setting to be in Standalone settings ...

@Adrian - I don't know, maybe there is a super-hack that allows you to - Scott Rossi asked this very question in this thread http://runtime-revolution.278305.n4.nab ... 03345.html but I don't think got a reply - Peter Brett answered several times on that thread so may ask and see if he replies?

Hmmm. Thanks Dave. I think I'll try further messing with revsaveasiosstandalone to see if that at least works. (Though, of course, it's more hassle to do it every time a standalone is built).

Edit: I wonder if the new "experimental" Background Audio setting sets the exits on suspend to false? I'll give it a try in the next couple of days (unless anyone already has done this?)

@Adrian - yes changing the in-memory version of revsaveasiosstandalone (what I think of as Panos' work-around) works fine for me - just have set it when you need it as you say...

creepyTowel wrote:...

Also, I have the exact combination of resources (and only those) as described in Thierry's helpful update of his official versions for LC-Xcode-iOS:

LiveCode 8.0.0 RC1 – Xcode 7.3 -Mac OS 10.10/10.11 – iOS 9.3

...and I can't even test on the simulator any more. I just get an alert "iPhone simulator 9.2".

Any ideas? I have to say that at the moment this just seems to be one ****ing thing after another...

Cheers

Hi creepyTowel,

If you are on OS X 10.10, you have to use Xcode 7.2 with LC 8 RC-1, since Xcode 7.3 will not run on OS X 10.10.
If you are on OS X 10.11, you have to use Xcode 7.3.

So my *guess* is that you see this alert because you have tested your stack on iPhone sim 9.2 on OS X 10.10, then saved it, and then tried to test it on OS X 10.11. The stack remembers that it was tested on iPhone sim 9.2, and tries to find this option on OS X 10.11 (but this option is no longer available, so it shows an alert). If this is the case, make sure you explicitly select "iPhone sim 9.3" from the Development -> Test Target menu when you are on OS X 10.11 (and similarly, make sure you select "iPhone sim 9.2" when testing the same stack back on OS X 10.10). If this does not help, please submit a bug report

Now regarding modifying the app bundle, as Dave said, this is no longer possible because of the new dmg permissions. However, you should still make changes "in-memory", just they won't be saved.

@Adrian:
Yes, the new "experimental" Background Audio setting sets the exits on suspend to false, so ticking this checkbox should allow apps to run on the background.

Excellent - thanks Panos.

Thanks Panos

>> If this does not help, please submit a bug report

It didn't help, so I have -- bug 17429.

Cheers

Apologies. I was looking in the wrong place for the iOS version setting. It does indeed work as you described.

Sorry for wasting your time. I've cancelled the bug report.

Thanks

No worries, I am glad it worked

I have the same problem also Really disapointed for this.

Tried all the combinations,
LiveCode 7.3 with xCode 7.2
LiveCode8.0 with xCode 7.3

Erased and got the certificates again, not a change, xcode works, loads and app made there on my iPhone, but LiveCode is unable to sign any standalone.