FaceTime New Bug?

[PurpleHillsMac]

Hi all,

I've noticed that FaceTime Video hangs up on me every 19 seconds after connecting and FaceTime Audio hangs up 20 seconds after connecting.

Tested on:
iPhone 7 - iPhone X
iPhone X - iPhone 8 Plus
iPhone X - iPad Air

All devices are running the latest iOS.

Is anybody else encountering this issue?

I've reached out to Apple with this issue and I am waiting for them to look into it and get back to me.

 

[ManuCH]

Does this happen on 4G or Wifi? Or both? If it's only on Wifi, it's likely an issue with your router settings. On 4G... that would be weird.

 

[PurpleHillsMac]

It happens both on Wifi and 4G.

 

[PurpleHillsMac]

It happens both on Wifi and 4G.

I've done a bit more testing, but on my iPad Pro 9.7 this isn't an issue. On my iphone X, FaceTime still cuts off after 20 seconds. Is anybody else experiencing this?

 

[crawfish963]

I have not seen this on any of my devices. Have you done a restart?

 

[PurpleHillsMac]

Yes, and this issue is occurring on my mom’s iPhone too. She’s using an iPhone 7.

Apple is looking into to for me and I’ll post back whatever they tell me.

 

[crawfish963]

Intersting. FaceTime hasn't worked properly since they introduced the group feature. What a nightmare.

 

[PurpleHillsMac]

Intersting. FaceTime hasn't worked properly since they introduced the group feature. What a nightmare.

Yeah, I've found that it goes to an eternal "reconnecting" on longer calls. "Poor Connection" comes on all the time for me, and it gets stuck on that even if the connection improves. The only way I found to fix it is to call back.

 

[crawfish963]

FWIW, I have a 400 meg connection at home and still get the "Poor connection" message when FaceTiming from the other room with another device in the house.

 

[PurpleHillsMac]

FWIW, I have a 400 meg connection at home and still get the "Poor connection" message when FaceTiming from the other room with another device in the house.

I'll bring this up to Apple when they call back about my other issue. We can only hope that the more we ask, the sooner they'll iron out the bugs...

 

[crawfish963]

I wonder how much of it has to do with server allocation for FaceTime. I can't think of any other reason why it would be so slow. It's almost like Apple is bottlenecking FaceTime most of the time. Or maybe it's just the NSA spying and eating up bandwidth

 

[PurpleHillsMac]

I'll bring this up to Apple when they call back about my other issue. We can only hope that the more we ask, the sooner they'll iron out the bugs...

IMO, FaceTime was hands down the best calling service for a long time. But recently it seems to be buggy
[doublepost=1551578996][/doublepost]

I wonder how much of it has to do with server allocation for FaceTime. I can't think of any other reason why it would be so slow. It's almost like Apple is bottlenecking FaceTime most of the time. Or maybe it's just the NSA spying and eating up bandwidth

Let me guess, maybe a combo of both? Now that we mentioned the NSA, we're definitely gonna be spyed on...

 

[I7guy]

I have not had this issue on the latest beta. As far as the poor connection message, I have gotten the message before even when both parties are on high speed connections.

 

[Ledgem]

Not an issue for me or anyone in the family (5-6 different devices being used across different parts of the country). That sounds like an odd issue, though. Is the call failing, or is the app crashing? Is there any other common point of failure, like a common internet connection that is involved?

 

[PurpleHillsMac]

Not an issue for me or anyone in the family (5-6 different devices being used across different parts of the country). That sounds like an odd issue, though. Is the call failing, or is the app crashing? Is there any other common point of failure, like a common internet connection that is involved?

Same here with me, we’re all spread across different countries and using a mix of wifi and 4G. It’s really an odd one. The app doesn’t crash, it just hangs up and makes the hang up chime.

 

[fyun89]

I'm having this exact issue as well.
I dont think I had this issue before iOS12 but I started to notice this since late last year. It goes away and comes back later. It seems to be a problem on Apple's side

 

[PurpleHillsMac]

I'm having this exact issue as well.
I dont think I had this issue before iOS12 but I started to notice this since late last year. It goes away and comes back later. It seems to be a problem on Apple's side

Interesting, then it’s not only me that’s having this issue. I’m still waiting on a reply from Apple. I’ll contact them tomorrow and bug them for an answer.

 

[Aidy06]

Happens to me also, will say ‘reconnecting’ and then it will ring again. I’ll answer and it will keep doing it like it’s in a loop, happens over 4G and WiFi. This has only been an issue for me since installing beta 4.

 

[fyun89]

Happens to me also, will say ‘reconnecting’ and then it will ring again. I’ll answer and it will keep doing it like it’s in a loop, happens over 4G and WiFi. This has only been an issue for me since installing beta 4.

In my case, I never see "reconnecting". It just drops the call with a record being "call failed" in my phone app's history.
I don't know if this is relevant, but my phone is iPhone X (2017)

 

[Aidy06]

In my case, I never see "reconnecting". It just drops the call with a record being "call failed" in my phone app's history.
I don't know if this is relevant, but my phone is iPhone X (2017)

iPhone X here also. Happens every time without fail for me, strange.

 

[PurpleHillsMac]

iPhone X here also. Happens every time without fail for me, strange.

My iPhone seems to be cured for the time being... but who knows how long that will last. Like @fyun89 said, it seems to come and go.

 

[fyun89]

iPhone X here also. Happens every time without fail for me, strange.

Turning off and on sometimes cured for me.
May be just to have more info out, I normally do facetime audio at night time in PST zone. Idk if it is the usual time when Apple does server inspection.

 

[Aidy06]

Issue has now been fully resolved for me since installation of beta 5.