Multiple sessions

[owenkealey]

Hi,

My goal is to have multiple inappwebview sessions in my app so that they each have their own state and do not share anything. I tried using UniqueKeys to distinguish between web views but it seems the cookies on the first web view are being used by the second web view. Any guidance on how to fix this?

[pichillilorenzo]

I made some research to check if it is possible to do this in Android, but it seems not possible. The problem is not related to any Flutter API, such as UniqueKeys. Probably it is related to how Android manage cookies for all the WebViews.

[owenkealey]

I am trying iOS not Android.

…

On Tue, Jun 2, 2020 at 6:30 AM Lorenzo Pichilli ***@***.***> wrote: I made some research to check if it is possible to do this in Android, but it seems not possible. The problem is not related to any Flutter API, such as UniqueKeys. Probably it is related to how Android manage cookies for all the WebViews. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#371 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGH6KGHZUTY6ECC72UDFICLRUTIFJANCNFSM4NQOY44Q> .

[owenkealey]

I can do this with multiple WKWebView instances in Swift so I am wondering if it was possible with this plugin

[pichillilorenzo]

Ok, I found a bug in my code for the iOS platform. I was setting some WKWebView configurations too late. This will be fixed in the next release!

It seems that to have multiple sessions on iOS, I need to use configuration.websiteDataStore = WKWebsiteDataStore.nonPersistent() for each WKWebView you want to have without sharing cookies.
This is done through the incognito: true option.

Now incognito option is broken on iOS, but I'm going to fix it right now.

[owenkealey]

Awesome thank you!

…

On Tue, Jun 2, 2020 at 7:40 PM Lorenzo Pichilli ***@***.***> wrote: Ok, I found a bug in my code for the iOS platform. I was setting some WKWebView configurations too late. This will be fixed in the next release! It seems that to have multiple sessions on iOS, I need to use configuration.websiteDataStore = WKWebsiteDataStore.nonPersistent() for each WKWebView you want to have without sharing cookies. This is done through the incognito: true option. Now incognito option is broken on iOS, but I'm going to fix it right now. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#371 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGH6KGGF2QXL34X27DO5A33RUWEVJANCNFSM4NQOY44Q> .

[pichillilorenzo]

New version 3.3.0+3 released!

[shimorojune]

I am facing the same problem dealt with @owenkealey here.

The cookies are not stored only when there is an incognito version is present, which I believe would mean that maybe that feature is causing the problem.

I have tried the same code sample provided by @pichillilorenzo in this page. The same Gmail example provided, does not always persist the data all the time.
You can even try using other OAuth enabled sites such as Medium.com or similar.

@pichillilorenzo Could you please look into this?

[shimorojune]

@pichillilorenzo @owenkealey
I experimented around a bit, and found that while in incognito mode, the cookies for example are wiped clean to default state, the cookies are not filled with the default values once the incognito mode is turned off.
What could be the reason for this?

[sarthak13gupta]

I made some research to check if it is possible to do this in Android, but it seems not possible. The problem is not related to any Flutter API, such as UniqueKeys. Probably it is related to how Android manage cookies for all the WebViews.

Hi @pichillilorenzo , is it still not possible to have multiple inappwebview sessions without sharing state or anything ?
I'm making a dapp wherein i have to connect with the same web3 site on two different webviews but with different wallets .... can u help me with that?

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug and a minimal reproduction of the issue.