Closed Bug 844369 Opened 11 years ago Closed 11 years ago

Installing a packaged app with a locale override that matches the phone's locale fails with MANIFEST_MISMATCH

Categories

(Core Graveyard :: DOM: Apps, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:tef+, b2g18 affected, b2g18-v1.0.0 wontfix, b2g18-v1.0.1 affected)

RESOLVED DUPLICATE of bug 844243
blocking-b2g tef+
Tracking Status
b2g18 --- affected
b2g18-v1.0.0 --- wontfix
b2g18-v1.0.1 --- affected

People

(Reporter: jsmith, Assigned: fabrice)

References

Details

(Keywords: regression)

Build: B2G 18 2/22/2013
Device: Unagi

Steps:

1. Install "Packaged App Test Case 7" at http://mozqa.com/webapi-permissions-tests/

Expected:

The download should be successful.

Actual:

The download fails with MANIFEST_MISMATCH. Probably a fallout from bug 834515.
Blocks: app-install
blocking-b2g: --- → tef?
See Also: → 844243
Blocks: 834515
Keywords: regression
Using the locale override is a common app developer scenario so we must block on this regression. Fabrice can you start the investigation on a forward fix here or a backout if possible?
Assignee: nobody → fabrice
blocking-b2g: tef? → tef+
QA Contact: jsmith
I started testing:
I can reproduce if I do the device locale override in the mini-manifest but not in the package manifest. If both manifests have the local override, the installation works fine. How exactly did you test Jason?
(In reply to Fabrice Desré [:fabrice] from comment #2)
> I started testing:
> I can reproduce if I do the device locale override in the mini-manifest but
> not in the package manifest. If both manifests have the local override, the
> installation works fine. How exactly did you test Jason?

I used the test case in comment 0.

Mini-manifest: http://mozqa.com/webapi-permissions-tests/localeoverride.manifest

{
  "name" : "Test Locale Override",
  "version" : "1.0",
  "size" : 14000,
  "release_notes": "First v1.1 release",
  "icons": {
    "126": "/webapi-permissions-tests/qalogo.png"
  },
  "developer": {
    "name": "Mozilla QA",
    "url": "http://jasondanielsmith.wordpress.com/"
  },
  "locales": {
    "en": {
      "name": "Localized app name for English",
      "developer": {
        "name": "Localized developer name for English",
        "url": "Localized developer url for English"
      }
    },
    "pt-BR": {
      "name": "Localized app name for Brazil pt-BR",
      "developer": {
        "name": "Localized developer name for Brazil pt-BR",
        "url": "Localized developer url for Brazil pt-BR"
      }
    }
  },
  "package_path": "/webapi-permissions-tests/localeoverride.zip"
}

Packaged App: mozqa.com/webapi-permissions-tests/localeoverride.zip

Webapp manifest:

{
  "version": "1.0",
  "name": "Test Locale Override",
  "description": "A test app for testing out a locale override",
  "launch_path": "/webapi_permissions_test.html",
  "icons": {
    "128": "/webapi-permissions-tests/qalogo.png"
  },
  "type": "web",
  "permissions": {
    "geolocation": {
      "description": "Come see my geolocation"
    },
    "desktop-notification": {
      "description": "Come see my notifications"
    },
    "fmradio": {
      "description": "Come see my fmradio"
    }
  },
  "developer": {
    "name": "Mozilla QA",
    "url": "http://jasondanielsmith.wordpress.com/"
  },
  "locales": {
    "en": {
      "name": "Localized app name for English",
      "developer": {
        "name": "Localized developer name for English",
        "url": "Localized developer url for English"
      }
    },
    "pt-BR": {
      "name": "Localized app name for Brazil pt-BR",
      "developer": {
        "name": "Localized developer name for Brazil pt-BR",
        "url": "Localized developer url for Brazil pt-BR"
      }
    }
  },
  "default_locale": "es"
}
The patch in Bug 844243 fixes the issue from this case, because the root cause here is that we were modifying a manifest that we should not touch at install time.
(In reply to Fabrice Desré [:fabrice] from comment #4)
> The patch in Bug 844243 fixes the issue from this case, because the root
> cause here is that we were modifying a manifest that we should not touch at
> install time.

Okay, not surprised one bug fixes the other. I'll dupe on that and nom the other.
No longer blocks: app-install, 834515
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.