Hi Chris, You can apply the workaround described here until 8.1.1 rc1 is released:
https://github.com/livecode/livecode/pull/4530/files (Make sure you include the line [get shell("xattr -cr" && quote & pAppBundle & quote)] as well) Best, Panos -- On Tue, Sep 20, 2016 at 9:55 AM, panagiotis merakos < panos.mera...@livecode.com> wrote: > Hi Chris, > > I just tested with your stack in LC 8.1.1 RC-1 (not public) and I confirm > I still get the "resource fork, Finder information, or similar detritus > not allowed” error when building an iOS standalone. After further > investigation, it seems this is caused *only* if you add the "Internet" or > "tsNet" inclusion in the "Inclusions" pane. I will change the status of > http://quality.livecode.com/show_bug.cgi?id=18135 back to IN_PROGRESS. > > Best, > Panos > -- > > On Mon, Sep 19, 2016 at 10:54 PM, panagiotis merakos < > panos.mera...@livecode.com> wrote: > >> You are welcome. Just the stack should be enough to replicate this, but I >> would suggest you send everything, just in case. >> >> Best, >> Panos >> -- >> On 19 Sep 2016 22:46, "Chris Sheffield" <cs_livec...@icloud.com> wrote: >> >>> It appears to be just this stack. After creating a new stack, and even >>> setting it to copy the same files, the build works just fine. >>> >>> Yes, I do have png files, quite a lot of them, inside an images folder >>> that is included in the Copy Files section. Like I said though, I included >>> that folder even with the new stack, and everything worked fine. This >>> particular app also makes use of a few mergExt externals. I have updated >>> those to the latest versions included with LC 8.1. Again, even including >>> all of those in the new simple stack I created, everything builds fine. >>> >>> So I will plan on sending you my stack. Do you need all the included >>> files, or just the stack itself? I just tried removing all my Copy Files >>> entries, and the build still fails, so I don’t think it’s related to any of >>> those, but I’m happy to include them in a zip archive if you’d like. >>> >>> Thanks again. >>> >>> >>> > On Sep 19, 2016, at 2:28 PM, panagiotis merakos <merak...@gmail.com> >>> wrote: >>> > >>> > Hi Chris, >>> > >>> > Hmm, that's weird, it should work. The first part of the error >>> > (—resource-rules blah blah) is just a warning. The codesign fails >>> because >>> > of the "resource fork, Finder information, or similar detritus not >>> allowed” >>> > part. >>> > >>> > The command [get shell("xattr -cr" && quote & pAppBundle & quote)] >>> should >>> > recursively clear those "extended attributes" in the app bundle. I am >>> not >>> > on a MacOS Sierra to test now, but what happens if you try to create a >>> > different ios standalone (after having applied this workaround)? >>> > >>> > Moreover, does your app contain any .png files in the "Copy Files" >>> section? >>> > >>> > If you see this error *only* when building an ios standalone *for this >>> > particular app*, I suggest attaching your sample stack to bug 18135 (or >>> > send it privately to panos.mera...@livecode.com if it is >>> confidential), so >>> > as we ensure that the fix to this bug works with your stack. Today I >>> tested >>> > 8.1.1 RC-1 (not public yet) for this bug and I could not reproduce it >>> using >>> > a couple of simple stacks. >>> > >>> > Best regards, >>> > Panos >>> > -- >>> > >>> > On Mon, Sep 19, 2016 at 10:47 PM, Chris Sheffield < >>> cs_livec...@icloud.com> >>> > wrote: >>> > >>> >> Panos, >>> >> >>> >> I greatly appreciate the quick reply. Unfortunately that fix didn’t >>> work >>> >> for me. I even dug in a little deeper and applied Monte’s other >>> changes as >>> >> well, and my build still fails. The —resource-rules error is gone, >>> but I am >>> >> still left with the second part of the error about the "resource fork, >>> >> Finder information, or similar detritus not allowed”. That is with >>> the line: >>> >> >>> >> get shell("xattr -cr" && quote & pAppBundle & quote) >>> >> >>> >> added just before the code signing occurs. >>> >> >>> >> This is running macOS Sierra (GM), LiveCode 8.1, and Xcode 7.3.1. >>> >> >>> >> Any other ideas? >>> >> >>> >> Thanks, >>> >> Chris >>> >> >>> >> >>> >>> On Sep 19, 2016, at 12:06 PM, panagiotis merakos <merak...@gmail.com >>> > >>> >> wrote: >>> >>> >>> >>> Hi Chris, >>> >>> >>> >>> Try the workaround described here: >>> >>> http://quality.livecode.com/show_bug.cgi?id=18135 >>> >>> >>> >>> It worked for me. >>> >>> >>> >>> Best, >>> >>> Panos >>> >>> On 19 Sep 2016 19:01, "Chris Sheffield" <cs_livec...@icloud.com> >>> wrote: >>> >>> >>> >>>> I’m hoping someone can help with this. >>> >>>> >>> >>>> I just fired up LiveCode 8.1 this morning to create a new app build >>> for >>> >> a >>> >>>> landscape app that has the “cropped” issue in iOS 10. I am getting >>> an >>> >> error >>> >>>> at the point that the app gets signed: >>> >>>> >>> >>>> codesigning failed with Warning: —resource-rules has been >>> deprecated in >>> >>>> Max OS X >= 10.10! >>> >>>> [path to my app]: resource fork, Finder information, or similar >>> detritus >>> >>>> not allowed >>> >>>> >>> >>>> I did a little digging and it sounds like, in an Xcode project at >>> least, >>> >>>> it’s simply a matter of removing the path to the ResourceRules.plist >>> >> file >>> >>>> in the project settings. I went and tried doing what I thought >>> would be >>> >> the >>> >>>> equivalent in LiveCode and I commented out the lines pertaining to >>> this >>> >>>> file in the Settings.plist file, but that didn’t do the trick. >>> >>>> >>> >>>> Has anyone run into this one? I really need to get this figured out >>> >> asap. >>> >>>> Even if it can be solved with a temporary workaround, that’d be >>> great. >>> >>>> >>> >>>> Thanks, >>> >>>> Chris >>> >>>> >>> >>>> >>> >>>> -- >>> >>>> Chris Sheffield >>> >>>> Read Naturally, Inc. >>> >>>> www.readnaturally.com >>> >>>> >>> >>>> _______________________________________________ >>> >>>> use-livecode mailing list >>> >>>> use-livecode@lists.runrev.com >>> >>>> Please visit this url to subscribe, unsubscribe and manage your >>> >>>> subscription preferences: >>> >>>> http://lists.runrev.com/mailman/listinfo/use-livecode >>> >>> _______________________________________________ >>> >>> use-livecode mailing list >>> >>> use-livecode@lists.runrev.com >>> >>> Please visit this url to subscribe, unsubscribe and manage your >>> >> subscription preferences: >>> >>> http://lists.runrev.com/mailman/listinfo/use-livecode >>> >> >>> >> _______________________________________________ >>> >> use-livecode mailing list >>> >> use-livecode@lists.runrev.com >>> >> Please visit this url to subscribe, unsubscribe and manage your >>> >> subscription preferences: >>> >> http://lists.runrev.com/mailman/listinfo/use-livecode >>> >> >>> > _______________________________________________ >>> > use-livecode mailing list >>> > use-livecode@lists.runrev.com >>> > Please visit this url to subscribe, unsubscribe and manage your >>> subscription preferences: >>> > http://lists.runrev.com/mailman/listinfo/use-livecode >>> >>> >>> _______________________________________________ >>> use-livecode mailing list >>> use-livecode@lists.runrev.com >>> Please visit this url to subscribe, unsubscribe and manage your >>> subscription preferences: >>> http://lists.runrev.com/mailman/listinfo/use-livecode >> >> > > > -- > Panagiotis Merakos <panos.mera...@livecode.com> > LiveCode Software Developer > > Everyone Can Create Apps <https://livecode.com> > -- Panagiotis Merakos <panos.mera...@livecode.com> LiveCode Software Developer Everyone Can Create Apps <https://livecode.com> _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
