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

Can’t get further than ./CarPlay.AppImage #54

Open
e1isev opened this issue Nov 20, 2023 · 12 comments
Open

Can’t get further than ./CarPlay.AppImage #54

e1isev opened this issue Nov 20, 2023 · 12 comments

Comments

@e1isev
Copy link

e1isev commented Nov 20, 2023

I get the error
elise@raspberrypi:~/Desktop $
• /CarpLay.AppImage
A Javascript error uccurred In the main process
Uncaught Exception:
Error: No native build was found for platform=linux arch=arm runtime=electron abi fault libc=glibe node=18.17.1 electron=27.0.4|
Loaded from: /tmp/.mount_CarplaoLKjo2/resources/app.asar/node modules/usb at load.resolve. Load.path/tmp/.mount_CarplaolKjo2/resources/app.asar/node_modules/node-gyp-b
u1 ld/node-gyp-build.js: 60:9)
at load (/tmp/.mount_CarplaolKj02/resources/app.asar/node_modules/node-gyp-build/node-gyp-buil
d.js: 22:30)
at Object. (/tmp/.mount_CarplaolKjo2/resources/app.asar/node_modules/usb/dist/usb/b
indings.js:8:38
at Module. compile (node:internal/modules/cjs/loader: 1271:14) at Object..js (node:internal/modules/cjs/loader:1326:10)

@rhysmorgan134
Copy link
Owner

Hi, can you share what Raspberry OS version you are running (bullseye vs buster) which device type (pi3, 4 or 5) and whether it is 64bit or 32 bit?

@e1isev
Copy link
Author

e1isev commented Nov 20, 2023

I've got a Raspberry pi 2B, Could that be my issue?
32bit
bullseye

@rhysmorgan134
Copy link
Owner

Possibly, it may be that the 32 bit version is broken, let me rebuild one tomorrow, you can try some of the previous versions if you want

@e1isev
Copy link
Author

e1isev commented Nov 21, 2023

I tried version 4.0.1 using the method here
And got the same error

@eVisper
Copy link

eVisper commented Dec 6, 2023

I am getting the same error, was running v3.0.0 just fine and upgraded to v4.0.2 and got the same error. So I deleted v4.0.2 and went back to v3.0.0 and am still getting the error when it was previously working.

Running on a 4b with Pi OS.

@rhysmorgan134
Copy link
Owner

Are you running on 64 or 32 bit OS?

Also is it bookworm or bullseye?

@eVisper
Copy link

eVisper commented Dec 6, 2023

32 bit/bullseye.

@eVisper
Copy link

eVisper commented Dec 6, 2023

Not sure what changed, but v3.0.0 is working again now.

@e1isev
Copy link
Author

e1isev commented Dec 7, 2023

I have also got it working on the v3.0.0

@rhysmorgan134
Copy link
Owner

Looks like I need to do a new build for 32bit, thanks for the feedback guys.

@bacca11
Copy link

bacca11 commented Jan 12, 2024

Thanks for contributing to this really cool App. I'm looking forward to getting it running on my system.

When I run it I get the following result in terminal:
With React-Carplay version 3:
acca11@raspberrypi:~/Desktop $ ./Carplay.AppImage
/home/bacca11/.config/ReactCarplay
spawning carplay {
dpi: 240,
nightMode: 0,
hand: 0,
boxName: 'nodePlay',
width: 800,
height: 600,
fps: 30
}
directory found
sending dpi
device connected and ready
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
../../buildtools/third_party/libc++/trunk/include/vector:1425: assertion __n < size() failed: vector[] index out of bounds[8340:0112/122700.568002:ERROR:gpu_process_host.cc(991)] GPU process exited unexpectedly: exit_code=6
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
[8429:0112/122703.278951:ERROR:shared_image_manager.cc(202)] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox.
../../buildtools/third_party/libc++/trunk/include/vector:1425: assertion __n < size() failed: vector[] index out of bounds[8385:0112/122703.592759:ERROR:command_buffer_proxy_impl.cc(325)] GPU state invalid after WaitForGetOffsetInRange.
[8340:0112/122703.607304:ERROR:gpu_process_host.cc(991)] GPU process exited unexpectedly: exit_code=6
[8385:0112/122703.651546:ERROR:command_buffer_proxy_impl.cc(128)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
../../buildtools/third_party/libc++/trunk/include/vector:1425: assertion __n < size() failed: vector[] index out of bounds[8340:0112/122706.280048:ERROR:gpu_process_host.cc(991)] GPU process exited unexpectedly: exit_code=6
14 0.51375 0.8966666666666666
15 0.5125 0.8966666666666666
16 0.5125 0.8966666666666666
[8385:0112/122708.756171:ERROR:command_buffer_proxy_impl.cc(128)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
14 0.5075 0.8433333333333334
15 0.50625 0.8383333333333334
16 0.50625 0.8383333333333334



I'm running on Raspberry Pi 2B; 32-bit Raspian Bullseye.
I'm running React-Carplay 3.0.1 to get a 32-bit version of the app.
Dongle is CarlinKit CPC200-CCPA which has the USB attributes listed as Bus 001 Device 008: ID 1314:1521 Magic Communication Tec. Auto Box.

On the display I see the React-Carplay white screen with, "Connect iPhone to begin CarPlay" displayed.

I'm not sure what to do next to get CarPlay to display. My phone connects to the dongle fine, but no Carplay.
I see in the terminal notes above that the device is connected and ready, but there are failures to retrieve data from the device. Is this potentially due to the newer CPC200-CCPA dongle not being properly registered in the code of the app?
What would you suggest I try next?

@MrDude82
Copy link

MrDude82 commented Apr 5, 2024

Looks like I need to do a new build for 32bit, thanks for the feedback guys.

hi Rhys,

you just have New build?

Thanks

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

5 participants