topic Unable to replace existing app when publishing through the Hub in Management & Governance

Unable to replace existing app when publishing through the Hub

sogloqlik — Wed, 29 Jan 2025 16:21:29 GMT

Hi All,

When trying to publish an App through the hub, I do not get the "Replace existing App" checkbox although I am able to publish it. I guess It has something to with the security rules but haven't been able to find a solution so far.

Help would be appreciated.

Regards,

Re: Unable to replace existing app when publishing through the Hub

Or — Tue, 09 Jul 2024 07:04:13 GMT

Either take ownership of the published app (using QMC), or make a security rule to allow publishing for apps you don't own. By default you can't publish over an app you don't own.

Re: Unable to replace existing app when publishing through the Hub

sogloqlik — Tue, 09 Jul 2024 08:01:41 GMT

Hi,

Thank you for the answer,

The user is the owner of application and still cant replace.

Am I missing something else?

Regards,

Re: Unable to replace existing app when publishing through the Hub

Or — Tue, 09 Jul 2024 09:00:24 GMT

Presumably, or it'd work... 🙂

I'm not entirely sure here, but I think in order to republish an app you need two things on the security front:

* Publish permissions for the app/stream in question

* Update permissions on the app in question (I think on the App_* resource, possibly a specific part of it but I'm not sure which), since a republish is effectively updating an app.

Note that users with QMC access can also republish using QMC / Apps / Publish / Replace Existing App and this should (probably) work with out-of-the-box security rules.