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. Android build now fails (used to work)
Forum Updated to NodeBB v4.3 + New Features

Android build now fails (used to work)

Scheduled Pinned Locked Moved Solved Mobile and Embedded
23 Posts 4 Posters 3.6k Views 2 Watching
  • 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.
  • JoeCFDJ JoeCFD

    @mzimmers said in Android build now fails (used to work):

    the build process is trying to remove that file in the first place

    This file at the place is a copy of the one you setup. Every time it has to be replaced in build because it may be changed. This is reasonable.

    mzimmersM Offline
    mzimmersM Offline
    mzimmers
    wrote on last edited by
    #11

    @JoeCFD OK, but where is the original file? It isn't from my project android folder -- that file is different, and has a different datestamp. Where is the file coming from?

    JoeCFDJ 1 Reply Last reply
    0
    • mzimmersM mzimmers

      @JoeCFD OK, but where is the original file? It isn't from my project android folder -- that file is different, and has a different datestamp. Where is the file coming from?

      JoeCFDJ Offline
      JoeCFDJ Offline
      JoeCFD
      wrote on last edited by JoeCFD
      #12

      @mzimmers AndroidManifest.xml is an important file and located normally under android dir. Qt gives the flexibility for the user to put it anywhere and it can be set in qmake or cmake file with path. But it has a fixed location in build dir and is a copy of the one you set-up. For example,mine is under buildfiles/android

      mzimmersM 1 Reply Last reply
      0
      • JoeCFDJ JoeCFD

        @mzimmers AndroidManifest.xml is an important file and located normally under android dir. Qt gives the flexibility for the user to put it anywhere and it can be set in qmake or cmake file with path. But it has a fixed location in build dir and is a copy of the one you set-up. For example,mine is under buildfiles/android

        mzimmersM Offline
        mzimmersM Offline
        mzimmers
        wrote on last edited by
        #13

        @JoeCFD Here's the complete error messaging:

        Can't remove old file: C:/Users/Michael.Zimmers/Qt_projects/build-nga_demo-Android_Qt_6_4_2_Clang_arm64_v8a-Release/android-build/AndroidManifest.xml
        16:17:05: The process "C:\Qt\6.4.2\mingw_64\bin\androiddeployqt.exe" exited with code 3.
        Error while building/deploying project nga_demo (kit: Android Qt 6.4.2 Clang arm64-v8a)
        When executing step "Build Android APK"
        

        Code 3 is "the system cannot find the specified path" which makes no sense, as that path is definitely there.

        JoeCFDJ 1 Reply Last reply
        0
        • mzimmersM mzimmers

          @JoeCFD Here's the complete error messaging:

          Can't remove old file: C:/Users/Michael.Zimmers/Qt_projects/build-nga_demo-Android_Qt_6_4_2_Clang_arm64_v8a-Release/android-build/AndroidManifest.xml
          16:17:05: The process "C:\Qt\6.4.2\mingw_64\bin\androiddeployqt.exe" exited with code 3.
          Error while building/deploying project nga_demo (kit: Android Qt 6.4.2 Clang arm64-v8a)
          When executing step "Build Android APK"
          

          Code 3 is "the system cannot find the specified path" which makes no sense, as that path is definitely there.

          JoeCFDJ Offline
          JoeCFDJ Offline
          JoeCFD
          wrote on last edited by JoeCFD
          #14

          @mzimmers can you copy your xml file to the place? Then it will be available. If it is read only, build will not work either.

          mzimmersM 1 Reply Last reply
          0
          • JoeCFDJ JoeCFD

            @mzimmers can you copy your xml file to the place? Then it will be available. If it is read only, build will not work either.

            mzimmersM Offline
            mzimmersM Offline
            mzimmers
            wrote on last edited by
            #15

            @JoeCFD I've tried that. No luck. It gets replaced with the "mystery version."

            Regarding permissions: here's what Windows thinks:
            windows.PNG

            BUT: This from a MINGW64 window:
            ming.PNG

            So...I truly don't know what's going on.

            JoeCFDJ KenAppleby 0K 2 Replies Last reply
            0
            • mzimmersM mzimmers

              @JoeCFD I've tried that. No luck. It gets replaced with the "mystery version."

              Regarding permissions: here's what Windows thinks:
              windows.PNG

              BUT: This from a MINGW64 window:
              ming.PNG

              So...I truly don't know what's going on.

              JoeCFDJ Offline
              JoeCFDJ Offline
              JoeCFD
              wrote on last edited by JoeCFD
              #16

              @mzimmers It could be a Qt bug in qtcreator as well although it may not be. Otherwise, there will be more people who will complain. Check write permissions of all parent dirs of build dir. You can see gradle stuff and xml file will be copied there every time in build. Check out how to set permissions for the whole dir. I am not in the office and can not check the build commands of QtCreator.

              mzimmersM 1 Reply Last reply
              0
              • JoeCFDJ JoeCFD

                @mzimmers It could be a Qt bug in qtcreator as well although it may not be. Otherwise, there will be more people who will complain. Check write permissions of all parent dirs of build dir. You can see gradle stuff and xml file will be copied there every time in build. Check out how to set permissions for the whole dir. I am not in the office and can not check the build commands of QtCreator.

                mzimmersM Offline
                mzimmersM Offline
                mzimmers
                wrote on last edited by
                #17

                @JoeCFD doubtful that it's a Qt bug -- this used to work, and I haven't updated lately.

                I copied my project to a different folder - same result.

                Weird, huh?

                JoeCFDJ 1 Reply Last reply
                0
                • mzimmersM mzimmers

                  @JoeCFD doubtful that it's a Qt bug -- this used to work, and I haven't updated lately.

                  I copied my project to a different folder - same result.

                  Weird, huh?

                  JoeCFDJ Offline
                  JoeCFDJ Offline
                  JoeCFD
                  wrote on last edited by
                  #18

                  @mzimmers It is a Windows problem. Somehow, the write permissions of build dir are gone.

                  mzimmersM 1 Reply Last reply
                  0
                  • JoeCFDJ JoeCFD

                    @mzimmers It is a Windows problem. Somehow, the write permissions of build dir are gone.

                    mzimmersM Offline
                    mzimmersM Offline
                    mzimmers
                    wrote on last edited by
                    #19

                    @JoeCFD said in Android build now fails (used to work):

                    @mzimmers It is a Windows problem. Somehow, the write permissions of build dir are gone.

                    Hmm...I did update Windows recently. Aargh...fortunately, I'm getting a Linux box soon.

                    I wonder if this is worth reporting...

                    JoeCFDJ 1 Reply Last reply
                    0
                    • mzimmersM mzimmers

                      @JoeCFD said in Android build now fails (used to work):

                      @mzimmers It is a Windows problem. Somehow, the write permissions of build dir are gone.

                      Hmm...I did update Windows recently. Aargh...fortunately, I'm getting a Linux box soon.

                      I wonder if this is worth reporting...

                      JoeCFDJ Offline
                      JoeCFDJ Offline
                      JoeCFD
                      wrote on last edited by
                      #20

                      @mzimmers Linux Box? A virtual machine is OK as well.

                      piervalliP 1 Reply Last reply
                      0
                      • JoeCFDJ JoeCFD

                        @mzimmers Linux Box? A virtual machine is OK as well.

                        piervalliP Offline
                        piervalliP Offline
                        piervalli
                        wrote on last edited by piervalli
                        #21

                        @JoeCFD
                        Have you checked in the release of Qt 6.4.1, the minum version of SDK and ndk Android?

                        Java version?
                        Last try to move the project in c:\data\ , so the path is more short of under users, I remember a bug with long path

                        1 Reply Last reply
                        0
                        • mzimmersM mzimmers

                          @JoeCFD I've tried that. No luck. It gets replaced with the "mystery version."

                          Regarding permissions: here's what Windows thinks:
                          windows.PNG

                          BUT: This from a MINGW64 window:
                          ming.PNG

                          So...I truly don't know what's going on.

                          KenAppleby 0K Offline
                          KenAppleby 0K Offline
                          KenAppleby 0
                          wrote on last edited by
                          #22

                          @mzimmers More arbitrary thoughts:

                          • Are the contents of the "mystery version" the same as the one in your Qt6.4 installation, which would be in c:/Qt/Qt6.4.2/android_arm64_v8a/src/android/templates/AndroidManifest.xml or somewhere similar?
                            It may be that during the build process Qt copies the default template version to the build directory first, then overwrites it with your project version. If this is the case, it would be worth looking at the permissions on the file in the Qt templates directory.

                          • Try creating yourself a new Windows user (I would say one without the "." in the pathname) and building the project afresh from there.

                          • And another possible thing to try is to completely uninstall Qt and reinstall.

                          mzimmersM 1 Reply Last reply
                          1
                          • KenAppleby 0K KenAppleby 0

                            @mzimmers More arbitrary thoughts:

                            • Are the contents of the "mystery version" the same as the one in your Qt6.4 installation, which would be in c:/Qt/Qt6.4.2/android_arm64_v8a/src/android/templates/AndroidManifest.xml or somewhere similar?
                              It may be that during the build process Qt copies the default template version to the build directory first, then overwrites it with your project version. If this is the case, it would be worth looking at the permissions on the file in the Qt templates directory.

                            • Try creating yourself a new Windows user (I would say one without the "." in the pathname) and building the project afresh from there.

                            • And another possible thing to try is to completely uninstall Qt and reinstall.

                            mzimmersM Offline
                            mzimmersM Offline
                            mzimmers
                            wrote on last edited by
                            #23

                            @KenAppleby-0 said in Android build now fails (used to work):

                            It may be that during the build process Qt copies the default template version to the build directory first, then overwrites it with your project version. If this is the case, it would be worth looking at the permissions on the file in the Qt templates directory.

                            Bingo. I'd recently set my Qt folder to readonly in order to protect against inadvertent overwrites. This was indeed the culprit. I reinstalled 6.4.2 and I can build now. (I have a deployment problem, but I'll bring that up in a separate topic.)

                            Thanks to everyone who helped with this.

                            1 Reply Last reply
                            1
                            • mzimmersM mzimmers has marked this topic as solved on

                            • Login

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