The problem appears to be on line 44.

“non-simple” MXML entires should be an array, but your case is an empty array.

I’ve seen this happen when the wrong type is used in the MXML. What are you 
specifying for the itemRenderer? Is it a string instead of a reference?

I’ve created an issue that we should catch these errors at compile-time, but 
someone has to work on that… ;-)
https://github.com/apache/royale-compiler/issues/96 
<https://github.com/apache/royale-compiler/issues/96>

HTH,
Harbs

> On Sep 23, 2019, at 12:27 PM, Serkan Taş <serkan....@likyateknoloji.com> 
> wrote:
> 
> I tried removing "excludeFrom" but failed with the same error Harbs.
> 
> Here is the debug view of the step which throws exception :
> 
> <hofbadiapnfkgngg.png>
> 
> data array content :
> <anbhmfojjnegbbma.png>
> 
> <eibffggjiaffciaa.png>
> <oplijogleghgamec.png>
> 
> <macnpeoicbolbkih.png>
> 23.09.2019 10:33 tarihinde Harbs yazdı:
>> A likely cause of the problem is the “excludeFrom” piece. Definitely try to 
>> narrow that down.
>> 
>> I’ve bumped into issues using “includeIn” in the past, and there’s likely 
>> still bugs related to states. I generally use state.visible instead of 
>> includeIn.
>> 
>> HTH,
>> Harbs
>> 
>>> On Sep 23, 2019, at 8:45 AM, Serkan Taş <serkan....@likyateknoloji.com 
>>> <mailto:serkan....@likyateknoloji.com>> wrote:
>>> 
>>> Thanks Alex, just to be sure, can you see the images attached ?
>>> 
>>> 23.09.2019 08:40 tarihinde Alex Harui yazdı:
>>>> You’ll have to catch the exception in the debugger and find out what “cls” 
>>>> is supposed to be.  That section of code could be run quite often when 
>>>> setting up an MXML-based UI.
>>>>  
>>>> The MXMLDataInterpreter is interpreting a data array from some .JS file 
>>>> representing an MXML file, and initializeStrandBasedObject is trying to 
>>>> initialize some component and probably calls generateMXMLObject to create 
>>>> some object that initializes some property.  You’ll have to figure out 
>>>> what was in the data arrays and what went wrong.  You should find that 
>>>> generateMXMLObject is passed a data array that is part of a different 
>>>> array passed to initializedStrandBasedObject.  Knowing what class that 
>>>> strandBasedObject is may help you figure out what part of what MXML is 
>>>> having a problem.
>>>>  
>>>> HTH,
>>>> -Alex
>>>>  
>>>>  
> 

Reply via email to