Thanks to visit codestin.com
Credit goes to github.com

Skip to content

DartUri: Unresolved uri: dart:web_sql, DartUri: Unresolved uri: dart:ui when running new app in Chrome on macOSΒ #101639

Closed
@mykdavies

Description

@mykdavies

I just upgraded Flutter and I'm now getting these two messages when I launch a newly created skeleton app in Chrome on macOS.

Launching lib[/main.dart]() on Chrome in debug mode...
lib/main.dart:1
DartUri: Unresolved uri: dart:web_sql
DartUri: Unresolved uri: dart:ui
This app is linked to the debug service: ws://127.0.0.1:52145[/P_jcIvp2bYw]()=[/ws]()
Debug service listening on ws://127.0.0.1:52145[/P_jcIvp2bYw]()=[/ws]()
πŸ’ͺ Running with sound null safety πŸ’ͺ
Connecting to VM Service at ws://127.0.0.1:52145[/P_jcIvp2bYw]()=[/ws]()

It doesn't seem to affect anything yet, I just don't understand at what point it might cause problems, and if I need to do anything to resolve it.

I notice that this message appears unremarked in a few logs in other bug reports, eg github search

Steps to Reproduce

  1. Execute flutter create testapp to create a skeleton app.
  2. Execute flutter run on the app

Expected results:

Launching lib[/main.dart]() on Chrome in debug mode...
lib/main.dart:1
This app is linked to the debug service: ws://127.0.0.1:52145[/P_jcIvp2bYw]()=[/ws]()
Debug service listening on ws://127.0.0.1:52145[/P_jcIvp2bYw]()=[/ws]()
πŸ’ͺ Running with sound null safety πŸ’ͺ
Connecting to VM Service at ws://127.0.0.1:52145[/P_jcIvp2bYw]()=[/ws]()

Actual results:

Launching lib[/main.dart]() on Chrome in debug mode...
lib/main.dart:1
DartUri: Unresolved uri: dart:web_sql
DartUri: Unresolved uri: dart:ui
This app is linked to the debug service: ws://127.0.0.1:52145[/P_jcIvp2bYw]()=[/ws]()
Debug service listening on ws://127.0.0.1:52145[/P_jcIvp2bYw]()=[/ws]()
πŸ’ͺ Running with sound null safety πŸ’ͺ
Connecting to VM Service at ws://127.0.0.1:52145[/P_jcIvp2bYw]()=[/ws]()
Code sample
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        // This is the theme of your application.
        //
        // Try running your application with "flutter run". You'll see the
        // application has a blue toolbar. Then, without quitting the app, try
        // changing the primarySwatch below to Colors.green and then invoke
        // "hot reload" (press "r" in the console where you ran "flutter run",
        // or simply save your changes to "hot reload" in a Flutter IDE).
        // Notice that the counter didn't reset back to zero; the application
        // is not restarted.
        primarySwatch: Colors.blue,
      ),
      home: const MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({Key? key, required this.title}) : super(key: key);

  // This widget is the home page of your application. It is stateful, meaning
  // that it has a State object (defined below) that contains fields that affect
  // how it looks.

  // This class is the configuration for the state. It holds the values (in this
  // case the title) provided by the parent (in this case the App widget) and
  // used by the build method of the State. Fields in a Widget subclass are
  // always marked "final".

  final String title;

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  int _counter = 0;

  void _incrementCounter() {
    setState(() {
      // This call to setState tells the Flutter framework that something has
      // changed in this State, which causes it to rerun the build method below
      // so that the display can reflect the updated values. If we changed
      // _counter without calling setState(), then the build method would not be
      // called again, and so nothing would appear to happen.
      _counter++;
    });
  }

  @override
  Widget build(BuildContext context) {
    // This method is rerun every time setState is called, for instance as done
    // by the _incrementCounter method above.
    //
    // The Flutter framework has been optimized to make rerunning build methods
    // fast, so that you can just rebuild anything that needs updating rather
    // than having to individually change instances of widgets.
    return Scaffold(
      appBar: AppBar(
        // Here we take the value from the MyHomePage object that was created by
        // the App.build method, and use it to set our appbar title.
        title: Text(widget.title),
      ),
      body: Center(
        // Center is a layout widget. It takes a single child and positions it
        // in the middle of the parent.
        child: Column(
          // Column is also a layout widget. It takes a list of children and
          // arranges them vertically. By default, it sizes itself to fit its
          // children horizontally, and tries to be as tall as its parent.
          //
          // Invoke "debug painting" (press "p" in the console, choose the
          // "Toggle Debug Paint" action from the Flutter Inspector in Android
          // Studio, or the "Toggle Debug Paint" command in Visual Studio Code)
          // to see the wireframe for each widget.
          //
          // Column has various properties to control how it sizes itself and
          // how it positions its children. Here we use mainAxisAlignment to
          // center the children vertically; the main axis here is the vertical
          // axis because Columns are vertical (the cross axis would be
          // horizontal).
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            const Text(
              'You have pushed the button this many times:',
            ),
            Text(
              '$_counter',
              style: Theme.of(context).textTheme.headline4,
            ),
          ],
        ),
      ),
      floatingActionButton: FloatingActionButton(
        onPressed: _incrementCounter,
        tooltip: 'Increment',
        child: const Icon(Icons.add),
      ), // This trailing comma makes auto-formatting nicer for build methods.
    );
  }
}
Logs

> flutter analyze
Analyzing testapp...                                                    
No issues found! (ran in 2.0s)

> flutter doctor -v
[βœ“] Flutter (Channel beta, 2.12.0-4.2.pre, on macOS 12.3.1 21E258 darwin-arm,
    locale en-GB)
    β€’ Flutter version 2.12.0-4.2.pre at /Users/michael/Flutter
    β€’ Upstream repository https://github.com/flutter/flutter.git
    β€’ Framework revision 5c931b769b (11 days ago), 2022-03-29 10:49:29 -0500
    β€’ Engine revision 486f4a749e
    β€’ Dart version 2.17.0 (build 2.17.0-182.2.beta)
    β€’ DevTools version 2.11.1

[βœ“] Android toolchain - develop for Android devices (Android SDK version 32.0.0)
    β€’ Android SDK at /Users/michael/Library/Android/sdk
    β€’ Platform android-32, build-tools 32.0.0
    β€’ Java binary at: /Applications/Android
      Studio.app/Contents/jre/Contents/Home/bin/java
    β€’ Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
    β€’ All Android licenses accepted.

[βœ“] Xcode - develop for iOS and macOS (Xcode 13.3)
    β€’ Xcode at /Applications/Xcode.app/Contents/Developer
    β€’ CocoaPods version 1.11.2

[βœ“] Chrome - develop for the web
    β€’ Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[βœ“] Android Studio (version 2020.3)
    β€’ Android Studio at /Applications/Android Studio.app/Contents
    β€’ Flutter plugin can be installed from:
      πŸ”¨ https://plugins.jetbrains.com/plugin/9212-flutter
    β€’ Dart plugin can be installed from:
      πŸ”¨ https://plugins.jetbrains.com/plugin/6351-dart
    β€’ Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)

[βœ“] VS Code (version 1.66.1)
    β€’ VS Code at /Applications/Visual Studio Code.app/Contents
    β€’ Flutter extension version 3.38.1

[βœ“] Connected device (2 available)
    β€’ macOS (desktop) β€’ macos  β€’ darwin-arm64   β€’ macOS 12.3.1 21E258 darwin-arm
    β€’ Chrome (web)    β€’ chrome β€’ web-javascript β€’ Google Chrome 100.0.4896.75

[βœ“] HTTP Host Availability
    β€’ All required HTTP hosts are available

β€’ No issues found!

Metadata

Metadata

Assignees

Labels

P2Important issues not at the top of the work lista: error messageError messages from the Flutter frameworkdependency: dartDart team may need to help usfound in release: 2.12Found to occur in 2.12found in release: 2.13Found to occur in 2.13has reproducible stepsThe issue has been confirmed reproducible and is ready to work onplatform-webWeb applications specificallyr: fixedIssue is closed as already fixed in a newer versiontoolAffects the "flutter" command-line tool. See also t: labels.waiting for PR to land (fixed)A fix is in flight

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions