On manually installed apps, it might be better to disable the update button

[zbalkan]

Hi,

This affects local development only but also, until external app stores feature gets released, it would affect externally developed apps in production as well. When an app is installed via the uploaded zip file, it's better not to have an update button at all -or a disabled button.

What do you think?

[ShreyasZare]

Thanks for the post. The "Update" button for all apps allow you to manually update the app using an app zip file. When an app installed via the app store has an update, another button called "Store Update" is available to manually trigger update from the store.

[zbalkan]

Hi, yes, I meant store update, my bad. This issue occurred due to the name conflict between in-tree LogExporterApp and my for of LogExporterApp. Should I rename my fork then?

[ShreyasZare]

Oh ok. The current App design is very simple and is not able to distinguish difference between manually installed apps and store installed apps.

The external app store plan is to have separate "namespace" kind of implementation so that an app named in one store does not get affected by another app with the same name from another store. There, the manually installed apps would have their own separate namespace. So the issue you see now will eventually get fixed.

Right now, what you can do is just have a app's name renamed when you install it so that it does not match with the one in the app store. May be you can have something like "Log Exported v2" to help distinguish it for now.

[zbalkan]

Yep. Renaming is the simplest path. I'll find something. Thanks.

[zbalkan]

Renamed as discussed https://github.com/DeltaZulu-OU/LogForwarderApp