![]() ![]() However, it still won't connect and I see no logs (on either side). ovpn12 extension, and now I can see the cert in the OpenVPN app. I followed the instructions to separately add my p12 cert via an. After upgrading to 1.2.5, that stopped working. I had a working mobileconfig deployed profile with connect on demand. Than we have a workaround until the problem with the API is solved. That way we could distribute the client ourself through MDM. Than take some time to take a deep dive in the problems with the new Apple API.Īn other option would be to release version 1.1.1 as an unsigned IPA for download. Rolling out a new client based on version 1.1.1 seems the best quick win. So it probably won’t be deprecated until iOS 12.Ĭommon guys, We have big problems now in our MDM solution which is based on the OpenVPN connection. Depreciation of api’s is typically not done in dot releases like 11.3. After that, they would have enough time to implement the new api. ![]() So why not revert it back and help the customers now. I might be deprecated in the future, but it still is not deprecated. ![]() This is possibly one of the worst App upgrades I have witnessed in 10 years of iOS development. If it was, the QA Director needs to be made redundant after this shambles. Also, why was this issue not found during Q/A? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |