Opened 8 years ago
Closed 6 years ago
#736 closed Bug / Defect (fixed)
iOS: Opening profiles from iCloud Drive doesn't work (iOS 9 + 10)
| Reported by: | CallumA | Owned by: | Antonio Quartulli |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | OpenVPN Connect | Version: | OpenVPN Connect for iOS v1.2.6 |
| Severity: | Not set (select this one, unless your'e a OpenVPN developer) | Keywords: | iOS9, iOS10, Connect, iCloud Drive |
| Cc: | Samuli Seppänen |
Description
If an OpenVPN profile is stored in iCloud Drive and the file is opened in OpenVPN Connect (share button -> Copy to OpenVPN Connect) it does not show up in the Connect app. Other apps do work so it does appear to be an OpenVPN Connect thing, rather than an iCloud Drive bug.
This happened to me on iOS 9, a day before I updated to iOS 10 where the bug still exists.
Change History (7)
comment:1 Changed 7 years ago by
| Cc: | Samuli Seppänen added |
|---|---|
| Owner: | set to jamesyonan |
| Status: | new → assigned |
comment:2 Changed 7 years ago by
| Version: | → 1.0.7 |
|---|
comment:3 Changed 6 years ago by
| Owner: | changed from jamesyonan to Antonio Quartulli |
|---|
comment:4 Changed 6 years ago by
| Status: | assigned → accepted |
|---|
comment:5 Changed 6 years ago by
| Summary: | Opening profiles from iCloud Drive doesn't work (iOS 9 + 10) → iOS: Opening profiles from iCloud Drive doesn't work (iOS 9 + 10) |
|---|---|
| Version: | 1.0.7 → OpenVPN Connect for iOS v1.2.6 |
comment:6 Changed 6 years ago by
Hi, this bug has been addressed and its fix will be shipped within v1.2.8.
Unfortunately, I have to say that it works only with one file at once, due to an iOS bug :-( Somebody else already opened a bug report to apple for this (https://openradar.appspot.com/36505593)
comment:7 Changed 6 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | accepted → closed |
1.2.8 has been approved and is being released to the AppStore?? as we speak. I am finally closing this ticket. Please feel free to re-open it if the issue is not yet solved.
This issue has been recently reported again and we have an internal ticket for this.
Hopefully it will be fixed soon.