I am running into a super strange issue as I converted over from UIWebview. In our application, the user logs in and we set authentication cookies for our API server. This has always worked perfectly until we started using WkWebView for the newer iOS builds. I have tried trigger 2.8.4 and even 2.8.5. What is really wierd is I can get it to work great by killing or putting the app in the backgrond after install and then opening it again.
Here is a basic flow:
- Install App in iOS, App Opens after install
- User enters username and password and click login
- JSONP call is sent to API and response comes back. (In console I can see the set-cookie directives as expected)
- Cookies are evidently not set in the webview because subsequent calls to API do not include them in the request header
===HERE IS WHERE IT GETS WEIRD===
- User clicks HOME button to send app to background OR kills it completely
- User brings app back to foreground
- User logs in again
- JSONP call sent exactly the same as before
- Cookies are set correctly and all is well from that point forward.
This seems related to a few things I am seeing out there. Here is a good thread https://issues.apache.org/jira/browse/CB-12074
I wanted to see if anyone has produced a workaround for trigger.