Call not working after some period of time (iOS)

[fecabianchi]

Please include following information for better support

What version of React Native are you running? 0.50.4
What version of react-native-twilio-programmable-voice are you running? 3.5.0
What device are you using? (e.g iOS9 simulator, Android 6 device)? iOS 11 Device
Is there any relevant message in the log? No
If using iOS, which pod version are you using? 3.10.0

Step to reproduce

• When the app is reloaded, or resumed after a some period of time the call doesn't work, if i logout and login the voice call works again.

• Doesn't have the same issue with Android

[fecabianchi]

@fabriziomoscon have you seen this issue?

[fabriziomoscon]

When you resume the app you should really initialise the Twilio backend token, because it has an expiration.
Let me know if this fixes the problem.

[fecabianchi]

Ok, but if the app stays in the background the token will not be renewed right?

i saw two behaviors, so here is the scenario.
We have two users, if both have fresh login to the app the call works, if user1 (caller) get a fresh login and user2 doenst, the user1 hear the sound of calling on the phone but no notification arrives at user2, the twilio log when this happens is Incoming: Completed and Outgoing Dial: No Answer.

if the caller doesn't get a fresh login when he try to call there is no calling sound (completely mute) and nothing appears on the twilio logs.

[fabriziomoscon]

Please note that tokens needs to be valid ONLY for calling. Since you should only call in the foreground, initialising the token on each app resume ensure you have always a fresh session.
The library receives calls regardless of the backend token status.

[fecabianchi]

so there is some weird stuff going on because if I get a valid token for calling, the call works, but the the receiver does not receive any call notification (if receiver token is invalid). so I'll investigate.

[eugenehp]

Hey @fecabianchi what's the update?
I'm seeing similar behaviour on my end as well.
Curious if you found some additional details after your investigation.

[fabriziomoscon]

@fecabianchi @eugenehp
please update your Podfile with

pod 'TwilioVoice', '=2.0.0-beta21'

and package.json with

"react-native-twilio-programmable-voice": "^3.12.0",

and check if the problem persists

[eugenehp]

Nice job Fabrizio! I’ll check it ASAP and let you know.

…

On Thu, Mar 1, 2018 at 4:42 AM Fabrizio Moscon ***@***.***> wrote: @fecabianchi <https://github.com/fecabianchi> @eugenehp <https://github.com/eugenehp> please update to pod 'TwilioVoice', '=2.0.0-beta21' and "react-native-twilio-programmable-voice": "^3.12.0", and check if the problem persists — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#64 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABxW74PCyYpaBBWqW0BaCaVH-x18Jvvxks5tZ-yjgaJpZM4RktlW> .

[jpmermoz]

I'm getting the same issue. Incoming calls works great on background, but after a day my app stops receiving incoming calls unless I receive a new access-token from the server.

If I go to the Twilio debugger, i'm getting this error:

GCM/FCM client uninstalled or turned off notifications

This seems to happen on both Android and IOS.

[yatindma]

getting "Empty Credentials" when making a call from iOS or Viceversa, In Android it's working fine.

[jdegger]

Hi, since a long time has passed I will be closing this issue. Read our repository update in #158. I invite you to reopen this issue when you still have problems so we can debug the problems together.