E_UNEXPECTED UWP Catastrophic Failure

Question

I am getting the following:

Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED))

when the ListView attribute is set to Null in the Visual State. It makes no sense, why does VS and Blend complain?

<VisualState.Setters>
     <Setter Target="listView.(Selector.IsSynchronizedWithCurrentItem)" Value="{x:Null}"/>
</VisualState.Setters>

EDIT
A similar issue:

 <VisualState.Setters>
   <Setter Target="NumberButtonBox.(RelativePanel.RightOf)" Value="{x:Null}" />
   <Setter Target="NumberButtonBox.(RelativePanel.Below)" Value="GridPlaceholder" />
</VisualState.Setters>

where NumberButtonBox is defined as

<Viewbox x:Name="NumberButtonBox" RelativePanel.RightOf="GridPlaceholder" MaxWidth="250" MaxHeight="450" MinWidth="200">

The error shows only on the setter using a value of {x:Null}, not on the other line. Changing the order of the Setter lines has no effect.

Is setting the property to Null in this way the correct way to clear this value? At runtime it does work, just the editor has issues with this.

"Catastrophic failure" is merely a description of the quality of the error reporting in UWP, it is quite useless to diagnose anything. http://stackoverflow.com/help/mcve — Hans Passant, Jun 23 '16 at 13:18
But at least it happens in a specific situation: a `` with a Value of `{x:Null}` — Hans Keﬆing, Jun 24 '16 at 06:33
what is the listview in your code? please post some more code .. — Akash Gutha, Jun 26 '16 at 16:35

score 2 · Answer 1 · edited May 23 '17 at 12:33

2

The only alternative to set null without crash at design time is this (as reported in this similar question)

example:

<Style x:Key="MyList" TargetType="ListView">
    <Setter Property="Transitions" >
        <Setter.Value>
            <TransitionCollection></TransitionCollection>
        </Setter.Value>
    </Setter>
</Style>

instead of:

Style x:Key="MyList"
        TargetType="ListView">
    <Setter Property="Transitions" 
            Value="{x:Null}"/>
</Style>

edited May 23 '17 at 12:33

Community

1
1

answered Jun 29 '16 at 16:09

Frix33

1,191
11
27

An empty collection could work for a collection-type property, but not for others. And note that it is only the designer that reports a crash, runtime it works as expected. – Hans Keﬆing Jun 29 '16 at 18:31
Mmh for not collection-type i think the only way is use a Converter instead of x:Null bind. Check this: http://stackoverflow.com/questions/356194/datatrigger-where-value-is-not-null – Frix33 Jun 30 '16 at 06:31

E_UNEXPECTED UWP Catastrophic Failure

1 Answers1