Welcome to the ConnectWise View Bug Report Forum
If you do not have an account, click "Sign in/ Sign up" to get started.
ConnectWise View gives a knowledgeable expert the ability to connect to a field tech's or customer's mobile device camera. Ultimately, these "experts" will be able to see what's going on and assist the technician/customer without having to travel offsite.
Below are a few tips and rules for those who wish to participate, please read through them.
- Search for an existing bug report before adding your own. This helps us prevent duplicate entries and improve bug tracking.
- If you find a matching bug report, give it a thumbs up and throw in a comment with more details about the problem.
- If you can't find a request for an item you need, create your own bug report.
- Provide as many details as you can, especially:
- Platform (iOS, Android, etc.)
- Connection (WiFi or Mobile Data)
- Mobile device OS, model, etc.
- Browser(s) used
- No spam, advertising, or self-promotion.
- No offensive posts, links, or images.
- Only one request per post.
- Administrators have the ability to moderate the forums, including editing, deleting, and moving posts. Posts may be deleted for any reason, with or without notification.
Thank you for sharing your thoughts with us!
Connectwise view until a few days ago had a feature to text the URL to the client. Now it only gives option to email and copy URL
There's an issue with mobile carriers filtering text messages from View, resulting in end users not receiving text messages. We've removed the text message invitation option until it is resolved.
More on the issue here: https://docs.connectwise.com/ConnectWise_View_Documentation/Technical_bulletins/Not_receiving_text_messages_from_ConnectWise_View
When I try setting up ConnectWise Control View, it does not work on S20s. I get an error message "Error requesting your camera/microphone: Could not Start video source". I get the same error message on chrome, edge and samsung internet.I have in each app allowed permissions for camera and microphone but i have no luck. i tried this with multiple s20's and they have the same issue. It works on our s10's and iphones. My s20 is up to date and i have restarted my phone multiple times. I also tried wiping the cached partition. I am registering an external Bug report on this issue. So when devs create the internal issue, support can have them link it.
I can launch ConnectWise View from my browser (option is available), however other users inside of my ConnectWise Console cannot (No Option Available). What permission level does a user need to create a View Session? It would be nice to have a toggle box for this permission so it can be assigned to non-technical user accounts that just need this feature.
I'm assuming you are using ConnectView with Automate? If this is the case, this issue has been fixed with the launch of the ConnectWise View integration with ConnectWise Automate.
Whenver I take a snapshot, the video feed freezes both on the operator's side and the cameraperson's side.
Then, after a few moments, the operator's screen shows "negotiating connection with cameraperson".
Then, after that, "the cameraperson has left the session" even though the smartphone browser shows it's still streaming (albeit frozen).
So, ultimately, taking a snapshot terminates the feed.
Edit #1: I've done more testing and it appears that taking colorful snapshots freezes the feed, but taking bland ones does not.
By "bland" I mean something like the image I've attached at the bottom of this post.
The smartphone is an iPhone 11 on the latest iOS using Safari.
Edit #2: After more testing, it seems I can take snapshots without any hitches if I switch to low resolution.
So I should redefine the bug as: "on the default high resolution, taking all but the most bland snapshots freezes the feed".
Good Morning Connectwise devs!
There is a current issue/bug of which the Connectwise Clients are showing as offline in the control panel despite the device being online and when the customer checks the client is sat "Waiting for your host".
There is currently no option for the client to be refreshed on the customer end and the reinstall option or the wake option tries to contact the machine but nothing happens. The only way around it is to perform a temporary session with the customer and to manually reinstall the client which isn't ideal.
I know there was a Bitdefender issue a little while ago which was resolved which the software inadvertently removed the client from the host machine however this has been resolved for sometime now.
I have had this happen across 10 different devices on different networks over the space of two weeks which leads me to believe there's an bug or an issue somewhere with the client.
Would you kindly be able to test this and as a suggestion for a future feature add an option for the customer to refresh the application on the customer end please?
Thank you for your time with this.
We are running version 19.3.24708.7130.
When we connect to a session if someone is already logged into that box it locks the account. Not log off or sign off. It just locks the computer. This happens on Windows 10 PC's. These are W10 devices that are added to the domain. Im wondering if there is a setting on admin that I am just missing. Any help would be appreciated.
"chat did not take place during this session" time entry created in Connectwise when using link to control a client
I don't see a bug here listed even though Connectwise support in ticket 13970359 told me it would be in the system and to check here for an update.
Every time the control button is used to start a new session on a configuration within the connectwise app a new time entry, created as billable time is added to the Connectwise ticket with the text of "Chat does not exist"
This ends up with the potential for double billing the client due to the additional time entry that is created for the session length. Instead our techs have to review their time entries for the day, open every time entry and hit delete. A slow process that could involve many time entries a day.
Has happened since an update in September 2019 update
Does anyone else have this issue?
Customer support service by UserEcho