cancel
Showing results for 
Search instead for 
Did you mean: 
Create a Post

Capsule Connect for iOS12 very slow

With the newest iOS 12 compatible version 1.600.19 of capsule connect "sending" actions are very slow (at least 10 times slower than on iOS 11 with old version of capsule connect).

We have an iOS app which communicates with an server via REST services (http requests via NSUrlConnection); the transfer of a bigger amount of data from the app to the server is now very slow, whereas the data transfer from server to app is as quick as usual.

I tested the same both on iOS 11 devices with old capsule connect and on iOS 12 devices with new capsule connect and also with a connection to a server which requires VPN and one which do not need VPN.

Only in case of iOS 12 with new capsule connect and connection to a server which requires VPN the very slow "sending data transfer" happens.

8 Replies
Highlighted
Admin
Admin

Re: Capsule Connect for iOS12 very slow

Yuval Raban‌ any ideas?

0 Kudos

Re: Capsule Connect for iOS12 very slow

Same problem with speed here.  A good product has turned into a poor product since iOS 12.

0 Kudos
Admin
Admin

Re: Capsule Connect for iOS12 very slow

Keep in mind that Apple changed the VPN infrastructure extensively in iOS 12.

There may be some additional adjustments we need to make to account for this.

I would open a TAC case so we can gather the appropriate troubleshooting data.

0 Kudos

Re: Capsule Connect for iOS12 very slow

In the iOS12 settings, change tunnel type from SSL to IPsec. That should solve your problem. TAC mentioned that VPN code was improved in JHF142 and R80.20, haven't tried it yet.

0 Kudos

Re: Capsule Connect for iOS12 very slow

Many thanks, much appreciated.

0 Kudos

Re: Capsule Connect for iOS12 very slow

Even with tunnel type IPsec same problem remains. Any further help is much appreciated.

0 Kudos

Re: Capsule Connect for iOS12 very slow

This helped on R80.10, jhf 103.

0 Kudos
Admin
Admin

Re: Capsule Connect for iOS12 very slow

Please open a TAC case, as previously suggested, so we can troubleshoot what's going on.