I would like to upgrade my month license to a lifetime license, but I can't seem to find a way to do this. Any help would be great.

There's no upgrade. Simply cancel your monthly license, and when it expires, purchase the lifetime license.

Please generate another bug report with the error too.

These logs indicate some kind of firewall or vpn, is that the case?

3.2.20

3.3.20

This should be fixed, please verify.

This should be fixed, please verify.

Yeah you can just download and install the Vysor apk here manually.

https://github.com/koush/release

Can you try checking again on the latest version?

Can you try checking again on the latest version?

Hello, I do not know anything about Programming or anything about this, but I presented this error when installing the desktop application and I need some help since I did not find another place for technical support.

When I open the installer it downloads as usual but just in the middle of it, it stops and immediately the next error pops up.

I add that when the error appears it gives you the option of Open Setup Log and when you click it opens the following File

SquirrelSetup.log

I also tried the Vysor from the Google chrome browser but I get the following error and I don't know how to fix it...

note: I speak Spanish. all this I put in the google translator, sorry if it is somewhat misinformed or etc.

Unsure, but that looks like an old version of windows. Use the issue template.

I have done every step regarding this problem that were shown on the website. Are there any other steps I should try to do for fixing the issue?

use the issue template.

I remotely shared my device, we are able to view/control device using chrome browser from remote PC. But we couldn't pull the logs and push the APK remotely. Please let us know if that is possible using Vysor tool.

I remotely shared my device, we are able to view/control device using chrome browser from remote PC. But we couldn't pull the logs and push the APK remotely. Please let us know if that is possible using Vysor tool.

You can use adb logcat. Vysor's desktop connections create an adb connection.

This was part of the reason I managed to run into this bug: I assumed the underlying pipeline would be zero copy (as that's something I strive towards for performance reasons). Ie, the ArrayBuffer I pass in belongs to the decoder until the call returns.

Similar to Android's MediaCodec's management of input/output buffers that are queued/dequeued.

I'll take a look.

Please ensure you are connected to the internet. It's failing to fetch the server, and then falling back to the packaged apk (which has a bug). I'll fix the latter bug shortly.

Try this prerelease pacman build.

https://github.com/koush/vysor.io/releases/tag/v3.2.19

I don't a arch VM set up yet to test it, just did a build and am crossing my fingers. I'll be able to do a proper test/build once I do full update for all the other platforms.

if you're savvy enough, take a look at electron-builder's supported packages and let me know if there's one I can use for Arch.

https://www.electron.build/

All platforms: 7z, zip, tar.xz, tar.lz, tar.gz, tar.bz2, dir (unpacked directory).
macOS: dmg, pkg, mas, mas-dev.
Linux: AppImage, snap, debian package (deb), rpm, freebsd, pacman, p5p, apk.
Windows: nsis (Installer), nsis-web (Web installer), portable (portable app without installation), AppX (Windows Store), Squirrel.Windows.

I just installed Vysor by building it from the AUR, and it isn't launching at all. This is the output I'm getting when I try to launch it from a terminal:

I do not provide the AUR, I did build a snap and appimage. This AUR actually seems to be hosting an extremely dated version of Vysor as well. (2.x, whereas Vysor is at 3.x right now)

I am that footgun user. In my head, EncodedVideoChunk seemed like a simple dictionary object (which is why I modified post creation), but I guess more is happening under the hood there.

Thanks, I finally reproduced your underlying issue.

In the meantime, instead of pasting the link into the browser clicking "Open WIth Vysor" when prompted, click "Connect Network Device" and paste in the link.

Looks like it got saved in a buggy state, so resetting it and then allowing it to update may resolve it. Though it should also automatically clear bad settings now too.

Thanks, I found further issues in your logs that may be addressed by 3.2.14.

credentials [object Promise]
credentials/listening error Error: Missing gcm object in credentials

Describe the bug When clicking 'view' in Vysor for my Samsung Galaxy S7 I get the following message after it attempts to connect "Error Connecting to Android Device......Error: apk path failed (empty)"

I was able to connect for many days last week after first purchasing Vysor. Today Vysor was updated after it suggested to relaunch it, and now I can not connect to the phone anymore

Attach a Vysor Bug Report Log Bug report was created

To Reproduce Steps to reproduce the behaviour:

1. Open Vysor
2. Vysor suggests relaunching application for the latest version.
3. Connect Samsung Galaxy S7 phone via USB
4. Click 'View' button beside the SM G930F. It attempts to connect but produces an error
5. Click 'Wifi' button beside the SM G930F. It attempts to connect but produces an error

Expected behaviour As it has done previously it should be able to connect to the phone and show its display in the separate window

Screenshots

Desktop (please complete the following information):

• OS: MacOS Mojave 10.14.3
• Vysor Version: 3.2.13

Android (please complete the following information):

• Device: Samsung Galaxy S7 / SM G930F
• OS: Android version 8.0.0 / Samsung Experience version 9.0
• Vysor Bug Report Link: https://gist.github.com/VysorLogs/8815b20ebff5cce6ceeb8325d658f5dd

Android Logcat I am not familiar

Additional context This worked fine last week for many days until Vysor was updated today

Your device is out of space.

web apk installation result: Error: android.os.ParcelableException: java.io.IOException: Requested internal only, but not enough space

Please ensure the both the share server and the client are at the latest version of Vysor (3.2.13 as of a few minutes ago)

please click reload to update to 3.2.13 as well.

you did not generate a bug report. i need that.

Thanks for testing. I've added more logging and fixed some race conditions around the new push channel. Can you try again on 3.2.13?

Please verify the fix in 3.2.11.

Click reset Vysor. It should trigger an update to version 3.3.x

Initial investigation shows that GAE is starting to fail after around 3000 concurrent connections. This is a result of a server migration to GAE from my own physical infrastructure.

I'll need to modernize the push transport to use Web Push where available, and also improve the existing socket.io service.

Might take a day or two.

Fixing.

Try setting the quality to low then high to see if it triggers an update.

I need a generated bug report. Again, use the template.

After last update of vysor (to 3.2.5) quality is very bad. Even on HIGH quality settings (logged in) image is very bad. It takes even 20 seconds until image is cleared out slowly. Previously image was "instantly" at high quality. Looks like now image is highly compressed and over time it getting better quality. Is there a way to run older version? This one is unusable :// Attached is how screen looks like after change (left) and 20 seconds later (right)

Use the bug report template. This does not have enough information.

Investigating.

Describe the bug I was working on my Android device, counting on the resolution consistency. But to my surprise after a certain restart of the software, the resolution was completely mixed up (I was making sure the setting were identical) and I realised an update took place behind the scene.

First, why the update is forced and not by choice? second, why the update have anything to do with the resolution?

There was a bug where the default resolution was incorrect and forced to 25%. This caused a lot of low resolution devices to fail altogether. The bug fix actually reverted it to the correct and original behavior.

Oh, i see. Vysor's events aren't generating touches. Those touch indicators may be happening prior injection. This would need to be a whole new feature.

duplicate of https://github.com/koush/vysor.io/issues/507

are you on a laptop or some system that has multiple monitors? The window somehow ended up off screen and the position was saved there. I'll fix this. In the meantime, clicking "reset" and logging back in will resolve this issue.

Describe the bug Unable to connect to Android device over Network. This previously worked fine on the previous Vysor build.

Attach a Vysor Bug Report Log https://gist.github.com/165f170a4be7e0d6d15a97a406103aa4 165f170a4be7e0d6d15a97a406103aa4-7e1235c581345085e46763bd9e69872ecac3d9c6.zip

Expected behavior Previously able to connect to Android device and view what is displayed.

Screenshots

Desktop (please complete the following information):

• OS: Windows
• Vysor Version 3.1.2

The WebSocket VerifyError has been fixed and this should be resolved.

When making screen recordings, I usually turn on the Show taps setting in Developer Options so that the viewer can see where I'm clicking.

When interacting with my device through Vysor though, clicks from my computer don't show the tap indicator.

The indicator does show (and gets captured in Vysor's screen recording) when I interact with my phone's actual touchscreen though.

Is it possible to either

• somehow treat Vysor click events as taps so Android's built-in option captures them, or
• build a setting similar to Show taps into Vysor itself?

There is an adb shell command to do this: https://stackoverflow.com/questions/49056918/how-to-enable-show-touches-developer-option-from-adb-shell

Then use the "shell" custom action to trigger it.

https://stackoverflow.com/questions/49056918/how-to-enable-show-touches-developer-option-from-adb-shell

I'm a bit concerned that ongoing notifications (like downloads or playback) will spam the Desktop.

Describe the bug When the "international keyboard" option is turned on in the Vysor main window, every time an app is opened on the phone a notification is sent to the PC per the attached image. This is because there is an ongoing notification on the phone for the keyboard. If you can have Vysor ignore this specific notification that would make things a lot less disturbing. A workaround would be to disable this notification on the phone, but it's not an ideal solution.

No bug report to attach this is a not a bug, as Vysor seems to be configured to send ALL notification from the phone to the PC (including ongoing persistent notifications which are needed to alert of incoming calls)

To Reproduce Steps to reproduce the behavior:

1. enable the international keyboard option in the main app.
2. Connect to a device and start opening apps that require keyboard input.

Screenshots If applicable, add screenshots to help explain your problem.

I've fixed this by preventing Vysor from spamming those keyboard notifications.

Can you confirm this bug still happens? I fixed another related bug involving text encoding. https://github.com/koush/vysor.io/issues/623

Describe the bug When a none English notification comes in (Hebrew in case), Vysor does not display the letter correctly (See image)

Bug report: https://gist.github.com/9db3b56ba37b76774599ebc3ef63bbd1

To Reproduce Steps to reproduce the behavior:

1. Receive a notification that does not contact English letter.
2. It does not display properly.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Windows 10
• Vysor Version 3.2.0

Android (please complete the following information):

• Device: Samsung Note 20 Ultra
• OS: Android 10

Good bug report. I fixed this in 3.2.3.

Currently notifications are short lived, and not synced (ie, dismissed from phone to android, etc).

As you noted, regular calls do not seem to use the notification API and use a system alert or something. Need to look into this in a future feature.

Describe the bug When the "international keyboard" option is turned on in the Vysor main window, every time an app is opened on the phone a notification is sent to the PC per the attached image. This is because there is an ongoing notification on the phone for the keyboard. If you can have Vysor ignore this specific notification that would make things a lot less disturbing. A workaround would be to disable this notification on the phone, but it's not an ideal solution.

No bug report to attach this is a not a bug, as Vysor seems to be configured to send ALL notification from the phone to the PC (including ongoing persistent notifications which are needed to alert of incoming calls)

To Reproduce Steps to reproduce the behavior:

1. enable the international keyboard option in the main app.
2. Connect to a device and start opening apps that require keyboard input.

Screenshots If applicable, add screenshots to help explain your problem.

Fixed in 3.2.2 by removing ongoing notifications. I'll need to revisit ongoing notifications in the future, as the desktop UX is meant for temporary ones, depending on host OS (mac/linux).

I'll filter out ongoing notifications, thanks for the report.

It's implemented. Please open new issues as you find bugs.

Describe the bug A clear and concise description of what the bug is.

Attach a Vysor Bug Report Log

1. First, trigger the bug.
2. Leave the window with the bug open. Do not close it, or the bug data will be lost.
3. To generate a bug report, open the main device window if it is not open already. Click the Bug Report button along the bottom. Please note that this will contain your email address. This is necessary for diagnosing licensing/purchase issues.
4. ISSUES WITHOUT BUG REPORTS MAY BE IMMEDIATELY CLOSED. The bug report contains internal logging from the app.

To Reproduce Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. MacOS]
• Vysor Version [e.g. 2.2.2]

Android (please complete the following information):

• Device: [e.g. Pixel 4]
• OS: [e.g. Android 10]
• Vysor Bug Report Link: [instructions follow, you must attach a bug report that contains the application errors and logging]

Android Logcat If you are familiar with adb logcat, please include the log output of any crashes to this issue.

Additional context Add any other context about the problem here.

Could you please develop a small great fonction as , the "Vysor" app up to all others windows as soon as a phone call is received on the phone ? I m a french user , sorry for my poor english, but i think it could be a good idea to have an option "always on top" BUT only for incoming phone call.

Thank you.

Alain

https://twitter.com/vysorapp/status/1304952083578150912

It looks like your card is inactive anyways, and the subscription is set to cancel regardless.

What happens when you click it? Can you get me the javascript console log? And another screenshot after clicking it?

Can you provide a screenshot of the red button?

I'll try leaving the international running for a while and see if it repros after some time.

So I'm trying to mirror my phone in nba 2k20 then I realize the audio still not working when you using recording on phone. So I decided to use OBS then realize I can't transfer the audio in obs so is just the same.

The screen doesn't fit to on the obs maybe on my screen monitor I'm using 1920x1080 on pc