Driver works via `app run` but not via `app install`?

Developers
1

So I have weird issue, I’m experimenting with custom app and one of my drivers just refuses to “load” when used with install but works perfectly fine with run.
What I mean by that is that I cannot enter the pairing process because the driver seems to be forever loading in the browser, and I cannot “click” it to move forward. It’s the first view after selecting the app (before entering onPairListDevices).

When I set up device with the app executed via run and then install the app, then the result is that the device shows “app unavailable”.

What’s super strange is that I have two drivers, and only one behaves like that. The second one works perfectly in both cases. It’s also possible to add a device to an app executed with run, and then it works with install, too (and the other way around, too).

There are 0 logs in the app that would allow me to debug that issue further, and I’m somewhat stuck.

Does anyone have any ideas?

2

Use homey app run --remote

1 Like
3

Oh man… thanks :slight_smile:

1 Like
4

YW! Afaik it’s not mentioned in the “how to build an app manual”.

The introduction of Homey Cloud introduced this flag, to be able to develop on a docker image (as far as I know).

Imho they should"ve turned it around: homey app run --local for Docker development and homey app run for any physical Homey.

5

Agree, also kinda surprise for me that the normal run is not fully isolated even though it’s also docker based env… it’s some room for improvement for sure.

I honestly skipped the cloud part of introduction as … well I’m not using cloud but local with pro so… :smiley:

6

Yea haha, I think we all skip what’s not needed :stuck_out_tongue:

The flag is not mentioned in here, it even didn’t make it to ‘Useful commands’:

1000046671
10000466711080×1774 254 KB

Doesn’t homey --help show it?