fix(android): music player starts on its own and no longer shows autoplay refusals

WebView now allows play() after the track fetch; a NotAllowedError leaves
the track waiting for the play button instead of raising an error.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

1 files changed, 3 insertions, 1 deletions

diff --git a/packages/meshbay-android/app/src/main/kotlin/org/meshbay/client/MainActivity.kt b/packages/meshbay-android/app/src/main/kotlin/org/meshbay/client/MainActivity.kt
index a781350..ea31bca 100644
--- a/packages/meshbay-android/app/src/main/kotlin/org/meshbay/client/MainActivity.kt
+++ b/packages/meshbay-android/app/src/main/kotlin/org/meshbay/client/MainActivity.kt
@@ -98,7 +98,9 @@ class MainActivity : Activity() {
             domStorageEnabled = true            // IndexedDB and localStorage: session, resume positions
             allowFileAccess = false
             allowContentAccess = false
-            mediaPlaybackRequiresUserGesture = true
+            // The page is our own bundled UI. With `true`, WebView wants play() inside the tap
+            // handler itself, and the music player only calls it after fetching the track.
+            mediaPlaybackRequiresUserGesture = false
             setSupportMultipleWindows(false)
             mixedContentMode = android.webkit.WebSettings.MIXED_CONTENT_NEVER_ALLOW
         }