webosbrew / dev-manager-desktop

Device/DevMode Manager for webOS TV
Apache License 2.0
1.22k stars 79 forks source link

An error during app installation: Type error #89

Closed geoL86 closed 1 year ago

geoL86 commented 1 year ago

Hello community, I got this error "Failed to install: Type error " during app installation, who can help to understand is that a bug on software or miscounfiguration/versions/compatability?

webOS: 6.3.2 F/W: 3.34.70 webos Dev Manager: 1.10.1

01 02
mariotaku commented 1 year ago

Hi, this should be some bugs in the app. I'm working on a new version to fix that.

have-a-boy commented 1 year ago

As far as I know, there was a recent update of the WebOS developer mode app that stopped the WebOS OSE CLI package from working with actual WebOS TVs. The automatic refresh of developer mode also seems to have changed and doesn't work anymore. I've since had to switch to using the separate WebOS CLI package for TVs from LGs developer website for building and installing apps. It uses the exact same CLI syntax, but actually works for physical WebOS systems.

I'm guessing this is related.

mariotaku commented 1 year ago

Hi, for version 1.9 and above, webOS OSE CLI was not used anymore, so it should be other issues. Please try v1.11.5, it should work better across TV versions.

geoL86 commented 1 year ago

Hi @mariotaku , I tried starting from v1.11.5 to v1.11.8 - unsuccessfully, the same error "Type error". Even more, I observe new type of errors related to ssh, like: SSH_MSG_DISCONNECT: packet corrupt, etc ...

mariotaku commented 1 year ago

Could you try this snapshot and open the Safari inspector by right clicking in the app window? It will give you some logs when there are errors.

ztepsa commented 1 year ago

Could you try this snapshot and open the Safari inspector by right clicking in the app window? It will give you some logs when there are errors.

Hi all, I can confirm that the snapshot fixed the issues mentioned above.

My TV is using webOS 3.9.0, and with both versions 1.10.1 and 1.11.9 I run into same issues described above after webos developer app update. When using snapshot I do not see any errors in the web console and app works as expected.

It seems that there were no fixes between snapshot and latest release, so I would expect also 1.11.9 to work, but it did not, maybe some cache issue between reinstalls?

If you need any more info I'd be glad to help 👍

mariotaku commented 1 year ago

@ztepsa Hi, this is very interesting as there should be no feature difference between snapshot and v1.11.9. But if you tried on v1.11.9, I can catch some error logs as it shipped with error reporting tool.

Do you have the homebrew channel installed? How did you install the app?

SMJ93 commented 1 year ago

I get the same issue when trying to install an ipk on version 1.11.10. Downloaded the dev manager from GitHub releases.

If I use ares CLI it installs the app as expected:

ares-install --device lgtv myapp_1.0.0_all.ipk
geoL86 commented 1 year ago

@mariotaku I tried package from snapshot and the latest one as well (1.11.13) - result the same but belive that node will produce informative traceses on sentry _)

tomyummmm commented 1 year ago

Hi, I am on 1.11.17 and got this error trying to install Homebrew app when connecting to my 2023 model of TV, I think it has to do with the CLI requirement of 1.12.4 and newer for the TV. Could you update this? Thank you.

odu14ick commented 1 year ago

Can confirm I am still experiencing this on 1.11.18 version against 03.11.54 version of LG 55g3

odu14ick commented 1 year ago

Update: installing the new CLI and setting the env var seemed to help fix the issue. Not sure at which step exactly it got resolved, but I tried installing my app with the CLI, failed, came back and voi-la - the Dev Manager started working.

Don't take my words for granted, maybe the issue is something else entirely - it's just the only intended change that I did.

UPD: I've just encountered this again, and installing didn't work (even with the newest CLI installed, etc) until I went to Terminal tab and opened a shell. Once I've done that - everything started working.

Yeah2333 commented 11 months ago

Hi, i am on 1.12.1. And when install, this type error still happen.