Closed fishbone1 closed 2 years ago
@silkimen Same problem here on both Android and iOS. Can you check this out? Currently, I can't perform OAUTH authorisation properly.
I'm not sure. but this sounds very much like a problem I'm experiencing, on authentication (with setFollowRedirects set to true) we are having users report they struggle to login or on app reload, lose a login session... which sounds like they are losing or not having cookies issued. We are yet to be able to actually reliable replicate the problem in a test environment but have plenty of users saying something is wrong with authentication.
"If" this is the same thing, I can report I'm using v3.1.0 of the plugin, cordova android 9.0.0 and ios 6.1.1 and it "seems" to be happening exclusively on ios, most reports curiously seem to be ios 14.7.1 (that could be a coincidence), but we get a mix of supported devices and ios14+ versions reported
Hi guys, I'm sorry for the inconvenience you are experiencing. This is an old known issue of this plugin, see #148. Unfortunately, I had no time to fix this. Would someone mind creating a PR for this?
I'm closing this ticket, please follow up on #148.
Describe the bug Cookies of redirecting HTTP responses (e.g. status code 302) are not stored. Only the cookies of the redirection's target location HTTP response are stored.
System info
Minimum viable code to reproduce If applicable, add formatted sample coding to help explain your problem.
e.g.:
Workaround
This patch solves the problem. But I'm not sure if it follows the redirect correctly in all cases. For instance I'm not sure how to treat headers. Send the same headers to the redirection target? At the moment it works for us: