Same error can appear multiple times

[iddan]

Union type makes this to happen:

 • Either inexact props [1] is incompatible with exact Props [2].
 • Or inexact props [1] is incompatible with exact Props [2].
 • Or inexact props [1] is incompatible with exact Props [2].
 • Or inexact props [1] is incompatible with exact Props [2].
 • Or inexact props [1] is incompatible with exact Props [2].
 • Or inexact props [1] is incompatible with exact Props [2].
 • Or inexact props [1] is incompatible with exact Props [2].
 • Or inexact props [1] is incompatible with exact Props [2].
 • Or inexact props [1] is incompatible with exact Props [2].
 • Or inexact props [1] is incompatible with exact Props [2].
 • Or inexact props [1] is incompatible with exact Props [2].
 • Or inexact props [1] is incompatible with exact Props [2].
 • Or inexact props [1] is incompatible with exact Props [2].
 • Or inexact props [1] is incompatible with exact Props [2].
 • Or inexact props [1] is incompatible with exact Props [2].
 • Or inexact props [1] is incompatible with exact Props [2].
 • Or inexact props [1] is incompatible with exact Props [2].
 • Or inexact props [1] is incompatible with exact Props [2].
 • Or inexact props [1] is incompatible with exact Props [2].
 • Or inexact props [1] is incompatible with exact Props [2].
 • Or inexact props [1] is incompatible with exact Props [2].
 • Or inexact props [1] is incompatible with exact Props [2].
 • Or inexact props [1] is incompatible with exact Props [2].
 • Or inexact props [1] is incompatible with exact Props [2].

[cprodescu]

Thank you for reporting! Can you add a minimal example using flow.org/try/

My blind guess is that you're passing an object spread {...props} to a React component that uses an exact type as Props. That is a known issue, likely related to #2405

[iddan]

Exactly that, but the props contain a spread of union of exact object types

[SamChou19815]

We now limit the size of the union type errors