This article includes a list of all of the known issues in RealVNC Server for Mobile.
Device Access & On-Demand Assist
Android & iOS
- It is not possible to start a new RealVNC Connect session from the system menu. Users must start the session using the RealVNC Server app.
- When starting a new broadcast from another app while a RealVNC Connect session is active, it does not stop the RealVNC Connect session. The RealVNC Server app needs to be restarted once the non-RealVNC Server broadcast has ended.
- If the device has no internet connectivity when the RealVNC Server app is launched, connections are not possible. The RealVNC Server app needs to be restarted once internet connectivity is restored.
- On tablets, when the RealVNC Server app is started in landscape and switched to portrait, it is not possible to switch back to portrait.
- Active RealVNC Connect sessions are ended when the device goes to sleep, or the screen is locked.
- Connected RealVNC Viewer users are not informed when the broadcast is paused.
- Sending logs from the app to RealVNC Technical Support requires the iOS Mail app to be installed.
Device Access Only
- If the RealVNC Server app encounters an error when joining a Team, it may lead to the app using On-Demand Assist mode. System administrators should confirm they are applying a valid cloud connectivity token.
- Sending logs from the app to RealVNC Technical Support requires an email app to be available in the Android Work Profile.
- If RealVNC Server tries to join a team that has no capacity for new devices it does not retry automatically. The RealVNC Server app needs to be restarted once capacity has been made available in the Team.
- If notifications have not been enabled in iOS' Settings, Notifications, Screen Sharing, users will not be able to receive push notifications to accept or reject incoming connections.