9.6.6 build errors

William Prothero waprothero at gmail.com
Tue Feb 1 20:45:42 EST 2022 

Jacqueline:
Thank you for posting this. I simply forgot why we turned off messages. I got involved in other things and it’s been awhile since I’ve built an app that I want someone else to use. 

The problem I worry about is that there may be messages that refer to problems with the build process.
Bill

> On Feb 1, 2022, at 10:13 AM, J. Landman Gay via use-livecode <use-livecode at lists.runrev.com> wrote:
> 
> It's one of the most intrusive changes LC has ever made. Can we get a stack property to indicate whether we want messages locked or not? Except for a few specific situations, I'm betting most of us want the old behavior.
> 
> --
> Jacqueline Landman Gay | jacque at hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
> On February 1, 2022 11:58:27 AM panagiotis m via use-livecode <use-livecode at lists.runrev.com> wrote:
> 
>> Oh right, I see, thanks Klaus and Jacque. Yes, this is what Bill probably
>> meant. You still have to perform these checks though, because since LC 9
>> messages are not locked when building a standalone, and it is not
>> recommended to lock messages manually.
>> 
>> Kind regards,
>> Panos
>> 
>> On Tue, 1 Feb 2022, 19:39 J. Landman Gay via use-livecode, <
>> use-livecode at lists.runrev.com> wrote:
>> 
>>> I think you mean how we have to litter our scripts with checks for the
>>> standalone builder in every *open/whatever handler. Turning off messages
>>> was a way to accomplish the same thing without altering the scripts. If
>>> building standalones gives you problems then you'd still need to do that.
>>> 
>>> I hadn't thought about how this may be affecting my current stack, since
>>> I've never had any trouble before.
>>> --
>>> Jacqueline Landman Gay | jacque at hyperactivesw.com
>>> HyperActive Software | http://www.hyperactivesw.com
>>> On February 1, 2022 11:12:51 AM William Prothero via use-livecode
>>> <use-livecode at lists.runrev.com> wrote:
>>> 
>>> > Thanks, Panos. I remember having to disable build messages, or something
>>> > like that, but I haven’t built an app for awhile. I know breakpoints
>>> needed
>>> > to be removed, but I thought there was something else. Anyway, this will
>>> > help me in my current project with lc9.6.6.
>>> >
>>> > Thanks,
>>> > Bill
>>> >
>>> > William A. Prothero, PhD
>>> > Prof Emeritus, Dept of Earth Science
>>> > University of California, Santa Barbara
>>> >
>>> >> On Feb 1, 2022, at 8:53 AM, panagiotis m via use-livecode
>>> >> <use-livecode at lists.runrev.com> wrote:
>>> >>
>>> >> Hello Bill,
>>> >>
>>> >> You do not need to disable error msgs to build a standalone. I am not
>>> sure
>>> >> if you ever had to.
>>> >>
>>> >> Kind regards,
>>> >> Panos
>>> >> --
>>> >>
>>> >>> On Tue, 1 Feb 2022 at 18:46, William Prothero via use-livecode <
>>> >>> use-livecode at lists.runrev.com> wrote:
>>> >>>
>>> >>> Regarding this, I don’t recall seeing a reply to my query about whether
>>> >>> you still need to disable error messages when building a standalone.
>>> >>> Hopefully this has been fixed, but …
>>> >>>
>>> >>> Best,
>>> >>> Bill
>>> >>>
>>> >>> William A. Prothero, PhD
>>> >>> Prof Emeritus, Dept of Earth Science
>>> >>> University of California, Santa Barbara
>>> >>>
>>> >>>> On Feb 1, 2022, at 6:59 AM, matthias rebbe via use-livecode <
>>> >>> use-livecode at lists.runrev.com> wrote:
>>> >>>>
>>> >>>> Mark,
>>> >>>>
>>> >>>> where are you saving the standalone to?
>>> >>>> Any chance that the target folder is on iCloud drive. E.g. Desktop or
>>> >>> Documents folder?
>>> >>>>
>>> >>>> I had similar problems in the past when i built the standalone
>>> directly
>>> >>> on the Desktop or Documents folder which were both synchronized with
>>> iCloud
>>> >>> Drive. I just cannot remember the correct error message. Sometimes the
>>> >>> build process was successful and sometimes it was aborted.
>>> >>>> I could solve this to select a target folder outside of iCloud Drive.
>>> >>>> Btw. building the standalone in a Dropbox folder works w/o problems.
>>> >>>>
>>> >>>> Matthias
>>> >>>>
>>> >>>>> Am 01.02.2022 um 11:47 schrieb Mark Smith via use-livecode <
>>> >>> use-livecode at lists.runrev.com>:
>>> >>>>>
>>> >>>>> Hi Panos,
>>> >>>>>
>>> >>>>> I did not change anything between attempts, just one right after the
>>> >>> other. I guess I was observing this in RC2 and just persisted and it
>>> seemed
>>> >>> to work on the 2nd or 3rd attempt. For good measure I just took the
>>> same
>>> >>> stack and was able to build and install two more times without
>>> incident so
>>> >>> it’s definitely not a repeatable problem and as yet I have no formula
>>> or
>>> >>> hypothesis as to what might be causing it. I’ll keep an eye on it and
>>> log
>>> >>> any similar problems I run across.
>>> >>>>>
>>> >>>>> Mark
>>> >>>>>
>>> >>>>>
>>> >>>>>>> On Feb 1, 2022, at 10:23 AM, panagiotis m via use-livecode <
>>> >>> use-livecode at lists.runrev.com> wrote:
>>> >>>>>>
>>> >>>>>> Hello Mark,
>>> >>>>>>
>>> >>>>>> I have not seen this before. Did anything change in your stack
>>> (used a
>>> >>>>>> different provisioning profile or changed anything in the iOS
>>> >>> settings) or
>>> >>>>>> in the iOS device until the successful 3rd attempt?
>>> >>>>>>
>>> >>>>>> I cannot remember of anything that we changed in the 9.6.6 release
>>> >>> cycle
>>> >>>>>> that could have caused this behavior.
>>> >>>>>>
>>> >>>>>> Kind regards,
>>> >>>>>> Panos
>>> >>>>>>
>>> >>>>>> On Tue, 1 Feb 2022 at 12:14, Mark Smith via use-livecode <
>>> >>>>>> use-livecode at lists.runrev.com> wrote:
>>> >>>>>>
>>> >>>>>>> I just wanted to flag this issue. I am currently using the new
>>> release
>>> >>>>>>> version of 9.6.6 although I did have similar problems with RC2 as
>>> >>> well.
>>> >>>>>>> This morning I took a stack I had previously built and successfully
>>> >>>>>>> installed (using Development/Test Target -> iPhone) and tried
>>> >>> installing
>>> >>>>>>> it. The first time the app went through what appeared to be all the
>>> >>> build
>>> >>>>>>> steps but did not install the app. The 2nd time it went through all
>>> >>> of the
>>> >>>>>>> steps and then reported “Unknown Error” and the 3rd time it built
>>> and
>>> >>>>>>> installed the app correctly. I’ve not noticed behaviour like this
>>> in
>>> >>>>>>> previous versions. At the moment I have no hypothesis about what
>>> >>> might be
>>> >>>>>>> going on.
>>> >>>>>>>
>>> >>>>>>> Mark
>>> >>>>>>>
>>> >>>>>>>
>>> >>>>>>> _______________________________________________
>>> >>>>>>> use-livecode mailing list
>>> >>>>>>> use-livecode at 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 at 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 at 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 at 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 at 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 at 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 at 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 at 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 at 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 at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

William Prothero
waprothero at gmail.com

More information about the use-livecode mailing list