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
Logging in with a Facebook account through the Publicize web flow should return to the app after the login, and the Facebook account should be available be made available to the user.
Actual behavior
The web flow to connect a new Facebook account never returns to the app after successfully logging in with Facebook:
IMG_0102.MP4
Steps to reproduce the behavior
Open the app and select a WP.com or Jetpack site.
On the My Site screen, scroll down to the Configuration section.
Tap "Sharing".
Tap "Facebook".
Tap "Connect".
Login with a Facebook account that has at least one page.
Accept all Facebook permissions.
Notice how the web flow gets stuck and never returns to the app.
Additional context
This was caused by a change to the parameters of the URL used to create a new Facebook connection (internal ref: r238579-wpcom). Assuming the implementation on iOS is similar to what we have on Android, then the end of the web flow is detected based on some URL pattern. The fix should be to update this logic to take the new URL structure into account.
Tested on iPad Pro 11in, iOS 15.1, WPiOS 19.0
The text was updated successfully, but these errors were encountered:
Expected behavior
Logging in with a Facebook account through the Publicize web flow should return to the app after the login, and the Facebook account should be available be made available to the user.
Actual behavior
The web flow to connect a new Facebook account never returns to the app after successfully logging in with Facebook:
IMG_0102.MP4
Steps to reproduce the behavior
Additional context
This was caused by a change to the parameters of the URL used to create a new Facebook connection (internal ref: r238579-wpcom). Assuming the implementation on iOS is similar to what we have on Android, then the end of the web flow is detected based on some URL pattern. The fix should be to update this logic to take the new URL structure into account.
Tested on iPad Pro 11in, iOS 15.1, WPiOS 19.0
The text was updated successfully, but these errors were encountered: