You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CapacitorCookies always calls CookieHandler.setDefault with the Bridge's CookieManager. Make this configurable
Platforms
iOS
Android
Web
Request or proposed solution
If an app wants to use multiple instances of BridgeFragment, the newest instance will overwrite the global CookieManager defined with CookieHandler.setDefault(CookieManager), which will break global cookie handling for older instances. This is likely not a big problem if apps are using OkHttp or other frameworks that don't use the global CookieManager. Still, it would be good to make this behavior explicit.
Alternatives
Don't use the global CookieManager (available via CookieHandler.getDefault()) in any of your application code
Additional Information
Thanks so much for this project!
The text was updated successfully, but these errors were encountered:
Description
CapacitorCookies always calls CookieHandler.setDefault with the Bridge's CookieManager. Make this configurable
Platforms
Request or proposed solution
If an app wants to use multiple instances of
BridgeFragment
, the newest instance will overwrite the globalCookieManager
defined withCookieHandler.setDefault(CookieManager)
, which will break global cookie handling for older instances. This is likely not a big problem if apps are usingOkHttp
or other frameworks that don't use the globalCookieManager
. Still, it would be good to make this behavior explicit.Alternatives
Don't use the global
CookieManager
(available viaCookieHandler.getDefault()
) in any of your application codeAdditional Information
Thanks so much for this project!
The text was updated successfully, but these errors were encountered: