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. Type is defined multiple time on Android
Forum Updated to NodeBB v4.3 + New Features

Type is defined multiple time on Android

Scheduled Pinned Locked Moved Unsolved Mobile and Embedded
3 Posts 2 Posters 481 Views 1 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.
  • F Offline
    F Offline
    Fausto01
    wrote on last edited by
    #1

    I made a brand new project with Qt 5.15.2, created Android templates and tried to build it: everything worked fine.
    When I add a .aar file into android/libs (the library is external, I do not have access to it) I get the error

    Type org.qtproject.qt5.android.bearer.QtNetworkReceiver$1 is defined multiple times
    

    What can it be?

    Axel SpoerlA 1 Reply Last reply
    0
    • F Fausto01

      I made a brand new project with Qt 5.15.2, created Android templates and tried to build it: everything worked fine.
      When I add a .aar file into android/libs (the library is external, I do not have access to it) I get the error

      Type org.qtproject.qt5.android.bearer.QtNetworkReceiver$1 is defined multiple times
      

      What can it be?

      Axel SpoerlA Offline
      Axel SpoerlA Offline
      Axel Spoerl
      Moderators
      wrote on last edited by
      #2

      @Fausto01
      Looks like a duplicated symbol.
      Maybe the external library is statically linked to Qt.

      Software Engineer
      The Qt Company, Oslo

      F 1 Reply Last reply
      0
      • Axel SpoerlA Axel Spoerl

        @Fausto01
        Looks like a duplicated symbol.
        Maybe the external library is statically linked to Qt.

        F Offline
        F Offline
        Fausto01
        wrote on last edited by
        #3

        @Axel-Spoerl I don't know why, but upgrading android-31 to android-34 solved the problem

        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