Ario.Paxaz Posted April 8 Posted April 8 Hello How should I troubleshoot UniGUI Touch on mobile devices? Regards.
Sherzod Posted April 8 Posted April 8 47 minutes ago, Ario.Paxaz said: How should I troubleshoot UniGUI Touch on mobile devices? Hello, One of the ways to troubleshoot on mobile is by using Chrome Developer Tools. You can connect your Android device via USB and use chrome://inspect in your desktop Chrome to inspect and debug the page opened on your phone. It allows you to view console logs, network activity, layout issues, and more — just like on desktop. If you’re not familiar with it, you can Google something like "Chrome remote debugging Android" — there are many helpful guides online.
Ario.Paxaz Posted April 8 Author Posted April 8 1 hour ago, Sherzod said: desktop Chrome to inspect and debug The address of the page opened on the mobile was displayed, but when I click inspect, the HTTP/1.1 404 Not Found page is displayed. But if I click Close, the page closes on mobile. Is there anything else I need to do? Regards.
Ario.Paxaz Posted April 8 Author Posted April 8 11 minutes ago, Sherzod said: Does the desktop version work (without /m)? I don't understand what you mean.
Ario.Paxaz Posted April 8 Author Posted April 8 20 minutes ago, Sherzod said: Does the desktop version work (without /m)? If you mean desktop applications, yes, desktop applications run without problems at http://172.22.1.176:8077/ or http://localhost:8077/
Sherzod Posted April 8 Posted April 8 7 minutes ago, Ario.Paxaz said: I don't understand what you mean. Run the sample desktop application on the device and check.
Ario.Paxaz Posted April 8 Author Posted April 8 1 minute ago, Sherzod said: Run the sample desktop application on the device and check. Yes, the desktop app ran on mobile.
Ario.Paxaz Posted April 8 Author Posted April 8 inspect for the desktop application also gave this message, the HTTP/1.1 404 Not Found page is displayed. But if I click Close, the page closes on mobile.
Sherzod Posted April 8 Posted April 8 Thanks — that helps clarify. Since the page is open and visible in chrome://inspect, but inspect gives a 404, it's likely a DevTools issue (version mismatch or rendering failure). You can try one of these: 1. Click “inspect fallback” instead of “inspect” (if available) 2. Update Chrome on your desktop to match the version on your mobile device 3. Reload the mobile tab, then try inspect again. 1
Recommended Posts