error: The argument type 'Future' can't be assigned to the parameter type 'void Function()'
Asked Answered
O

4

48

While I am passing value from home page to source page it shows an error: The argument type 'Future' can't be assigned to the parameter type 'void Function()'. (argument_type_not_assignable at [strong text] lib\home.dart:15)

Where I am doing wrong??

Home page -

import 'package:flutter/material.dart';
import 'sourceScreen.dart';

class Home extends StatefulWidget {
  int value;
  Home({this.value});
  @override
  _HomeState createState() => _HomeState();
}

class _HomeState extends State<Home> {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Center(
        child: FlatButton(
          onPressed: Navigator.push(context, MaterialPageRoute(builder: (context)=>SourceScreen({value:value}))), child: null,
        ),
      ),
    );
  }
}

Below page is where I wanna use home page value-

import 'package:flutter/material.dart';
import 'dart:convert';
import 'package:http/http.dart' as http;
import 'models/model.dart';
import 'models/card.dart';
import 'article.dart';

final API_KEY = '***';

Future<List<Source>> fetchNewsSource() async {
  final response = await http.get(
      'https://newsapi.org/v2/sources?language=en&country=in&apiKey=$API_KEY');

  if (response.statusCode == 200) {
    List sources = json.decode(response.body)['sources'];
    return sources.map((source) => new Source.formJson(source)).toList();
  } else {
    throw Exception('Fail to load data');
  }
}

class SourceScreen extends StatefulWidget {
  @override
  _SourceScreenState createState() => _SourceScreenState();
}

class _SourceScreenState extends State<SourceScreen> {
  var list_source;
  var refreshKey = GlobalKey<RefreshIndicatorState>();

  @override
  void initState() {
    super.initState();
    refreshListSource();
  }

  Future<Null> refreshListSource() async {
    refreshKey.currentState?.show(atTop: false);
    setState(() {
      list_source = fetchNewsSource();
    });
  }

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        backgroundColor: Color.fromRGBO(58, 66, 86, 1.0),
        appBar: AppBar(
          elevation: 1.0,
          backgroundColor: Color.fromRGBO(58, 66, 86, 1.0),
          title: Text('uTTerNews'),
        ),
        body: Center(
          child: RefreshIndicator(
              child: FutureBuilder<List<Source>>(
                future: list_source,
                builder: (context, snapshot) {
                  if (snapshot.hasError) {
                    Text('Error: ${snapshot.error}');
                  } else if (snapshot.hasData) {
                    List<Source> sources = snapshot.data;
                    return new ListView(
                        children: sources
                            .map((source) =>
                            GestureDetector(
                              onTap: () {
                                Navigator.push(context, MaterialPageRoute(
                                    builder: (context) =>
                                        articleScreen(source: source,)));
                              },
                              child: card(source),
                            ))
                            .toList());
                  }
                  return CircularProgressIndicator();
                },
              ),
              onRefresh: refreshListSource),
        ),
      ),
    );
  }
}
Overlap answered 2/9, 2019 at 18:41 Comment(0)
U
164

Replace

onPressed: Navigator.push(...)

with

onPressed: () => Navigator.push(...)

If you need to use await keyword, you can do

onPressed: () async {
  await Navigator.push(...);
  await anyOtherMethod();
}
Underslung answered 2/9, 2019 at 18:44 Comment(3)
Thanks! But why does this work? Can you explain it?Knowhow
@Knowhow Navigator.push returns a Future and onPressed accepts void, which is why you can't directly assign Navigator.push to onPressed, however when you do onPressed: () => You're simply executing Navigator.push(...) inside the callback provided by onPressed. Hope that explained!Underslung
Ah, I see thanks for running through that much appreciated!Knowhow
B
9

This one worked for me in latest versions

 onPressed: () {
          selectHandler();
 },
Bascinet answered 16/2, 2021 at 18:2 Comment(6)
It doesn't have to do anything with the latest or older versions. This code is essentially equal to onPressed: selectHandler.Underslung
@Underslung It does. With the latest version, OnPressed: selectHandler doesn't work to onPressed as you can't assign void directly. with onPressed: () => selectHandler you are instructing to execute the function inside the callback.Exobiology
@SeshaKiran Can you show some code to support your statement that onPressed: selectHandler wouldn't work? The only time you may run into the error is when you invoke a method on an object which hasn't been initialized yet (for example when you use late keyword for lazy initialization).Underslung
@Underslung There was not usage of late keyword, but it was not working for me in a simple case. it was a sample learning code without any API.Bascinet
@ArunPrasadES A code will be appreciated.Underslung
@Underslung Pls. find the code. I added as another answer.Exobiology
E
4
    @CopsOnRoad -- Here is the sample code that is working for me.

    
      @override
      Widget build(BuildContext context) {
        return Container(
          width: double.infinity,
          child: RaisedButton(
            color: Colors.grey,
            textColor: Colors.black,
            child: Text('Answer 1'),
            **onPressed: () => selectHandler()**,
          ),
        );
      }
    }
    
   
Exobiology answered 2/6, 2021 at 1:44 Comment(1)
First this is not a code I can reproduce on my own. Please post a minimal reproducible code. Second, Function is not recommended to be used without the parameter. It should be Function()Underslung
R
0

simply change the final Function selectHandler to final VoidCallback selectHandler;

Rollins answered 9/9, 2021 at 10:1 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.