As I mentioned in another post, my release version doesn't work either (a few months ago I did a test deployment and it worked, with less code of course). In my case I get this error:
App.mxml:40 Uncaught TypeError: a.child is not a function at $$.J.Zwa (App.mxml:40) at B4.J.HA (EventDispatcher.as:131) at Jxa (eventtarget.js:381) at B4.J.dispatchEvent (EventDispatcher.as:108) at B4.J.nLa (URLLoader.as:367) My build is maven, different from Hugo's, but could the errors be related? @Harbs, could this be related to the comments made lately when minifying? I can tell this is all hyper-mega-new to me? đ Hiedra -----Mensaje original----- De: Harbs <harbs.li...@gmail.com> Enviado el: viernes, 10 de diciembre de 2021 14:05 Para: dev@royale.apache.org Asunto: Re: Differences between bebug and release You can try setting -js-dynamic-access-unknown-members=true although normally it shouldnât be necessary with the current defaults. https://apache.github.io/royale-docs/compiler/compiler-options.html#js-dynamic-access-unknown-members > On Dec 10, 2021, at 2:43 PM, Hugo Ferreira > <hferreira...@gmail.com<mailto:hferreira...@gmail.com>> wrote: > > I only see an error in console that does not seems related: > > telemetryproxy.html:1 Failed to load resource: the server responded > with a status of 404 () > > What's the option to build in release without minify to check if that > is really the case? > > Harbs <harbs.li...@gmail.com<mailto:harbs.li...@gmail.com>> escreveu no dia > sexta, 10/12/2021 Ă (s) 09:08: > >> I meant in your browser. Is there an error in the browser console? >> >>> On Dec 10, 2021, at 3:17 AM, Hugo Ferreira >>> <hferreira...@gmail.com<mailto:hferreira...@gmail.com>> >> wrote: >>> >>> Hi, >>> >>> This is the full log from my dev tool (Visual Studio Code): >>> >>>> Executing task: /usr/bin/java -jar >>> >> /Users/hugo/.vscode/extensions/bowlerhatllc.vscode-as3mxml-1.10.0/bin >> /asconfigc.jar >>> --sdk /Volumes/Data/SDK/apache-royale-src/apache-royale >>> --debug=false --project >>> /Volumes/Data/CloudDrive/Projects/GC/AddIn/asconfig.json < >>> >>> MXMLJSC >>> +royalelib=/Volumes/Data/SDK/apache-royale-src/apache-royale/framewo >>> +rks >>> --debug=false >>> +configname=royale >>> --targets=JSRoyale >>> --source-map=true >>> --html-template=src/resources/jewel-example-index-template.html >>> >> --theme=${royalelib}/themes/Jewel-Light-NoFlat-Primary-Blue-Theme/src >> /main/resources/defaults.css >>> --js-library-path+=${royalelib}/js/libs/MXRoyaleJS.swc >>> -remove-circulars >>> -js-output-optimization=skipAsCoercions >>> -compiler.exclude-defaults-css-files=MXRoyale-0.9.9-js.swc:defaults. >>> css >>> -keep-as3-metadata+=Transient >>> -- >>> src/App.mxml >>> Dec 10, 2021 1:14:43 AM >>> com.google.javascript.jscomp.LoggerErrorManager >>> printSummary >>> INFO: 0 error(s), 0 warning(s), 98.0% typed The project 'App' has >>> been successfully compiled and optimized. >>> 44.034354896 seconds >>> >>> Terminal will be reused by tasks, press any key to close it. >>> >>> No errors. >>> No warning. >>> But custom itemerrors not appear and a few features do not show. >>> Building in debug mode and all works perfectly. >>> >>> >>> Harbs <harbs.li...@gmail.com<mailto:harbs.li...@gmail.com>> escreveu no dia >>> quinta, 9/12/2021 Ă (s) >> 00:05: >>> >>>> Differences in release mode is generally because of renaming when >>>> minifying. Do you get an error in the dev tools? >>>> >>>> Make sure youâre using typedefs correctly for external APIs. >>>> >>>> Harbs >>>> >>>>> On Dec 9, 2021, at 1:52 AM, Hugo Ferreira >>>>> <hferreira...@gmail.com<mailto:hferreira...@gmail.com>> >>>> wrote: >>>>> >>>>> Hi, >>>>> >>>>> I just finished my first Royale Add-In application that was tested >>>>> only >>>> in >>>>> debug mode. >>>>> Now I compiled in release mode and when I was testing I saw that >>>>> custom item renderers did not appear. >>>>> Probably this is not merged to the App.js single file ? >>>> >>>> >> >>