Can't submit app due to 'only one app per domain is allowed'

RESOLVED WONTFIX

Status

Marketplace
General
RESOLVED WONTFIX
5 years ago
5 years ago

People

(Reporter: Lim Chee Aun, Unassigned)

Tracking

x86_64
Windows 8
Points:
---

Details

(Reporter)

Description

5 years ago
I tried to submit my app, which is hosted on GitHub Pages, but got stuck at Step 2 where it says "An app already exists on this domain; only one app per domain is allowed.". I do have another app that's already listed on Firefox Marketplace, which is also hosted on GitHub Pages.

The problem I think is that my apps are on 'cheeaun.github.com' with different sub-folders for each app. That's basically how GitHub Pages work. I expected that I should still be able to submit another app but this error shows that anyone can only submit *one* out of all their GitHub-hosted apps?
The one-app-per-origin restriction is documented in the manifest FAQ:
https://marketplace.firefox.com/developers/docs/manifest_faq

Check out the question "Can I have more than one app at my origin?".

So no, you cannot host more than one app on the same domain (more precisely, at the same origin).

However, there is a great workaround. Github pages support CNAMEs:
https://help.github.com/articles/setting-up-a-custom-domain-with-pages

This means if you have your own domain name "example.com", then you can create subdomains like this:
- "oneofmyapps.example.com" and point it to your first app on github pages
- "anotherapp.example.com" and point it to your second app on GH pages
- and so on.

There was a blog post on Mozilla Hacks recently, which also outlines this technique (subsection "Release to the public"):
https://hacks.mozilla.org/2012/11/hacking-firefox-os/

Hope this helps!
Thanks Fred.  Lim, unfortunately this is a limitation of the current v1 system and something we're looking to address in future versions.  For now though, this is a wontfix (or, really, a cantfix).
Status: UNCONFIRMED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.