Remove transitional accessor to RTCConfiguration.crypto_options
after downstream has been updated
Bug: webrtc:42235111
Change-Id: I8fb9761876dbd49b4a8955d7c6076d2a307aeee7
Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/402681
Reviewed-by: Sameer Vijaykar <samvi@google.com>
Commit-Queue: Sameer Vijaykar <samvi@google.com>
Reviewed-by: Harald Alvestrand <hta@webrtc.org>
Cr-Commit-Position: refs/heads/main@{#45296}
diff --git a/api/peer_connection_interface.h b/api/peer_connection_interface.h
index cd51c88..4311573 100644
--- a/api/peer_connection_interface.h
+++ b/api/peer_connection_interface.h
@@ -662,10 +662,6 @@
// frame encryption for native WebRTC.
CryptoOptions crypto_options;
- // TODO: bugs.webrtc.org/42235111 - remove after converting callers that
- // expect an optional.
- CryptoOptions& GetWritableCryptoOptions() { return crypto_options; }
-
// Configure if we should include the SDP attribute extmap-allow-mixed in
// our offer on session level.
bool offer_extmap_allow_mixed = true;