Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Redirect to Pairing not successful after taping on the Device connected #20127

Open
abodea opened this issue May 2, 2024 · 5 comments
Open
Labels
Bug 🐞 This is a bug with existing functionality not behaving as expected S3 Blocks non-critical functionality and a work around exists

Comments

@abodea
Copy link
Member

abodea commented May 2, 2024

Steps to reproduce

  1. Launch FF and connect to any FF account.
  2. Go to the FF homepage and tap on the Device connected under the Tab pickup menu.

Expected behavior

The connected device should be displayed.

Actual behavior

Redirect to Pairing not successful after taping on the Device connected.

Device & build information

  • Device: iPhone 15 Pro (17.4).
  • Build version: v126 (41443)
  • First seen version: ?

Notes

Attachments:

Skype_Video.2.mp4

┆Issue is synchronized with this Jira Task

@abodea abodea added Bug 🐞 This is a bug with existing functionality not behaving as expected S3 Blocks non-critical functionality and a work around exists labels May 2, 2024
@data-sync-user
Copy link
Collaborator

➤ Norberto Andres Furlan commented:

Nishant Bhasin

@data-sync-user
Copy link
Collaborator

➤ Norberto Andres Furlan commented:

Valerie Pomerleau can you take a look to this bug? Thanks!

@data-sync-user
Copy link
Collaborator

➤ Nishant Bhasin commented:

Andrei Bodea Could you double check if the device connected is actually shown in the account settings. This can be done after you have connected the device by going to the hamburger menu > sync > account management and navigating to connected devices

wondering if this is due to cached page cc Valerie Pomerleau

@data-sync-user
Copy link
Collaborator

➤ Valerie Pomerleau commented:

Hi Norberto Andres Furlan, I believe this is an edge case and doesn’t reflect that pairing was unsuccessful. The two devices in a pairing flow have separate routes as they go through the process, and I wouldn’t expect picking up the desktop tab on mobile would display the pairing status of the mobile device.

As long as both devices initially showed a success screen and the connected devices are listed in the account settings (as suggested by Nishant Bhasin), then the pairing was successful.

Perhaps Vijay Budhram can confirm.

@data-sync-user
Copy link
Collaborator

➤ Vijay Budhram commented:

Norberto Andres Furlan this does appear to be an edge case. Did you connect the account originally via pairing, or can you consistenly reproduce?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug 🐞 This is a bug with existing functionality not behaving as expected S3 Blocks non-critical functionality and a work around exists
Projects
None yet
Development

No branches or pull requests

2 participants