Expecting binder but got null

Question

I'm getting this message on my log although everything works fine

W/Parcel: Expecting binder but got null!

Has anyone faced such issue, and how to fix it?

Steps to Reproduce:

Just create a new Flutter project and run it on a simulator/emulator
See logs, you'll get this message: "Expecting binder but got null"

Expected behavior:

There should not be such error message

Runner Log

Launching lib/main.dart on sdk gphone64 x86 64 in debug mode...
Running Gradle task 'assembleDebug'...
✓  Built build/app/outputs/flutter-apk/app-debug.apk.
Installing build/app/outputs/flutter-apk/app-debug.apk...
Debug service listening on ws://127.0.0.1:62931/5G0AlEiF5bQ=/ws
Syncing files to device sdk gphone64 x86 64...
I/.flutter_issues(17884): Compiler allocated 4533KB to compile void android.view.ViewRootImpl.performTraversals()
E/SurfaceSyncer(17884): Failed to find sync for id=0
W/Parcel  (17884): Expecting binder but got null!

I used @răzvan-puiu 's answer. ``` void main() { WidgetsFlutterBinding.ensureInitialized(); runApp(const MyApp()); } ``` It worked. — Maharun Afroz, Jun 22 '23 at 12:55

score 8 · Accepted Answer · answered Aug 28 '22 at 15:38

8

Try adding the line below in the main() function

WidgetsFlutterBinding.ensureInitialized();

If this doesn't work, please check that the value you pass to the initialBinding: in the MaterialApp() is not null.

answered Aug 28 '22 at 15:38

Răzvan Puiu

671
1
6
24

1

I'm still getting this issue – SardorbekR Aug 28 '22 at 16:14
what if I write app without using binding ?? I start to use Android studio in 2017 or 2018, at that time default project didnt use binding. I realized new project use binding in 2018 or 2019 but I always change back to old codes and write very long code with longer time... so can we just ignore the warning? – Raii Nov 01 '22 at 16:08
2

MaterialApp doesn't have initialBinding parameter – Behzod Faiziev Nov 29 '22 at 09:23
@SardorbekR Did you got how to fix this issue ? – Rohan Jan 05 '23 at 17:36
@Rohan No, I didn't find a solution, but this message is not shown anymore – SardorbekR Jan 06 '23 at 03:49
1

Solved. void main() { WidgetsFlutterBinding.ensureInitialized(); runApp(const MyApp()); } – Maharun Afroz Jun 22 '23 at 12:49
1

It's working for me. I just move that statement to first line in main() function. – Doan Thai Jun 29 '23 at 09:49
1

since this answer is working for most people I'll accept it – SardorbekR Aug 29 '23 at 05:01

score 6 · Answer 2 · answered Dec 22 '22 at 07:59

6

Literally

File -> Invalidate Caches -> Clear Filesystem Cache

And then rebuilding fixed it for me (React Native 0.68.2)

answered Dec 22 '22 at 07:59

Karatekid430

940
11
25

Aygün Özdemir · Answer 3 · 2023-01-08T08:31:16.150

0

I have super.build(); in my widget for no reason. Just forgot to delete the code. So I removed the code and fixed.

class _VehicleAddState extends State<VehicleAdd>
    with AutomaticKeepAliveClientMixin<VehicleAdd> {
  double selectedMenu = 0;
  @override
  Widget build(BuildContext context) {
    super.build(context);

edited Jan 08 '23 at 08:31

answered Jan 06 '23 at 18:36

Aygün Özdemir

11
2

As it’s currently written, your answer is unclear. Please [edit] to add additional details that will help others understand how this addresses the question asked. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Jan 08 '23 at 02:00

score 0 · Answer 4 · edited Aug 08 '23 at 17:25

0

The message actually doesn't affect the functionality of the app. But still you can add a line in the main(). Add WidgetsFlutterBinding.ensureInitialized(); in the main function

void main() {
  WidgetsFlutterBinding.ensureInitialized();
  runApp(const MyApp());
}

edited Aug 08 '23 at 17:25

toyota Supra

3,181
4
15
19

answered Aug 08 '23 at 15:01

Karun Jose

41
3

Expecting binder but got null

4 Answers4

Linked