WPA3 Configuration Fails to Save on Certain Samsung Devices in Custom

In our Android application, which is designed to connect to Wi-Fi networks, we observed an issue where certain Samsung devices fail to save the Wi-Fi configuration when WPA3 is selected as the security type.

The issue occurs after the user clicks the Save button in the Wi-Fi configuration popup. The configuration is not saved, and the device does not attempt to connect to the specified Wi-Fi network.

This issue is specific to certain Samsung devices. Other devices, including Pixel and other non-Samsung models, are able to save the configuration and successfully connect to the network.

Note: This doesn’t happen with all the controllers(Working fine with Meraki,Mist,Ruckus) Issue occurs with: Cisco Aruba (WPA3 GCM)

Steps to Reproduce:

  Configure WPA3 SSIDin Aruba(with GCM)/Cisco
  Configure TLS Network using WifiNetworkSuggestion API
  Click Save in the Wi-Fi configuration popup

Expected Behavior:

  The Wi-Fi configuration should be saved, and the device should attempt to connect to the specified WPA3 network.

Observed Behavior:

On certain Samsung devices:

 The Wi-Fi configuration is not saved.
 The user is unable to connect to the network.

On other devices (e.g., Pixel): The Wi-Fi configuration is saved, and the connection is successful.
Impacted Devices:

Samsung Galaxy S21, S10, A34, M31

Other devices tested:

Google Pixel (Working as expected)

attaching google ticket for reference Google Issue Tracker

Hello,

Please contact using the following support channel.

Dev Support | Samsung Developer