Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Mobile and Embedded
  4. Warning: Additionally, the fallback loader failed to parse the XML

Warning: Additionally, the fallback loader failed to parse the XML

Scheduled Pinned Locked Moved Unsolved Mobile and Embedded
9 Posts 3 Posters 9.9k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • WasifW Offline
    WasifW Offline
    Wasif
    wrote on last edited by
    #1

    0

    While setting up Android environment in Qt, the following warning pops up:

    Warning: Additionally, the fallback loader failed to parse the XML.

    I already had a well setup and running Android environment. I upgraded to Qt 6.7 recently and tried to run application in already installed Emulator as well as actual android device. The application dies right before the launch of debugger. So I decided to remove and reinstall Android component of Qt, JDK, SDK and its system images. Doing so produces the above warning and application dies as usual.

    Qt version - 6.7, JDK version - 17, SDK version - 25.1.8937393 & 26.1.10909125

    I have tried installing system images of different APIs and deleting the cache folder of Qt.XWLL2Kdc.png

    1 Reply Last reply
    0
    • Axel SpoerlA Offline
      Axel SpoerlA Offline
      Axel Spoerl
      Moderators
      wrote on last edited by
      #2

      NDK version 26.1.0909125 is definitively supported and works for me.
      Looks like a broken NDK installation. Have you tried re-installing the NDK?

      Software Engineer
      The Qt Company, Oslo

      WasifW 1 Reply Last reply
      0
      • Axel SpoerlA Axel Spoerl

        NDK version 26.1.0909125 is definitively supported and works for me.
        Looks like a broken NDK installation. Have you tried re-installing the NDK?

        WasifW Offline
        WasifW Offline
        Wasif
        wrote on last edited by
        #3

        @Axel-Spoerl I have tried reinstalling everything. Rolled back to Qt Creator 12.0.2 version and Qt 6.6.3. All the old and working environment settings were acquired. JDK version 17 was reinstalled from Oracle before reinstalling SDK and NDK. But the issue persists.

        1 Reply Last reply
        0
        • Axel SpoerlA Offline
          Axel SpoerlA Offline
          Axel Spoerl
          Moderators
          wrote on last edited by
          #4

          I can see an OpenSSL issue in the background of the error log.
          Please resolve that first and see, if the error persists when done.

          Software Engineer
          The Qt Company, Oslo

          WasifW 2 Replies Last reply
          0
          • Axel SpoerlA Axel Spoerl

            I can see an OpenSSL issue in the background of the error log.
            Please resolve that first and see, if the error persists when done.

            WasifW Offline
            WasifW Offline
            Wasif
            wrote on last edited by
            #5

            @Axel-Spoerl
            I think that would do nothing as this setup (OpenSSL) is done at very last of setting up SDK. In the very first steps of managing Android settings comes setting up JDK location, Android SDK location and then downloading the essentials including cmdline-tools and NDK. This also shows the same warning. Downloading the OpenSSL binaries comes after this. But I'll give it a go and post the result.

            Capture.PNG

            1 Reply Last reply
            0
            • Axel SpoerlA Axel Spoerl

              I can see an OpenSSL issue in the background of the error log.
              Please resolve that first and see, if the error persists when done.

              WasifW Offline
              WasifW Offline
              Wasif
              wrote on last edited by Wasif
              #6

              @Axel-Spoerl
              As suspected.

              32d44601-d62d-44cd-80a6-c3910bd501f0-image.png

              1 Reply Last reply
              0
              • Axel SpoerlA Offline
                Axel SpoerlA Offline
                Axel Spoerl
                Moderators
                wrote on last edited by
                #7

                Hm, that's really weird and I can't reproduce that on Windows, macOS or Linux.
                So I can't offer more than trial and error. Can you launch an application via Android Studio?

                Software Engineer
                The Qt Company, Oslo

                1 Reply Last reply
                0
                • WasifW Offline
                  WasifW Offline
                  Wasif
                  wrote on last edited by Wasif
                  #8

                  @Axel-Spoerl
                  All the Android environment I have is just on Qt Creator. I don't have Android Studio.

                  1 Reply Last reply
                  0
                  • C Offline
                    C Offline
                    Cajus Pollmeier
                    wrote on last edited by
                    #9

                    I've the same warnings - the final build works fine, though.

                    The message comes from com.android.repository.impl.manager.RemoteRepoLoaderImpl. According to the source, there's a loop that should output a list of errors, but it seems to be empty. No idea what exactly causes this yet.

                    1 Reply Last reply
                    0

                    • Login

                    • Login or register to search.
                    • First post
                      Last post
                    0
                    • Categories
                    • Recent
                    • Tags
                    • Popular
                    • Users
                    • Groups
                    • Search
                    • Get Qt Extensions
                    • Unsolved