Hi,
(I saw 2 or 3 posts about this on this thread besides mine).Right. This is information which should have been communicated from the outset, rather than allege that I, for example, do not know what I am talking about. Indeed, the information you cite confirms my prior statement that OpenVPN were not compelled to release 1.2.5 this week. You could have taken your time to release a product which was not broken upon arrival for many customers, as well as using the time to plan through how to make users aware of the major rebase changes contained within the product.dazo wrote: ↑Thu Jan 11, 2018 3:28 pmRegarding retracting the 1.2.5 release and have 1.1.1 in the appstore again. Apple gave OpenVPN Inc a hard deadline on the old VPN API. Any app updates to OpenVPN Connect after July 2017 cannot utilize the old VPN API. This is out of our control. So we are forced by Apple to move forward. To rollback or even re-release the old 1.1.1 with a newer version number will be blocked by the Appstore before it reaches all the users - due to the fact that the app will then use an API which is no longer approved.
I get all that, and others clearly do as well. The issue is how this change was communicated prior to the release. OpenVPN need to reassess completely how they release and name versions with major changes.Regarding the issues related to the keychain. The newer VPN API we needed to move towards to is far more stringent and stricter in the access control. The old API was much more open and forgiving, and it was possible to access keying material outside the "domain" of the single app. This power is bad for device security. So when we now do not have that access, it is definitely seen as a user experience regression. But again, this is also outside our control. Apple enforces OpenVPN Connect updates to use the newer VPN API, and we need to play within the boundaries that gives us. One way to circumvent all this is to have the key/cert/ca files embedded into the configuration file.
You work in software. So do I, and many others here. You have to learn to deal with irritated users who are rightly upset at the approach taken with your release.And finally, all the feedback has been valuable - in various degrees. But some post have been less constructive and useful.
No. It's not. Writing a persons death sentence is 'disturbing to write'. Asking people to be nicer to you and staff is not remotely 'disturbing'.What I'm about to write, is truly sad and disturbing to write
I would simply appreciate why users are upset and work internally to ensure the business understands why a customer is irritated and upset, working together openly to agree a strategy to resolve their frustrations. I wouldn't, however, cry about being spoken to in a forceful manner by an intelligent customer who is raising legitimate issues of complaint.When submitting a post, think through how you would experience the message you're about to submit if you were the receiver and not the sender.
I think you haven't read the part when oat_bondmen says Apple forced them to release something for months and they had no choice other than publishing their new app or their old app was going to be removed.oat_bondmen wrote: ↑Thu Jan 11, 2018 4:12 pmIndeed, the information you cite confirms my prior statement that OpenVPN were not compelled to release 1.2.5 this week. You could have taken your time to release a product which was not broken upon arrival for many customers, as well as using the time to plan through how to make users aware of the major rebase changes contained within the product.dazo wrote: ↑Thu Jan 11, 2018 3:28 pmRegarding retracting the 1.2.5 release and have 1.1.1 in the appstore again. Apple gave OpenVPN Inc a hard deadline on the old VPN API. Any app updates to OpenVPN Connect after July 2017 cannot utilize the old VPN API. This is out of our control. So we are forced by Apple to move forward. To rollback or even re-release the old 1.1.1 with a newer version number will be blocked by the Appstore before it reaches all the users - due to the fact that the app will then use an API which is no longer approved.
Er, that's me.
At no point has that statement been made. Here's the statement again:says Apple forced them to release something for months and they had no choice other than publishing their new app or their old app was going to be removed.
I think you're confused as to my identity.We're a dozen of people here pretending this app is a mess for 99% of this world's users but it seems oat says we are only few people complaining. Well... up to you to believe him or not.
great, it worked, thank you very much !!!asiaexplorer wrote: ↑Thu Jan 11, 2018 4:12 amI also can confirm that. It's working. Just rolled back to v1.1.1.bearever wrote: ↑Thu Jan 11, 2018 2:00 amThe above method does work (FYI I rolled back my openvpn app to v1.1.1) but you need to follow the above youtube tutorial by yourself. I cannot share my ipa file with you as the app is tied to my iTunes account.danquel wrote: ↑Wed Jan 10, 2018 5:02 pm
Has it worked for you? Can you send it to me? (danquel@hotmail.com) thank you, we are desperate
I followed the youtube link and the following tutorial: https://medium.com/@iosight/how-to-lega ... 45559b8357
The correct string for the version 1.1.1 is:With this information you can follow the tutorial from step 15. All steps above are only to find out the right string.Code: Select all
819500456
Of course you need the right iTunes version mentioned above to enter the app store and fiddler installed.
Would it be possible to rebrand/resign the IPA in xcode using our enterprise distribution provisioning profile and then push it out via Airwatch as an managed app?danquel wrote: ↑Thu Jan 11, 2018 11:17 pmgreat, it worked, thank you very much !!!asiaexplorer wrote: ↑Thu Jan 11, 2018 4:12 amI also can confirm that. It's working. Just rolled back to v1.1.1.
I followed the youtube link and the following tutorial: https://medium.com/@iosight/how-to-lega ... 45559b8357
The correct string for the version 1.1.1 is:With this information you can follow the tutorial from step 15. All steps above are only to find out the right string.Code: Select all
819500456
Of course you need the right iTunes version mentioned above to enter the app store and fiddler installed.
Indeed it isn’t.
Customers .. who have paid nothing because it is FREE.
Diaper changes ..oat_bondmen wrote: ↑Fri Jan 12, 2018 12:33 amNor is banning participants in these discussions, nor sending them ’warning’ messages, not is bleeting about ‘real persons’ being hurt by the dissent expressed here.
We should be receiving 6-12 hourly updates on progress being made to resolve each issue raised.
1. You have a lot to learn about FOSS development;Customers .. who have paid nothing because it is FREE.
