You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Testing out the Android Agent, I noticed several issues relating to user consent/notification that I think need to be addressed.
When connecting to an Android device via the Desktop tab, it doesn't tell you that you're "Waiting for user to grant access..." like it does when connecting to a desktop PC, it just shows a "Connected" status with nothing showing in the area where the remote view should be.
If you tap "Cancel" to deny the request to capture the screen, it doesn't disconnect, it still shows the "Connected" status and a blank remote view.
If when connecting, you allow the screen capture, then in the Android Agent's menu tap "Stop Screen Sharing" (on a side note, I think this should not be hidden in a menu, it should be on the main screen, just like the connect/disconnect button) it continues to show that it's "Connected" and the remote view freezes (presumably because the agent isn't sending new data for it). [I'd guess this is related to the previous issue.]
The above issues with consent/notification when viewing the Android device's display remotely are things that I think should be fixed to improve the user experience, but next there are some bigger issues, because of their potential for remote actions to go unseen when MeshCentral's settings are set to notify or require consent from the user:
If the user checked the "Don't show again" box during a previous remote viewing of their display, they will never again receive a request for their consent to view their display. [The Agent should pop to the front, but it doesn't tell them why.]
Using the Files tab to remotely view/modify the file system doesn't notify or request the consent of the user in any way, no matter what the User Consent/Notification settings are set to.
The text was updated successfully, but these errors were encountered:
Testing out the Android Agent, I noticed several issues relating to user consent/notification that I think need to be addressed.
[I'd guess this is related to the previous issue.]
The above issues with consent/notification when viewing the Android device's display remotely are things that I think should be fixed to improve the user experience, but next there are some bigger issues, because of their potential for remote actions to go unseen when MeshCentral's settings are set to notify or require consent from the user:
[The Agent should pop to the front, but it doesn't tell them why.]
The text was updated successfully, but these errors were encountered: