diff --git a/src/libraries/System.Net.WebSockets/tests/WebSocketDeflateTests.cs b/src/libraries/System.Net.WebSockets/tests/WebSocketDeflateTests.cs
index f3b2548f1de1e3..8794ff6f9ac6f6 100644
--- a/src/libraries/System.Net.WebSockets/tests/WebSocketDeflateTests.cs
+++ b/src/libraries/System.Net.WebSockets/tests/WebSocketDeflateTests.cs
@@ -349,6 +349,7 @@ public async Task LargeMessageSplitInMultipleFrames(int windowBits)
         }
 
         [Fact]
+        [ActiveIssue("https://github.com/dotnet/runtime/issues/52645", TestPlatforms.Android)]
         public async Task WebSocketWithoutDeflateShouldThrowOnCompressedMessage()
         {
             WebSocketTestStream stream = new();
@@ -363,6 +364,7 @@ public async Task WebSocketWithoutDeflateShouldThrowOnCompressedMessage()
         }
 
         [Fact]
+        [ActiveIssue("https://github.com/dotnet/runtime/issues/52645", TestPlatforms.Android)]
         public async Task ReceiveUncompressedMessageWhenCompressionEnabled()
         {
             // We should be able to handle the situation where even if we have
@@ -378,7 +380,7 @@ public async Task ReceiveUncompressedMessageWhenCompressionEnabled()
                 DangerousDeflateOptions = new WebSocketDeflateOptions()
             });
 
-            // Server sends uncompressed 
+            // Server sends uncompressed
             await SendTextAsync("Hello", server);
 
             // Although client has deflate options, it should still be able
@@ -399,6 +401,7 @@ public async Task ReceiveUncompressedMessageWhenCompressionEnabled()
         }
 
         [Fact]
+        [ActiveIssue("https://github.com/dotnet/runtime/issues/52645", TestPlatforms.Android)]
         public async Task ReceiveInvalidCompressedData()
         {
             WebSocketTestStream stream = new();