We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

bug: unable to send tab from firefox nightly android (phone/tablet) to PC

  • 3 replies
  • 1 has this problem
  • 1 view
  • Last reply by pn10eko

more options

as described, send tab function does not work one way (android to PC), but works fine from PC to android mobile phone/tablet. the pop-up error is the "Unable to send - RETRY", and pressing 'RETRY' doesn't do anything. I am logged in to the mozilla account on both android devices, and firefox sync/syncing tabs work fine. not sure what's the issue

Firefox Nightly -both phone and tablet: 127.0a1 (Build #2016019535) Firefox version -laptop: 125.0.3

as described, send tab function does not work one way (android to PC), but works fine from PC to android mobile phone/tablet. the pop-up error is the "Unable to send - RETRY", and pressing 'RETRY' doesn't do anything. I am logged in to the mozilla account on both android devices, and firefox sync/syncing tabs work fine. not sure what's the issue Firefox Nightly -both phone and tablet: 127.0a1 (Build #2016019535) Firefox version -laptop: 125.0.3

Modified by pn10eko

Chosen solution

recent update (127.0a1) has fixed it 👍 thank you so much

Read this answer in context 👍 0

All Replies (3)

more options

There may be some temporary issue.

https://bugzilla.mozilla.org/show_bug.cgi?id=1896080

more options

oops, i thought i checked bugzilla before posting! 😅 will wait for the fix then, thank you for your time

more options

Chosen Solution

recent update (127.0a1) has fixed it 👍 thank you so much