During the configuration, the .eap-config is retrieved twice; this generates duplicate profiles (of which only one is used, the other one discarded on the client). It's fine to download the config to show some data/terms, but for actual configuration the same config should be used and not a new one.
On macOS this is probably more difficult, because not all information is available in .mobileconfig files, while on iOS the .eap-config is exactly the same.
During the configuration, the .eap-config is retrieved twice; this generates duplicate profiles (of which only one is used, the other one discarded on the client). It's fine to download the config to show some data/terms, but for actual configuration the same config should be used and not a new one.
On macOS this is probably more difficult, because not all information is available in .mobileconfig files, while on iOS the .eap-config is exactly the same.