Page 1 of 1

Levure framework - non stackFiles

Posted: Tue Oct 29, 2019 6:15 pm
by mimu
i've accidently deleted the non-stackfiles in my Application Settings of standalone.livecode
(see attached image)
How can i recreate all these cryptic path ?
Bildschirmfoto 2019-10-29 um 17.52.39.png

Re: Levure framework - non stackFiles

Posted: Tue Oct 29, 2019 9:07 pm
by mimu
now i'am trying to use a backup from 4 weeks ago,
(app was working fine)
but when i execute
levureTestApplicationInSimulator "android", "beta"
i get this error Message:
Bildschirmfoto 2019-10-29 um 21.01.18.png
Any ideas what's my mistake?

Re: Levure framework - non stackFiles

Posted: Thu Oct 31, 2019 10:32 pm
by trevordevore
It looks like the standalone.livecode stack was saved while it was being built. You can remove all entries from the "Copy Files" pane. That should be empty. It is filled in by the Levure packager when building standalone.

Re: Levure framework - non stackFiles

Posted: Mon Nov 04, 2019 2:49 pm
by mimu
Hello Trevor,
thank you very much for your help.

I deleted all entries in the "copyFiles" pane.

When i call levureTestApplicationInSimulator "android", "beta" in the messagebox the Application is built and installed on my android test device, but only the standalone stack with the button "Open Application" is shown.

I'am really lost.
Bevore i had the project folder inside an iCloud folder, now moved it to desktop,
even tried to replace the levurefolder with the newest version, but no change.
The iOS version runs without any problems.

I've attached the build log and the yaml file.
Using LC 9.5.0 business , MacOS 10.13.6

I 'hope you have some tips what i've screwed up.

Re: Levure framework - non stackFiles

Posted: Tue Nov 05, 2019 12:02 am
by trevordevore
Since the app builds for iOS and works but not for Android it appears that there isn't a configuration issue. I would suggest checking to see if some code that is running is triggering an error.I would start by placing some debug code (a simple answer "I'm here!" will do) in the `InitializeApplication` and `OpenApplication` handlers of the app.livecodescript stack script. If that debug code is triggered then it is just a matter of determine where the code stops working.

If the debug code doesn't execute in `InitializeApplication` then something within Levure or a helper may be causing a problem. You could sprinkle some debug code in the `levureInitializeFramework` handler in the levure.livecodescript file.