Skip to content

Webapp Manifest icons are generated with invalid paths #1179

Closed

Description

@Splaktar
  1. Mac OS-X El Capitan
  2. Versions.
    angular-cli: 1.0.0-beta.6
    node: 4.4.3
    os: darwin x64
  3. Repro steps.
    ng new myApp --mobile
  4. The log given by the failure.
    N/A.
  5. Mention any other details that might be useful.
    The icon section of the manifest currently generated by the angular-cli looks like this:
  "icons": [
    {
            "src": "/android-chrome-36x36.png",
            "sizes": "36x36",
            "type": "image/png",
            "density": 0.75
        },
        {
            "src": "/android-chrome-48x48.png",
            "sizes": "48x48",
            "type": "image/png",
            "density": 1
        },
        {
            "src": "/android-chrome-72x72.png",
            "sizes": "72x72",
            "type": "image/png",
            "density": 1.5
        },
        {
            "src": "/android-chrome-96x96.png",
            "sizes": "96x96",
            "type": "image/png",
            "density": 2
        },
        {
            "src": "/android-chrome-144x144.png",
            "sizes": "144x144",
            "type": "image/png",
            "density": 3
        },
        {
            "src": "/android-chrome-192x192.png",
            "sizes": "192x192",
            "type": "image/png",
            "density": 4
        }
  ],

This doesn't work since the icons are bundled into dist/icons and not just in dist/. To fix this, it needs to define the icon src like this:

   "icons": [
    {
            "src": "icons/android-chrome-36x36.png",
            "sizes": "36x36",
            "type": "image/png"
        },
        {
            "src": "icons/android-chrome-48x48.png",
            "sizes": "48x48",
            "type": "image/png"
        },
        {
            "src": "icons/android-chrome-72x72.png",
            "sizes": "72x72",
            "type": "image/png"
        },
        {
            "src": "icons/android-chrome-96x96.png",
            "sizes": "96x96",
            "type": "image/png"
        },
        {
            "src": "icons/android-chrome-144x144.png",
            "sizes": "144x144",
            "type": "image/png"
        },
        {
            "src": "icons/android-chrome-192x192.png",
            "sizes": "192x192",
            "type": "image/png"
        }
  ],

Activity

  1. added 2 commits that reference this issue on Jun 23, 2016
    05b6dcc
    da154ad
  2. added
    P1Impacts a large percentage of users; if a workaround exists it is partial or overly painful
    on Jul 4, 2016
  3. added 3 commits that reference this issue on Jul 31, 2016
    3e623f5
    04dc080
    5fd5476
  4. added a commit that references this issue on Aug 12, 2016
    cc5e9ad
  5. angular-automatic-lock-bot commented on Sep 6, 2019

    @angular-automatic-lock-bot

    This issue has been automatically locked due to inactivity.
    Please file a new issue if you are encountering a similar or related problem.

    Read more about our automatic conversation locking policy.

    This action has been performed automatically by a bot.

  6. locked and limited conversation to collaborators on Sep 6, 2019
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

    P1Impacts a large percentage of users; if a workaround exists it is partial or overly painfultype: bug/fix

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions