• Replies 13 replies
  • Subscribers 21 subscribers
  • Views 1873 views
  • Users 0 members are here
Options
Related

A bitmap resource matching the provided launcher icon can't be found

CK68
over 4 years ago

I don't know why but I receive the following error:

A bitmap resource matching the provided launcher icon can't be found. You must provide a bitmap resource for the launcher icon.
BUILD: com.garmin.connectiq.common.manifest.ManifestException: [102] A bitmap resource matching the provided launcher icon can't be found.
You must provide a bitmap resource for the launcher icon.

I am using the default lauchner icon and I can't remember that I have changed that.

The drawables.xml:

<drawables>
      <bitmap id="LauncherIcon" filename="launcher_icon.png" />
</drawables>

The file launcher_icon.png is in the folder drawables.

The manifest file starts with:

<!-- This is a generated file. It is highly recommended that you DO NOT edit this file. --><iq:manifest xmlns:iq="">www.garmin.com/.../connectiq" version="3">
<iq:application entry="RunningIndexApp" id="c1e8b31edeae4a9ead781859a09d5615" launcherIcon="@Drawables.LauncherIcon" minSdkVersion="2.1.0" name="@Strings.AppName" type="datafield" version="1.12.0">

  • 3 months ago in reply to flocsy🤠

    Yes, and you see that error and then fix it, is the path to the png in the xml correct?  It's a relative path, so if the xml is in the same folder as the png, all you need is the name.

    Like this for example.

    <drawables>
    <bitmap id="LauncherIcon" filename="launcher_icon.png" />
</drawables>

  • 3 months ago in reply to jim_m_58
    flocsy🤠 said:
    Add a syntax error in the xml you think it loads for the device you compile. Most probably you'll see it doesn't use that directory...
    jim_m_58 said:
    Yes, and you see that error and then fix it,

    I think you’re misunderstanding the comment you’re replying to.

    flocsy is suggesting to introduce a deliberate error in an XML file for a device where the xml launcher icon is not being loaded, in order to prove that the XML file itself is not being loaded in the first place. His guess about the problem is that the resource folder(s) are named wrong (which would cause the XML files to be ignored), not that there are errors in the XML files.

    Sure it’s possible that the PNG paths are not correct, but that’s not the point that flocsy is making. 

  • 3 months ago in reply to FlowState

    It's the next step in trying to find the problem.  It's what I'd check at least.

    What would you check after the XML you think should be used is being used?