Skip to content

master channel build throws fatal error on calling flutter run #39729

Closed
@ghost

Description

@ghost

Hi team

first post here,

Channel: master
Engine version: e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94

See attachment for log
e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.log

Steps

c:\Projects\desktop>flutter channel master
Switching to flutter channel 'master'...
git: Your branch is up to date with 'origin/master'.
git: Switched to branch 'master'

c:\Projects\desktop>flutter channel master
Checking Dart SDK version...
Downloading Dart SDK from Flutter engine e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94...
Unzipping Dart SDK...
Building flutter tool...
Running pub upgrade...
Switching to flutter channel 'master'...
git: Your branch is up to date with 'origin/master'.
git: Already on 'master'

Flutter doctor

command flutter doctor

[√] Flutter (Channel master, v1.9.8-pre.54, on Microsoft Windows [Version 10.0.18362.10013], locale en-US)

[√] Android toolchain - develop for Android devices (Android SDK version 29.0.1)
[√] Visual Studio - develop for Windows (Visual Studio Community 2019 16.2.3)
[√] Android Studio (version 3.4)
[√] VS Code, 64-bit edition (version 1.37.1)
[√] Connected device (2 available)

• No issues found!

Logs

command flutter run

Running "flutter pub get" in desktop...                             2.0s
Launching lib\main.dart on PH 1 in debug mode...
Initializing gradle...                                              0.9s
Resolving dependencies...                                           4.2s
[Fatal Error] arm64_v8a_debug-1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.pom:8:10: Already seen doctype.
[Fatal Error] arm64_v8a_debug-1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.pom:8:10: Already seen doctype.
[Fatal Error] arm64_v8a_debug-1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.pom:8:10: Already seen doctype.
[Fatal Error] x86_64_debug-1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.pom:8:10: Already seen doctype.
[Fatal Error] x86_64_debug-1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.pom:8:10: Already seen doctype.
[Fatal Error] x86_64_debug-1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.pom:8:10: Already seen doctype.
[Fatal Error] x86_debug-1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.pom:8:10: Already seen doctype.
[Fatal Error] x86_debug-1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.pom:8:10: Already seen doctype.
[Fatal Error] x86_debug-1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.pom:8:10: Already seen doctype.
[Fatal Error] flutter_embedding_debug-1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.pom:8:10: Already seen doctype.
[Fatal Error] flutter_embedding_debug-1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.pom:8:10: Already seen doctype.
[Fatal Error] flutter_embedding_debug-1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.pom:8:10: Already seen doctype.

FAILURE: Build failed with an exception.

* What went wrong:
Could not resolve all files for configuration ':app:debugCompileClasspath'.
> Could not resolve io.flutter:flutter_embedding_debug:1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.
  Required by:
      project :app
   > Could not resolve io.flutter:flutter_embedding_debug:1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.
      > Could not parse POM http://download.flutter.io/io/flutter/flutter_embedding_debug/1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94/flutter_embedding_debug-1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.pom
         > Already seen doctype.
   > Could not resolve io.flutter:flutter_embedding_debug:1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.
      > Could not parse POM http://download.flutter.io/io/flutter/flutter_embedding_debug/1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94/flutter_embedding_debug-1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.pom
         > Already seen doctype.
   > Could not resolve io.flutter:flutter_embedding_debug:1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.
      > Could not parse POM http://download.flutter.io/io/flutter/flutter_embedding_debug/1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94/flutter_embedding_debug-1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.pom
         > Already seen doctype.
> Could not resolve io.flutter:arm64_v8a_debug:1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.
  Required by:
      project :app
   > Could not resolve io.flutter:arm64_v8a_debug:1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.
      > Could not parse POM http://download.flutter.io/io/flutter/arm64_v8a_debug/1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94/arm64_v8a_debug-1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.pom
         > Already seen doctype.
   > Could not resolve io.flutter:arm64_v8a_debug:1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.
      > Could not parse POM http://download.flutter.io/io/flutter/arm64_v8a_debug/1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94/arm64_v8a_debug-1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.pom
         > Already seen doctype.
   > Could not resolve io.flutter:arm64_v8a_debug:1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.
      > Could not parse POM http://download.flutter.io/io/flutter/arm64_v8a_debug/1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94/arm64_v8a_debug-1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.pom
         > Already seen doctype.
> Could not resolve io.flutter:x86_debug:1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.
  Required by:
      project :app
   > Could not resolve io.flutter:x86_debug:1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.
      > Could not parse POM http://download.flutter.io/io/flutter/x86_debug/1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94/x86_debug-1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.pom
         > Already seen doctype.
   > Could not resolve io.flutter:x86_debug:1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.
      > Could not parse POM http://download.flutter.io/io/flutter/x86_debug/1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94/x86_debug-1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.pom
         > Already seen doctype.
   > Could not resolve io.flutter:x86_debug:1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.
      > Could not parse POM http://download.flutter.io/io/flutter/x86_debug/1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94/x86_debug-1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.pom
         > Already seen doctype.
> Could not resolve io.flutter:x86_64_debug:1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.
  Required by:
      project :app
   > Could not resolve io.flutter:x86_64_debug:1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.
      > Could not parse POM http://download.flutter.io/io/flutter/x86_64_debug/1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94/x86_64_debug-1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.pom
         > Already seen doctype.
   > Could not resolve io.flutter:x86_64_debug:1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.
      > Could not parse POM http://download.flutter.io/io/flutter/x86_64_debug/1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94/x86_64_debug-1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.pom
         > Already seen doctype.
   > Could not resolve io.flutter:x86_64_debug:1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.
      > Could not parse POM http://download.flutter.io/io/flutter/x86_64_debug/1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94/x86_64_debug-1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.pom
         > Already seen doctype.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 12s
Running Gradle task 'assembleDebug'...
Running Gradle task 'assembleDebug'... Done                        13.1s
Gradle task assembleDebug failed with exit code 1

Activity

added
t: gradle"flutter build" and "flutter run" on Android
toolAffects the "flutter" command-line tool. See also t: labels.
on Sep 3, 2019
crazygo

crazygo commented on Nov 27, 2019

@crazygo

I changed channel from dev to beta, and got this error too

kwizner

kwizner commented on Feb 3, 2020

@kwizner

The error still occurs.

[Fatal Error] arm64_v8a_debug-1.0.0-a67792536ca236a971d0efbcfd7af4efb8f6c119.pom:1:44: Content is not allowed in prolog.
[Fatal Error] x86_debug-1.0.0-a67792536ca236a971d0efbcfd7af4efb8f6c119.pom:1:44: Content is not allowed in prolog.
[Fatal Error] flutter_embedding_debug-1.0.0-a67792536ca236a971d0efbcfd7af4efb8f6c119.pom:1:44: Content is not allowed in prolog.
[Fatal Error] x86_64_debug-1.0.0-a67792536ca236a971d0efbcfd7af4efb8f6c119.pom:1:44: Content is not allowed in prolog.
[Fatal Error] x86_64_debug-1.0.0-a67792536ca236a971d0efbcfd7af4efb8f6c119.pom:1:44: Content is not allowed in prolog.
[Fatal Error] arm64_v8a_debug-1.0.0-a67792536ca236a971d0efbcfd7af4efb8f6c119.pom:1:44: Content is not allowed in prolog.
[Fatal Error] flutter_embedding_debug-1.0.0-a67792536ca236a971d0efbcfd7af4efb8f6c119.pom:1:44: Content is not allowed in prolog.
[Fatal Error] x86_debug-1.0.0-a67792536ca236a971d0efbcfd7af4efb8f6c119.pom:1:44: Content is not allowed in prolog.
[Fatal Error] x86_64_debug-1.0.0-a67792536ca236a971d0efbcfd7af4efb8f6c119.pom:1:44: Content is not allowed in prolog.
[Fatal Error] arm64_v8a_debug-1.0.0-a67792536ca236a971d0efbcfd7af4efb8f6c119.pom:1:44: Content is not allowed in prolog.
[Fatal Error] x86_debug-1.0.0-a67792536ca236a971d0efbcfd7af4efb8f6c119.pom:1:44: Content is not allowed in prolog.
[Fatal Error] flutter_embedding_debug-1.0.0-a67792536ca236a971d0efbcfd7af4efb8f6c119.pom:1:44: Content is not allowed in prolog.
 > Could not resolve io.flutter:flutter_embedding_debug:1.0.0-a67792536ca236a971d0efbcfd7af4efb8f6c119.
         > Could not parse POM http://download.flutter.io/io/flutter/flutter_embedding_debug/1.0.0-a67792536ca236a971d0efbcfd7af4efb8f6c119/flutter_embedding_debug-1.0.0-a67792536ca236a971d0efbcfd7af4efb8f6c119.pom
            > Content is not allowed in prolog.
Loaimohamed79

Loaimohamed79 commented on Feb 5, 2020

@Loaimohamed79

anyone solve it ??

christopher2012

christopher2012 commented on Feb 5, 2020

@christopher2012

nope, problem on Mac and Windows.

jonahwilliams

jonahwilliams commented on Feb 7, 2020

@jonahwilliams
Contributor

If you're still having this issue please, please, please include the version of flutter you are on!

Otherwise, can you confirm that the POM file is actually downloadable, for example - curl http://download.flutter.io/io/flutter/flutter_embedding_debug/1.0.0-a67792536ca236a971d0efbcfd7af4efb8f6c119/flutter_embedding_debug-1.0.0-a67792536ca236a971d0efbcfd7af4efb8f6c119.pom > foo.txt and check if it is there?

added
waiting for customer responseThe Flutter team cannot make further progress on this issue until the original reporter responds
on Feb 7, 2020
kwizner

kwizner commented on Feb 10, 2020

@kwizner

@jonahwilliams POM file is downloadable. I can see the content in file.

There is no error on beta channel for me, but it's difficult to work with production code when I have diiffrent channel.

elcijcampeador

elcijcampeador commented on Feb 12, 2020

@elcijcampeador

Similar issue! Just started today.

flutter doctor

Flutter 1.15.4-pre.26 • channel master • https://github.com/flutter/flutter.git
Framework • revision b9ecebf101 (54 minutes ago) • 2020-02-12 10:58:02 -0800
Engine • revision e4f46f32f1
Tools • Dart 2.8.0 (build 2.8.0-dev.8.0 fd992e423e)

Flutter Upgrade

Upgrading engine...
Downloading Android Maven dependencies...                       
Failed to download the Android dependencies
Downloading Android Maven dependencies...                           5.0s
Downloading android-arm-profile/linux-x64 tools...                 12.8s
Downloading android-arm-release/linux-x64 tools...                 14.0s
Downloading android-arm64-profile/linux-x64 tools...               14.7s
Downloading android-arm64-release/linux-x64 tools...               14.2s
Downloading android-x64-profile/linux-x64 tools...                 15.2s
Downloading android-x64-release/linux-x64 tools...                 11.6s
Downloading android-x86 tools...                                   67.0s
Downloading android-x64 tools...                                   90.2s
Downloading android-arm tools...                                   74.3s
Downloading android-arm-profile tools...                           30.3s
Downloading android-arm-release tools...                           25.8s
Downloading android-arm64 tools...                                 93.0s
Downloading android-arm64-profile tools...                         35.5s
Downloading android-arm64-release tools...                         18.9s
Downloading android-x64-profile tools...                           42.2s
Downloading android-x64-release tools...                           24.2s
Downloading android-x86-jit-release tools...                       36.1s
Downloading package sky_engine...                                   4.1s
Downloading flutter_patched_sdk tools...                           34.4s
Downloading flutter_patched_sdk_product tools...                   44.0s
Downloading linux-x64 tools...                                    148.8s (!)
Downloading linux-x64/font-subset tools...                          9.5s

Flutter 1.15.4-pre.26 • channel master • https://github.com/flutter/flutter.git
Framework • revision b9ecebf101 (54 minutes ago) • 2020-02-12 10:58:02 -0800
Engine • revision e4f46f32f1
Tools • Dart 2.8.0 (build 2.8.0-dev.8.0 fd992e423e)

Running flutter doctor...
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, v1.15.4-pre.26, on Linux, locale en_US.UTF-8)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 3.5)
[✓] Connected device (3 available)

• No issues found!

Debug Console

Launching lib/main.dart on Android SDK built for x86 in debug mode...
[Fatal Error] flutter_embedding_debug-1.0.0-e4f46f32f1fd00872bf19e226ba43ef71e4a84a4.pom:1:44: Content is not allowed in prolog.
[Fatal Error] flutter_embedding_debug-1.0.0-e4f46f32f1fd00872bf19e226ba43ef71e4a84a4.pom:1:44: Content is not allowed in prolog.
[Fatal Error] flutter_embedding_debug-1.0.0-e4f46f32f1fd00872bf19e226ba43ef71e4a84a4.pom:1:44: Content is not allowed in prolog.
[Fatal Error] flutter_embedding_debug-1.0.0-e4f46f32f1fd00872bf19e226ba43ef71e4a84a4.pom:1:44: Content is not allowed in prolog.
[Fatal Error] flutter_embedding_debug-1.0.0-e4f46f32f1fd00872bf19e226ba43ef71e4a84a4.pom:1:44: Content is not allowed in prolog.
[Fatal Error] flutter_embedding_debug-1.0.0-e4f46f32f1fd00872bf19e226ba43ef71e4a84a4.pom:1:44: Content is not allowed in prolog.

FAILURE: Build failed with an exception.

* What went wrong:
Could not determine the dependencies of task ':app:compileDebugJavaWithJavac'.
> Could not resolve all task dependencies for configuration ':app:debugCompileClasspath'.
   > Could not resolve io.flutter:flutter_embedding_debug:1.0.0-e4f46f32f1fd00872bf19e226ba43ef71e4a84a4.
     Required by:
         project :app
      > Could not resolve io.flutter:flutter_embedding_debug:1.0.0-e4f46f32f1fd00872bf19e226ba43ef71e4a84a4.
         > Could not parse POM http://download.flutter.io/io/flutter/flutter_embedding_debug/1.0.0-e4f46f32f1fd00872bf19e226ba43ef71e4a84a4/flutter_embedding_debug-1.0.0-e4f46f32f1fd00872bf19e226ba43ef71e4a84a4.pom
            > Content is not allowed in prolog.
      > Could not resolve io.flutter:flutter_embedding_debug:1.0.0-e4f46f32f1fd00872bf19e226ba43ef71e4a84a4.
         > Could not parse POM http://download.flutter.io/io/flutter/flutter_embedding_debug/1.0.0-e4f46f32f1fd00872bf19e226ba43ef71e4a84a4/flutter_embedding_debug-1.0.0-e4f46f32f1fd00872bf19e226ba43ef71e4a84a4.pom
            > Content is not allowed in prolog.
      > Could not resolve io.flutter:flutter_embedding_debug:1.0.0-e4f46f32f1fd00872bf19e226ba43ef71e4a84a4.
         > Could not parse POM http://download.flutter.io/io/flutter/flutter_embedding_debug/1.0.0-e4f46f32f1fd00872bf19e226ba43ef71e4a84a4/flutter_embedding_debug-1.0.0-e4f46f32f1fd00872bf19e226ba43ef71e4a84a4.pom
            > Content is not allowed in prolog.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 38s
Gradle task assembleDebug failed with exit code 1
Exited (sigterm)
P4ulSZ

P4ulSZ commented on Feb 14, 2020

@P4ulSZ

Was anyone able to fix this problem?

aquilarafa

aquilarafa commented on Feb 18, 2020

@aquilarafa
  • clean gradle cache
  • run 'flutter precache'

24 remaining items

Loading
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    t: gradle"flutter build" and "flutter run" on AndroidtoolAffects the "flutter" command-line tool. See also t: labels.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @talhakosen@christopher2012@umbatoul@jonahwilliams@crazygo

        Issue actions

          master channel build throws fatal error on calling flutter run · Issue #39729 · flutter/flutter