Closed ghenry closed 4 years ago
It's the same on 13.5.1, so not iOS related.
It came through eventually after clicking Caller. Maybe coincidence. Now to test a push! :-)
So the alerts fail if I don't add rtc_channel_id
(which I created via uuidgen
on Fedora Linux), but do we need rtc_channel_id
? Can't we just call it UUID as per:
https://developer.apple.com/documentation/callkit/cxprovider/1930694-reportnewincomingcallwithuuid?language=objc https://github.com/masashi-sutou/flutter_ios_voip_kit/blob/master/ios/Classes/CallKitCenter.swift#L78
Or is this the wrong plugin I'm using with Flutter as it seems geared toward just one-to-one calling?
Thanks!
@ghenry
Nice! For Step 4. you can also do this quicker without a MacBook and KeyChain:
openssl x509 -inform der -in voip_services.cer -out voip_services.pem
Then paste your key in the .pem
after the cert Apple gave you. To create your CSR (bundle_id.voip.csr to upload) and Key for upload to Apple Developer Portal do:
openssl genrsa -out bundle_id.voip.key 2048
openssl req -new -key bundle_id.voip.key -out bundle_id.voip.csr
bundle_id
is just a naming format I did.
Thanks!
Hi,
I've edited the example via Xcode to use our app identifier and did
flutter run
after changing theSigning Team
. It just sits atgetVoIPToken
when I go toYour Callee
page.I've generated a VoIP Certificate, so I can test notifications like so:
which results in:
Now that is the correct device id for my test iPhone 8 as I ran the example previously before changing the identifier. What have I missed? The cert was created against the correct identifier on https://developer.apple.com/account/resources/certificates/add
Thanks.