Posts

Post marked as solved
6 Replies
Thank you for the quick reply!
Post marked as solved
6 Replies
Hello, it looks like this issue has been fixed with iOS 13.6. Can you confirm this? Has there been an internal bug report that lead to a fix with iOS 13.6? Thanks & Kind regards.
Post marked as solved
6 Replies
> If you (temporarily) replace your content filtering code with no-op code (just return .allow() to all new flow requests in your data> provider), do you still see the problem?Yes, I still see the problem, even after returning an allow verdict in every method of my data provider.The only way I can connect again to the VPN is by removing the configuration profile that contains the "Web Content Filter".After removing the configuration profile, I can see that the "-stopFilterWithReason:completionHandler:" method of my data provider is called. From this point on, the VPN connection can be established successfully.