|
Rank: Member Groups: Member
Joined: 9/4/2017 Posts: 10
|
Hello,
When I load linkedin in the EO Browser, I can login. When I close the application, and thus the browser, the cookie with my login data does not seem to be saved. When I restart the application, I have to login again. This process repeats itself.
Am I doing something wrong?
|
|
Rank: Administration Groups: Administration
Joined: 5/27/2007 Posts: 24,258
|
Hi, The first step to troubleshoot such issue is to use Google Chrome to load the same page and see if the same problem occurs. If the same problem occurs, then there is a problem with your page and you will need to fix that first. If it works with Google Chrome, then it should work with EO.WebBrowser unless you have explicitly set the EO.WebBrowser's cache path. The cookies are saved in files inside cache path. So if your application set a new cache path every time it restarts, it will lose all cookies. If you did not set cache path and the problem still only occurs with EO.WebBrowser but not Google Chrome, then you can try to isolate the problem into a test project and send the test project to us. See here for more details: https://www.essentialobjects.com/forum/test_project.aspxOnce we have that we will investigate further. Thanks!
|
|
Rank: Administration Groups: Administration
Joined: 5/27/2007 Posts: 24,258
|
Please check your private message for our reply. In the future please be very cautious and follow the steps in the above link when you send us test code.
|
|
Rank: Administration Groups: Administration
Joined: 5/27/2007 Posts: 24,258
|
Hi,
We have looked into the test project you sent to us. It won't work when you run it as a test.
When you run your code as a test, it is hosted by Visual Studio test execution engine. Every time you run a test, it will be run in a separate AppDomain. EO.WebBrowser is explicitly designed to be capable of maintaining separate cache path for separate AppDomains. So if you run the same test twice, they will have different cache path due to the fact that they are run inside separate AppDomains.
If you run your code in a normal application without explicitly using separate AppDomains, this should no longer be an issue.
Thanks!
|
|
Rank: Member Groups: Member
Joined: 9/4/2017 Posts: 10
|
Ahh thanks.
That makes sense.
|
|