Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KodularStarter_linux is not executing #16

Open
tykoth opened this issue Dec 13, 2023 · 5 comments
Open

KodularStarter_linux is not executing #16

tykoth opened this issue Dec 13, 2023 · 5 comments

Comments

@tykoth
Copy link

tykoth commented Dec 13, 2023

I've downloaded Linux version and chmoded +x, then tried to open executable:

./KodularStarter_linux: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory

Can you guys double check this binary?

@pavi2410
Copy link
Member

You have to install OpenSSL from apt

@tykoth
Copy link
Author

tykoth commented Dec 13, 2023 via email

@tykoth
Copy link
Author

tykoth commented Dec 15, 2023

I've installed the proper version using an old deb version and works, but now got a lot of errors on prompt and on c.kodular.io panel.

image

Error:

>> Starting companion app on device [0061115960] (Keep your phone connected via USB)Starting: Intent { act=android.intent.action.VIEW cmp=io.makeroid.companion/.Screen1 (has extras) }
Error type 3
Error: Activity class {io.makeroid.companion/io.makeroid.companion.Screen1} does not exist.

@pavi2410
Copy link
Member

I've installed the proper version using an old deb version and works, but now got a lot of errors on prompt and on c.kodular.io panel.

image

Error:

>> Starting companion app on device [0061115960] (Keep your phone connected via USB)Starting: Intent { act=android.intent.action.VIEW cmp=io.makeroid.companion/.Screen1 (has extras) }
Error type 3
Error: Activity class {io.makeroid.companion/io.makeroid.companion.Screen1} does not exist.

Do you have the Kodular Companion app installed on your phone?

@tykoth
Copy link
Author

tykoth commented Dec 17, 2023

Yes, with Kodular Companion on my phone plugged the problems changed:

Kodular Starter v2
OS: linux
ADB path: /tmp/KodularStarter/adb
- - - - - - - - - - - - - - - - - - - - - - 
Running a Vweb app on http://localhost:8004
Hit Ctrl+C to quit.
- - - - - - - - - - - - - - - - - - - - - - 
[INFO] Turn USB debugging on from the Developer Options on your phone
[INFO] Device found = ZF523M37N8
[INFO] Device found = ZF523M37N8
[INFO] Device found = ZF523M37N8
[INFO] Device found = ZF523M37N8
>> Starting companion app on device [ZF523M37N8] (Keep your phone connected via USB)8001
Starting: Intent { act=android.intent.action.VIEW cmp=io.makeroid.companion/.Screen1 (has extras) }
Warning: Activity not started, intent has been delivered to currently running top-most instance.

Achieved this:

>> Starting companion app on device [ZF523M37N8] (Keep your phone connected via USB)Starting: Intent { act=android.intent.action.VIEW cmp=io.makeroid.companion/.Screen1 (has extras) }
Warning: Activity not started, intent has been delivered to currently running top-most instance.

After ignored a lot of prompts with "internal erro" message on the app
image

image

But after a lot of insistence o got this error (must wait and cancel a lot of error messages):
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants