Apple Watch pairing error

[JonathanB]

Hi everyone,

We've moved everything relating to Apple Watch pairing issues to this new conversation and will be providing all future updates as edits to this post, so that you won't need to go searching through the comments for these.

I appreciate these pairing errors must be very frustrating, especially for those of you that have been running into issues for several weeks now. Technical specialists are continuing to look into this, however based on what they've seen so far, this does not seem to be one overall fault that we can apply a blanket fix to.

With this in mind, please make sure you have followed the advice on the private message we've sent to each of you, this will ensure that your individual case has been escalated. We've originally sent these messages out a couple of weeks ago, so I'll double check that everyone that has commented has received these. You can find your community messages by clicking on your avatar in the top right of any page, then on "Messages".

Finally, please ensure you are following the Community House Rules when posting on the community, particularly points 8 and 13.

The private message mentioned above will put you in touch with a team that you can raise a complaint with should you wish to do so, any comments that share details of individual Three employees will be removed from the community.

JonathanB

---

**Update 26/10/2022**

Hi everyone,

We really appreciate your patience whilst we've been working on this issue. I can't imagine how frustrating it is to not be able to take full advantage of your Apple watches.

As I mentioned last week above, the errors do not seem to be one overall fault that can be fixed immediately for everyone. We do need a specialist team to do some work in the background on your accounts. With this in mind, I'd advise the following:

• Make sure you've taken any action we've recommended on private messages to your community account. If you're experiencing these issues and we don't already know, please reply on this post so we can reach out.
• Do not repeatedly attempt unpairing and pairing, this may be interfering with the work done in the background. Please wait for a Three representative to contact you and advise before you unpair and pair again.

We've seen some great progress towards getting this sorted in the last few days, I'm hopeful that it won't be too much longer till this issue is fully resolved for everyone.

JonathanB

---

**Update 17/11/2022**

 Hi everyone,

We’re really sorry that there’s been a considerable delay between updates on the errors with Apple watch pairing. As we’ve mentioned previously there is more than one error involved and specialist teams are working hard to address the root causes of these.

I assure you that all comments about this issue are read, and all feedback given is being escalated on a daily basis.

Whilst we’re working on this, we’d be grateful if you can do the following:

• If you’re new to this thread, please either private message me, or add a reply, and I’ll direct you to a team that can help further.
• If I’ve already sent you this information, please ensure you have spoken to that team.
• Please only unpair and re-pair your watch if directed to by one of our support teams as part of the troubleshooting and investigation of your issue.

I’ll provide another update soon.

Thanks,
JonathanB

---

**Update 02/12/2022**

Hi everyone,

Thanks for your continued patience. We’ve seen some great progress towards resolving these issues since the last update. As I’ve mentioned previously there is more than one error involved, and for many of you, your bill cycle will also affect when you can successfully re-pair the service.

Here’s some general steps that should help with common scenarios we’re seeing.

• Ensure that you’ve registered for My3, without a registered online account and password set, the pairing will fail.
• There are some instances where special characters at the start of My3 passwords have resulted in an error. We recommend that you have a strong password that is a combination of upper and lower case letters, numbers, and special characters but avoid beginning the password with characters like /!”£$|\. My3 supports these, but it seems to be causing an issue when this info is passed onto the smartwatch pairing system.
• If you’ve changed your priceplan, upgraded, or are instructed to wait for your bill cycle to complete, you should wait till the day after your new bill cycle starts to attempt pairing. So for example, if your allowances refresh on the 1st, wait till the 2nd.
• Although individual smartwatches can be unpaired from your account, cancelling or removing the add on completely will delay being able to reinstate the service till the following bill cycle.
• As mentioned before, don’t repeatedly unpair and re-pair, the failed requests may cause further issues on your account that delay this being solved.
• I’m continuing to regularly check for anyone new on the thread, just send a reply or private message me, and I’ll link you in with a support team that can help get your specific error looked into and make sure you get the best advice.

Thanks,
JonathanB

---

**Update 11/01/2023**

Hi Everyone,

As well as the steps on the last update, we're finding it helps to clear your temporary data from your iPhone before attempting pairing.

You can do this in Settings, Safari, Clear History & Website Data.

In case anyone is having trouble finding their private messages, click on your avatar image in the top right of any community page, then "Messages". If you've posted on this thread, then you should have a message waiting from me with a link to a support team that will help.

Thanks,
JonathanB

[PaulGriff13]

Updated my plan to a 24month sim only, so I can connect my iwatch series 8 to my plan for £7 like is advertised on the web site and I keep getting error code E53304.

[PeteG]

Hello, Paul.

Welcome to the Three Community.

That specific error message relates to the account you're pairing the Apple Watch with, and usually indicates there's another pending change on the account that's yet to be processed. 

Since you've advised that you just upgraded the contract, I've got a feeling that upgrade itself will be the pending change. The upgrade should complete on the account on the billing date. Pop onto My3 in order to see when that is. You should be able to get the watch to pair after that. 

I hope that helps.

Pete.

[Gary]

Apple Watch will not pair with iPhone every one has tried everything but nobody will admit this I’ve been trying since October 2022 after being told faithfully by three and now no reply from you guys here or anyone from three even community all say same it does not work at least be honest community support 

[PaulGriff13]

Thanks for the quick reply. I'll check that out and hopefully that resolves it. 

[PaulGriff13]

Smartwatch pairing plan added and active, still getting error code E53304. 

[mrnewq]

I've had exactly the same problem and error since I bought the Mobile Data for my Apple Watch 7, 3 months ago ... first the generic "there's a problem" error, now, after getting through to their tier 2 support I have the E53305 error.

There's clearly some infrastructure issue Three haven't got to the bottom of yet.

Ensure you ask for compensation whilst they are fixing it. 

[Firth_r]

Exactly the same problem! Spoken to 9 different support reps - all of them had no idea what I was talking about and the issue still isn’t resolved. Cannot believe how shoddy the service is - why offer a service if you can’t deliver it?? Beyond frustrated. 

[JonathanB]

Hi everyone,

Just to confirm, there is a priority fault under investigation with the smartwatch pairing, this may be the cause of the issue for some or all of you. I'll update on this post when there's any news. I'm sorry for the disruption this is causing in the meantime.

JonathanB

[gbailey141]

Guys I'm in the same Boat. Apple Iphone 14 Pro Max and Apple smart watch. Same error code. Was told to re-set phone, watch etc and it still doesn't work...fuming is an understatement.

[Nadeem81]

Hello.im facing same issues.did ur issue resolved?