Cannot upload new click, got multiple origins error

[Penk Chen]

I'm uploading a new click package "dropbox.canonicalpartners_1.0_armhf.click" to store using <email address hidden> account.

Expected result: click upload without problem

Actual result: got following error while uploading:

    Can not create a new package with name dropbox, multiple origins for dropbox are not allowed.

[Shawn Wang (shawn111)]

<nessita> shawn111, right, I understand, but we try very hard to have our SCA code base as uniform as possible for click/old snap/new snap
<nessita> shawn111, so we try to avoid as much as possible to handle "special cases"
<nessita> shawn111, and the dropbox in particular is not a snap but a click
<nessita> and all clicks will have to be migrated to snap new
<nessita> where the name can not be shared by more than one account (at least during series 16)
<shawn111> nessita, yes,,, I see.
<shawn111> nessita, but because some projects are on 15.10
<shawn111> nessita, I will check with penk if possible to use snap
<nessita> shawn111, so I synced with kyleN today, about this issue
<nessita> shawn111, and the agreement with him is that the click for dropbox will be renamed to something else
<nessita> shawn111, because in click the package name is never shown to the user
<nessita> shawn111, so, the package can be named dropbox-scope (for example)
<nessita> and the title be Dropbox
<nessita> and users will see only Dropbox in searches
* thomi -> breakfast
<nessita> shawn111, does that make sense?
<shawn111> nessita, yes... change name is a good way
<shawn111> nessita, sounds good
<shawn111> nessita, thanks :)

[Penk Chen (penk)]

Hi, thanks for the log, we have renamed our package to dropboxcp.canonicalpartners to workaround this issue.

From our team's point of view:

- We're building click packages, and we don't have a time frame to migrate to new snap package because it's not in the phone system yet.

- appid.namespace1 and appid.namespace2 are two different click packages according to current design, this issue could still happen in the foreseeable future

So we really hope this issue can be resolved while the codebase remains unified, consider that we've got new click packages yet to release.