Forum Discussion
Recent Android change regarding Wifi configuration
We are on the way to solve the issue that was brought by the new requirement regarding the domain value for Wifi. Testing was done successfully on our preproduction environment and will be pushed soon in production.
Regarding communication of the updates, it could be good to have a thread in this community that would give information about changes that could impact customers like the change on the domain for Wifi. It would also permit Google to receive some real feedbacks from the field because I guess it's complicated to have an exhaustive picture about the impacts when something like this is changed.
Luc
I wonder if you are now looking at the same "chicken & egg" situation we are in now. How do we update all the existing devices with the new EAP-TLS config.
-If you update the existing profile it will pull before push which leaves the devices with no connection.
-If you push a new profile alongside the existing one it does not overwrite it unless someone manually re-applies the profile on the device side.
Best approach is usually to update the current Wifi profile. Most of our devices are using 4G so it shouldn't be a problem on our side. However, if I remember test I've done in the past, when the existing wifi profile is updated, the current wifi configuration is maintained until the new profile is received on the device. Once received, the old configuration is removed and replaced by the new one. In this scenario, even if you have devices that are using the Wifi only, it shouldn't be a problem to update the wifi configuration.
Luc
