skip to Main Content

Team,

I have been initializing Firebase like this since I started by following this flutter documentation, but for some reason this throws an error in the debugger, as follows:

TypeError: Class constructor IndexedDBLocalPersistence cannot be
invoked without ‘new’

Could you please help me rectify this?

Here is the Flutter code:

import 'package:firebase_core/firebase_core.dart';
import 'package:flutter/material.dart';
import 'package:pace/firebase_options.dart';
import 'package:pace/pages/auth_page.dart';

void main() async {
  WidgetsFlutterBinding.ensureInitialized();
  await Firebase.initializeApp(
    options: DefaultFirebaseOptions.currentPlatform,
  );
  runApp(const MyApp());
}

class MyApp extends StatefulWidget {
  const MyApp({super.key});

  @override
  State<MyApp> createState() => _MyAppState();
}

class _MyAppState extends State<MyApp> {
  @override
  Widget build(BuildContext context) {
    return const MaterialApp(
      home: Scaffold(
        body: AuthPage(),
      ),
    );
  }
}

2

Answers


  1. I occurred into the same error while trying to release my app on web and after a few attempts I have eventually found a solution for it.
    Here are the steps I have performed:

    1. Run flutter channel stable to make sure that you are currently using a stable channel and not a beta
    2. Run flutter upgrade to update to the latest version of the SDK, Dart SDK will update accordingly.
    3. Run flutter --version to check both your Flutter SDK version and your Dart SDK version.
    4. Make sure that your pubspec.yaml includes you Dart SDK version in the version constraints specified. (Example: if your Dart SDK version shown in the output provided from flutter --version is 2.19.4, make sure that your code looks something like this sdk: '>=2.19.0 <4.0.0' at least).
    5. In my case scenario, the issue is solved using Flutter SDK version 3.7.0 with Dart SDK version 2.19.0, however this is not the latest version, but I am confident that even with the last stable version ( Flutter SDK 3.16.5) the issue shouldn’t occur.

    Hopefully this solves the issue!

    Login or Signup to reply.
  2. Just downgrade from beta to stable.

    Login or Signup to reply.
Please signup or login to give your own answer.
Back To Top
Search