nothing happens when i join a session #21
-
i expected to see the host screen, but nothing happened, what did i do wrong? can someone tell me or is there a video tutorial? or is this bug? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 14 replies
-
|
If both of you exchanged your connection URLs and accepted the connection, it should show the screen, yes. Both of you can can try to start bananas from the terminal and see if if it spits out some useful error messages. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah did the exact steps and got nothing. Bananas never asked me which screen I wanted to share (I'm on Windows) |
Beta Was this translation helpful? Give feedback.
-
|
@BoscoDomingo, did you follow the tutorial? Did you restart the app after granting network access? What does the log output, when started via terminal? |
Beta Was this translation helpful? Give feedback.
-
|
Never got a popup to grant any permissions. I installed it for my user only using the installer, and I followed the tutorial to a T. I'll try using the terminal next time to see if I can make it work or at least get logs (it'll take a week or so as I just started my holidays) |
Beta Was this translation helpful? Give feedback.
-
|
I have the same problem (running v0.0.13) on Windows 10. The other Client to. Here is what the Terminal outputs: PS C:\Users\Steffen\AppData\Local\Programs\bananas>
(node:108624) UnhandledPromiseRejectionWarning: Error: EPERM: operation not permitted, rename 'C:\Users\Steffen\AppData\Roaming\bananas\settings.json.1338631364' -> 'C:\Users\Steffen\AppData\Roaming\bananas\settings.json'
(Use `bananas --trace-warnings ...` to show where the warning was created)
(node:108624) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:108624) UnhandledPromiseRejectionWarning: Error: EPERM: operation not permitted, rename 'C:\Users\Steffen\AppData\Roaming\bananas\settings.json.2489763602' -> 'C:\Users\Steffen\AppData\Roaming\bananas\settings.json'
(node:108624) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:108624) UnhandledPromiseRejectionWarning: Error: EPERM: operation not permitted, rename 'C:\Users\Steffen\AppData\Roaming\bananas\settings.json.167354636' -> 'C:\Users\Steffen\AppData\Roaming\bananas\settings.json'
(node:108624) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)
(node:108624) UnhandledPromiseRejectionWarning: Error: EPERM: operation not permitted, rename 'C:\Users\Steffen\AppData\Roaming\bananas\settings.json.206223596' -> 'C:\Users\Steffen\AppData\Roaming\bananas\settings.json'
(node:108624) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 4)
(node:108624) UnhandledPromiseRejectionWarning: Error: EPERM: operation not permitted, rename 'C:\Users\Steffen\AppData\Roaming\bananas\settings.json.1657275792' -> 'C:\Users\Steffen\AppData\Roaming\bananas\settings.json'
(node:108624) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 5)
(node:108624) UnhandledPromiseRejectionWarning: Error: EPERM: operation not permitted, rename 'C:\Users\Steffen\AppData\Roaming\bananas\settings.json.2879550098' -> 'C:\Users\Steffen\AppData\Roaming\bananas\settings.json'
(node:108624) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 6)
(node:108624) UnhandledPromiseRejectionWarning: Error: EPERM: operation not permitted, rename 'C:\Users\Steffen\AppData\Roaming\bananas\settings.json.2456406137' -> 'C:\Users\Steffen\AppData\Roaming\bananas\settings.json'
(node:108624) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 7)
(node:108624) UnhandledPromiseRejectionWarning: Error: EPERM: operation not permitted, rename 'C:\Users\Steffen\AppData\Roaming\bananas\settings.json.1052157541' -> 'C:\Users\Steffen\AppData\Roaming\bananas\settings.json'
(node:108624) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 8)
(node:108624) UnhandledPromiseRejectionWarning: Error: EPERM: operation not permitted, rename 'C:\Users\Steffen\AppData\Roaming\bananas\settings.json.3640098735' -> 'C:\Users\Steffen\AppData\Roaming\bananas\settings.json'
(node:108624) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 9)
(node:108624) UnhandledPromiseRejectionWarning: Error: EPERM: operation not permitted, rename 'C:\Users\Steffen\AppData\Roaming\bananas\settings.json.351115889' -> 'C:\Users\Steffen\AppData\Roaming\bananas\settings.json'
(node:108624) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 10)
(node:108624) UnhandledPromiseRejectionWarning: Error: EPERM: operation not permitted, rename 'C:\Users\Steffen\AppData\Roaming\bananas\settings.json.2052319972' -> 'C:\Users\Steffen\AppData\Roaming\bananas\settings.json'
(node:108624) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 11)
(node:108624) UnhandledPromiseRejectionWarning: Error: EPERM: operation not permitted, rename 'C:\Users\Steffen\AppData\Roaming\bananas\settings.json.881342043' -> 'C:\Users\Steffen\AppData\Roaming\bananas\settings.json'
(node:108624) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 12)
(node:108624) UnhandledPromiseRejectionWarning: Error: EPERM: operation not permitted, rename 'C:\Users\Steffen\AppData\Roaming\bananas\settings.json.4102593080' -> 'C:\Users\Steffen\AppData\Roaming\bananas\settings.json'
(node:108624) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 13)
(node:108624) UnhandledPromiseRejectionWarning: Error: EPERM: operation not permitted, rename 'C:\Users\Steffen\AppData\Roaming\bananas\settings.json.3559832144' -> 'C:\Users\Steffen\AppData\Roaming\bananas\settings.json'
(node:108624) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 14)
(node:108624) UnhandledPromiseRejectionWarning: Error: EPERM: operation not permitted, rename 'C:\Users\Steffen\AppData\Roaming\bananas\settings.json.576735084' -> 'C:\Users\Steffen\AppData\Roaming\bananas\settings.json'
(node:108624) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 15)
(node:108624) UnhandledPromiseRejectionWarning: Error: EPERM: operation not permitted, rename 'C:\Users\Steffen\AppData\Roaming\bananas\settings.json.963143865' -> 'C:\Users\Steffen\AppData\Roaming\bananas\settings.json'
(node:108624) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 16)
(node:108624) UnhandledPromiseRejectionWarning: Error: EPERM: operation not permitted, rename 'C:\Users\Steffen\AppData\Roaming\bananas\settings.json.2536215311' -> 'C:\Users\Steffen\AppData\Roaming\bananas\settings.json'
(node:108624) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 17)When using |
Beta Was this translation helpful? Give feedback.
-
|
That's the windows default folder for your apps data..
If we move it somewhere else this would mean we break the windows convention.. |
Beta Was this translation helpful? Give feedback.
-
|
I installed it without admin rights on a windows10 and it just works. You can try removing it and also remove the respective app data folder afterwards. Then just simply install it via your normal user account where you plan to use it |
Beta Was this translation helpful? Give feedback.
-
I tried is as Admin and without. I also cleared the whole Roaming banans folder. What i noticed: Moving the windows just one pixel triggers the error, and that very rapidly. Maybe it's too fast and blocks itself? EDIT: Just installed it on my Win11 Notebook (without Admin) and got the same error. |
Beta Was this translation helpful? Give feedback.
-
|
I'll try that with latest release on my win10 desktop, once I'm done with my day job; but last time I checked it was working - that said, we truly need a debounce of that settings update. Seems horribile to update the settings for every pixel move. |
Beta Was this translation helpful? Give feedback.
-
|
Continuous here: #41 |
Beta Was this translation helpful? Give feedback.
-
|
@hungdev there is a tutorial here: https://getbananas.net/tutorial |
Beta Was this translation helpful? Give feedback.
-
|
thank you, I can see my mouse now but I can't click on the host machine even though the host machine has click enabled |
Beta Was this translation helpful? Give feedback.
-
|
That's intentional for now, you as a participant, can only move your mouse around and double click to send a ping to the host. Full remote takeover is planned for v1 (keyboard and mouse), but needs some serious planning and rework, because we must be 100% sure that the host can at any point cancel the takeover with a keyboard shortcut. Otherwise it might get abused and would be a security nightmare. |
Beta Was this translation helpful? Give feedback.
-
|
hope v1 release soon <3 |
Beta Was this translation helpful? Give feedback.
-
|
You can have a look at the roadmap here: https://github.com/mistweaverco/bananas/milestones |
Beta Was this translation helpful? Give feedback.
@hungdev there is a tutorial here: https://getbananas.net/tutorial