-
Notifications
You must be signed in to change notification settings - Fork 152
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
Feat/v4 Twilio iOS v5 #138
Conversation
Great work! I was just getting started on this on my own, but glad to see someone made some headway already. After some initial testing on my app, it seems that when the call is ended on either end of the call, the call isn't terminated for the other party. Perhaps a bug with the |
Ethan, please make sure you have the latest version updated about 2 hours ago. I believe I found and corrected the issue.
…Sent from my iPhone
On Dec 28, 2019, at 11:52 PM, Ethan Naluz ***@***.***> wrote:
After some initial testing on my app, it seems that when the call is ended on either end of the call, the call isn't terminated for the other party. Perhaps a bug with the performEndCallAction method on line 543? Will try to investigate further.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Put correctly: I found an issue with canceling incoming calls. Make sure you have that fix when testing and let me know if that fixes your issue.
…Sent from my iPhone
On Dec 28, 2019, at 11:52 PM, Ethan Naluz ***@***.***> wrote:
After some initial testing on my app, it seems that when the call is ended on either end of the call, the call isn't terminated for the other party. Perhaps a bug with the performEndCallAction method on line 543? Will try to investigate further.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
That fix resolved the issue! The only small issue I found was that at the top of Not sure how important the uuid is (and in what situations it would be important), but my app is taking calls successfully without having the uuid set. Other than that, everything seems to check out in dev for me. Would appreciate it if anybody else could do more testing for their use cases and report back! |
Fixes #89 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a couple of clarifications.
I will need to test it on iOS before merging into master.
After playing around with this a bit, I found a bug when doing back to back calls. The second call doesn't terminate for the callee when the caller terminates the call. In the second call, two logs are missing that showed up during the first call: |
The bug I described above was introduced in part, because of Thoughts @fabriziomoscon @gitstud ? Happy to clarify if this was a vague or confusing explanation. |
I will try to verify this and help during the weekend. Unfortunately my app conversion to RN 0.61 is taking forever, but once I am in a position to make and receive calls I will help 100% with implantation |
@enaluz May I ask why you're calling the disconnect method from the Also, could you please provide the NSLogs so we can see what code path is being taken? I suspect it's from |
I finally finished my dialer yesterday and was able to test all of the events. @fabriziomoscon what can I do to help get this committed so we can continue to bug fix and add helpful features to this library? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, this is a very long PR. It is impossible to merge without me properly testing manually. Also because this library doesn't have tests :/
The fact that you changed some variable names, formatting and swapped lines, probably makes a lot of sense, but unfortunately it makes it tricky to complete a review.
Could I ask you to squash all commits into one and stock to the original formatting and variable names?
A future commit where you can for variable names and formatting should be sent separately.
Yeah, that's fare. Sorry about that - the initial implementation was just me copying the updated Twilio QuickStart, which is probably the wrong way to do it. I'll update it again with just the changes required for updating to the new version of the iOS SDK. |
* Correctly find callInvite to cancel I'm a novice at iOS development, but in my attempt to copy this QuickStart implementation into hoxfon/react-native-twilio-programmable-voice#138 I needed to make this change to get the cancel to work correctly. I wanted to share this change with you, but I have not tested it in this repo myself. Please confirm and merge if it is an issue. * Updated key name to uuid
This was automatically closed by me deleting the base branch Please do not remove https://github.com/lonnylot/react-native-twilio-programmable-voice/tree/feat/v4-ios-v5 as I will include it into #144 |
Upgrading to use Twilio 5.x iOS SDK.
This is an important update as the Twilio iOS 2.x SDK is unsupported as of January 1st 2020 and they recommend using the iOS 5.x SDK for incoming calls on iOS >= 13.x.
I am not an iOS dev. and I am giving this my best shot. I believe there are bugs, but I wanted to get it out publicly to ask for help from anyone who knows iOS/Objective-C.
EDIT: Here are some links related to the breaking changes: