Incorrect ParentDataWidget in Flutter — Fix
An Incorrect use of ParentDataWidget error is thrown when widgets like Positioned or Expanded are not direct children of their required parent RenderObject (such as Stack or Flex). Learn how ParentData is attached in Flutter and how to structure your widget hierarchy properly.
Why this happens: The 'Incorrect use of ParentDataWidget' error happens when a widget that supplies parent data (such as Positioned or Expanded) is separated from its required ancestor (Stack or Flex) by an intermediary container like Container or Padding.
How to fix it: Move the ParentDataWidget so it is an immediate child of its target container (e.g. Stack > Positioned > Container, never Stack > Container > Positioned).
An application renders a user profile avatar or shopping cart button with an absolute-positioned notification badge in the upper right quadrant. The developer wants to style the badge with padding, a rounded border, and a ripple tap effect. They create a helper method or wrap the badge in a Container, and inside that container they place `Positioned(top: 0, right: 0, child: Badge())`.
During widget tree construction, Flutter crashes immediately with an `Incorrect use of ParentDataWidget` error before the first frame paints. The app enters an error state because the ParentDataWidget was intercepted by the intermediary Container.
Observed Symptom & Flutter Error Assertion
Incorrect use of ParentDataWidget: Positioned widgets must be placed directly inside Stack widgets, or Expanded directly inside Flex/Row/Column.
════╡ EXCEPTION CAUGHT BY WIDGETS LIBRARY ╞═════════════════════════════════════════════════════════
The following assertion was thrown during widget build:
Incorrect use of ParentDataWidget.
The following ParentDataWidgets are providing parent data to the same RenderObject:
- Positioned(top: 10.0, left: 10.0)
However, the ParentDataWidget was not a direct child of a Stack widget.
The parent of Positioned was:
Container
The nearest ancestor Stack was:
Stack
════════════════════════════════════════════════════════════════════════════════════════════════════Declared Conditions
Nesting an intermediary widget (e.g. Container, Padding, or GestureDetector) between a ParentDataWidget (Positioned, Expanded, Flexible) and its required parent (Stack, Row, Column).
Official References
ParentDataWidget subclasses (like Positioned or Expanded) exist specifically to write layout parameters (StackParentData, FlexParentData) onto the RenderObject of their immediate parent. An intermediary widget intercepts this chain and cannot accept the foreign ParentData.
Move the ParentDataWidget so it is an immediate child of its parent (e.g. Stack > Positioned > Container, never Stack > Container > Positioned).
Architectural Deep Dive: Why This Failure Occurs in Flutter
Flutter Layout ProtocolIn Flutter's rendering pipeline, every RenderObject possesses a parentData property whose type is dictated strictly by its parent RenderObject (e.g., RenderStack creates StackParentData; RenderFlex creates FlexParentData).
A ParentDataWidget does not instantiate a RenderObject itself. Instead, it overrides applyParentData(RenderObject) to populate layout configuration (such as top, left, right, bottom offsets for Stack, or flex factor for Flex) into its child's RenderObject.parentData slot.
ParentDataWidget.debugIsValidAncestor() validates that the target RenderObject is an instance of the required parent class. When an intermediary widget (e.g. Container, which builds a RenderDecoratedBox) sits between Stack and Positioned, Positioned attempts to write StackParentData onto a RenderObject expecting BoxParentData, triggering an immediate framework assertion.
ParentDataWidget Tree Architecture: Broken vs Valid
Flutter RenderObject ParentData Attachment RuleParentDataWidget cannot attach StackParentData or FlexParentData onto an intermediary Container's RenderObject.
ParentDataWidget immediately communicates with parent's RenderObject, writing offsets and flex factors cleanly.
Positioned must be a direct child of Stack to write StackParentData onto the RenderStack.
Corrected: Positioned as Direct Child of Stack
Move Positioned directly below Stack, then place the Container or Badge inside Positioned.
- ✓Place Positioned as a direct child of Stack
- ✓Move decorative styling and padding inside Positioned's child
import 'package:flutter/material.dart';
void main() => runApp(const FixedParentDataDemo());
class FixedParentDataDemo extends StatelessWidget {
const FixedParentDataDemo({super.key});
@override
Widget build(BuildContext context) {
return MaterialApp(
debugShowCheckedModeBanner: false,
home: Scaffold(
appBar: AppBar(title: const Text('Fixed: Direct Positioned Child'), backgroundColor: const Color(0xFF0D9488)),
body: Center(
child: SizedBox(
width: 320,
height: 200,
child: Stack(
children: [
Container(
width: 320,
height: 200,
decoration: BoxDecoration(
color: Colors.white,
borderRadius: BorderRadius.circular(16),
border: Border.all(color: const Color(0xFF2DD4BF), width: 2),
),
child: const Center(
child: Text('Card Surface Area', style: TextStyle(fontWeight: FontWeight.bold)),
),
),
// FIX: Positioned is a direct child of Stack!
Positioned(
top: 14,
right: 14,
child: Container(
padding: const EdgeInsets.symmetric(horizontal: 10, vertical: 4),
decoration: BoxDecoration(
color: const Color(0xFF2DD4BF),
borderRadius: BorderRadius.circular(8),
),
child: const Text('PRO', style: TextStyle(color: Colors.white, fontWeight: FontWeight.bold, fontSize: 12)),
),
),
],
),
),
),
),
);
}
}
Alternative Fixes & Decision Framework
Compare Flutter architectural solutions to select the ideal strategy for your UX requirements.
Stack(
children: [
const BackgroundCard(),
Positioned(
top: 12,
right: 12,
child: Container(
padding: const EdgeInsets.symmetric(horizontal: 8, vertical: 4),
decoration: BoxDecoration(
color: Colors.red,
borderRadius: BorderRadius.circular(10),
),
child: const Text('3', style: TextStyle(color: Colors.white)),
),
),
],
)When to choose: Choose for any absolute-positioned overlay in a Stack where the badge or tag requires custom padding, decoration, or sizing.
Trade-offs: Standard and universally correct approach in Flutter. Positioned becomes the immediate child of Stack, with visual styling applied to its child.
Row(
children: [
const Icon(Icons.star),
Expanded(
child: Container(
padding: const EdgeInsets.all(8),
color: Colors.grey.shade200,
child: const Text('Flexible content'),
),
),
],
)When to choose: Choose whenever an Expanded or Flexible widget was inadvertently wrapped inside a Container, Padding, or GestureDetector inside a Row or Column.
Trade-offs: Expanded communicates directly with RenderFlex, passing bounded constraints down to the Container.
Stack(
children: [
const BackgroundCard(),
Align(
alignment: Alignment.topRight,
child: Padding(
padding: const EdgeInsets.all(12),
child: const BadgeChip(),
),
),
],
)When to choose: Choose when the overlay is positioned at a standard corner or edge (topRight, bottomCenter) and fractional alignment is cleaner than hardcoded pixel offsets.
Trade-offs: Align is a standard SingleChildRenderObjectWidget rather than a ParentDataWidget, so it has no ParentData placement restrictions and can be safely wrapped in other widgets.
// Good component design: returns pure visual content
class NotificationBadge extends StatelessWidget {
const NotificationBadge({super.key, required this.count});
final int count;
@override
Widget build(BuildContext context) {
return Container(
padding: const EdgeInsets.all(4),
decoration: const BoxDecoration(color: Colors.red, shape: BoxShape.circle),
child: Text('$count', style: const TextStyle(color: Colors.white, fontSize: 10)),
);
}
}
// Call site supplies ParentDataWidget:
Stack(
children: const [
Avatar(),
Positioned(top: 0, right: 0, child: NotificationBadge(count: 3)),
],
)When to choose: Choose when designing shared design system widgets so they can be reused across Stacks, Rows, or standard layouts without throwing ParentDataWidget errors.
Trade-offs: Eliminates hidden ParentData dependencies inside custom component build methods.
Architectural Limitations & Edge Cases
- ⚠ParentDataWidgets cannot be returned as root widgets from custom stateless or stateful widgets unless those custom widgets are guaranteed to be placed exclusively within the required parent.
- ⚠A Stack cannot contain an Expanded widget (Expanded requires RenderFlex, not RenderStack). Attempting this throws a different ParentData mismatch.
- ⚠TableCell widgets can only be placed as direct children of TableRow within a Table.
Common Mistakes to Avoid in Flutter
- •Wrapping a Positioned widget inside a Container or Padding before adding it to a Stack
- •Returning an Expanded or Flexible from a helper widget whose parent is not a Row, Column, or Flex
- •Using TableCell outside the children list of a TableRow
Automated Verification Proof & Toolchain Evidence
Verification Contract: Automated test suite tests invalid Positioned inside intermediary Container, traps assertion in isolated zone, and verifies corrected inverted hierarchy (Stack > Positioned > Container and Row > Expanded > Container) renders 0 errors.