Source code of java plugin used in TLabWebView (3D web browser / 3D WebView Unity plugin)

Android Studio Version:
Android Studio Koala | 2024.1.1
Build #AI-241.15989.150.2411.11948838, built on June 11, 2024
Runtime version: 17.0.10+0--11609105 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Windows 10.0
GC: G1 Young Generation, G1 Old Generation
Memory: 4096M
Cores: 24
Registry:
  debugger.new.tool.window.layout=true
  ide.experimental.ui=true
Non-Bundled Plugins:
  OpenGL-Plugin (1.1.5)
  GLSL (1.24)

OS: Windows 10  

• The following error occurs when using lockHardwareCanvas in unity 2021

2023/11/13 15:40:53.051 13492 13511 Error FrameEvents updateAcquireFence: Did not find frame.

Corresponding part of the code

// ViewToGLRenderer.java
public Canvas onDrawViewBegin() {
    m_surfaceCanvas = null;
    if (m_surface != null) {
        try {
            //mSurfaceCanvas = mSurface.lockCanvas(null);
            // https://learn.microsoft.com/en-us/dotnet/api/android.views.surface.lockhardwarecanvas?view=xamarin-android-sdk-13
            m_surfaceCanvas = mSurface.lockHardwareCanvas();
        }catch (Exception e){
            Log.e(TAG, "error while rendering view to gl: " + e);
        }
    }
    return m_surfaceCanvas;
}

• OpenGL Texture to HardwareBuffer
• WebView to ByteBuffer

When a page load fails with net::ERR_NAME_NOT_RESOLVED even though nslookup or dig succeed on the same device, the WebView process is typically using a different resolver than the system shell. In environments that rely on custom DNS (for example, a Pi-hole responder that is reachable only through a Tailscale VPN), double-check the following:

1. Ensure the device actually routes DNS through the tailnet. Private DNS / DoT settings override the resolver that the VPN advertises. Set Settings → Network & Internet → Private DNS to Off or Automatic, then reconnect to Tailscale so that the Pi-hole’s 100.x.y.z address is pushed down to the client.
2. Return an address that the device can reach. Pi-hole must answer with the service’s Tailscale IP, not an RFC1918 LAN address that the mobile device cannot route to from outside your home network.
3. Expose an IPv4 endpoint for the reverse proxy. Some Android builds still lack full IPv6 support over Tailscale. If Pi-hole responds with only a ULA (fd7a:…) address the WebView will fail the lookup. Add a 100.64.x.x record (or another routable IPv4) alongside the IPv6 answer.
4. Disable third-party “Secure DNS” in Chromium-based browsers on the device. Chrome/Edge’s DoH implementation bypasses Tailscale DNS entirely unless it is set to “Use current service provider”.

The plugin now logs the active DNS servers whenever the WebView encounters a host lookup error. Capture adb logcat output while reproducing the issue to confirm that the Pi-hole resolver is visible to the WebView process.