Post marked as unsolved
16
Views
Hi Team,
In my app, there is voip notification are working fine , from last year it have been stopped due to some pushkit changes.
Right now i want to know how to integrate the notification part like which certificate will be use for php side implementation like .pem file from voip_services.
and all other steps
Thanks in advance.
Post marked as unsolved
54
Views
Voip notifications are received in iOS 13 and 14 versions but not receiving only in iOS 12 version devices.
For below iOS 13 versions, i have used voip notifications for both messages and calls since there are no restrictions to show callkit immediately when payload is received under iOS 13 versions. This is not creating any issue when uploaded to testflight from XCODE 11. When i use XCODE 12 and upload to testflight, voip notifications are not received only in iOS 12 version devices. Have anyone faced the same kind of issue?
Post marked as unsolved
34
Views
After sending the push, the server shows that the push is successful. One system of 14.4 can receive the push, while the other system of 14.2 cannot receive the push and will not go away didReceiveIncomingPushWith
Post marked as unsolved
54
Views
We have implemented the calling feature with PushKit using NWPusher to send CallKit Notification to other device. It was working fine but it suddenly stopped working from last two days. We have regenerated the VoIP certificates and tested in both sandbox and production environments. The call is not working in both the environments and there is no error shown. We have noticed that the call back method 'didReceiveIncomingPushWith payload' is never called. So we are not sure what is the issue.
The call is going from the caller device but not received in the receiver device. We are not sure if that is the certificate issue or something else. Please help us to resolve this issue as we are about to release the app and we are stuck with this now.
Post marked as unsolved
185
Views
My app cannot receive push these few day but it work before.
Checked that the cert is valid
the server get 'sent successfully' response
used pushtry to test the cert and token and it can receive push in app
Any things i can further check?
Post marked as unsolved
63
Views
Hi. I have created 3 push certificates (Apple Push Notification service SSL (Sandbox & Production)
) with my AppID, and I noticed I can't create Apple Push Notification service SSL (Sandbox & Production) certificate with my AppID anymore.
I do not see my AppID in the selection of AppID for Apple push notification service SSL (Sandbox & Production ) certificate.
Is max number of push certificate for same AppID is 3 ?
Post marked as unsolved
55
Views
I am using the API's in Pushy to Communicate between App and the APNS, I am facing a problem as the am unable to fetch the invalid device token to pass to to Feedback system to remove from Cache, Please suggest if there is API as we were using one in APNSService called getInvaliddevcieTokens(),looking for a similar one.
Appreciate any suggestion and thanks for the help in advance.
Post marked as unsolved
252
Views
I have an iOS application which uses both Silent Push Notifications and Background Tasks to keep the application up to date, both wake up the app even if it's killed and allow to run code on the background.
Now I've turned this app into a Mac Catalyst app. I've managed to get Push Notification working, but I'm only receiving them when the app is opened, the app doesn't wake up if it's closed.
Also, the Background Tasks don't work at all, the UIBackgroundRefreshStatus is always UIBackgroundRefreshStatusDenied.
Is there any further configuration needed to run background code on Mac Catalyst? or is it not possible at all?
Thanks.
Post marked as unsolved
86
Views
Hallo, in our webapp there are implemented web push notifications for Safari users. Now we facing a problem after Update to Big Sur macOs, in Javascript we have a Code snippet to check if a popup should come and ask user if he want notifications but in Big Sur it's not working now.
if ('safari' in window && 'pushNotification' in window.safari) {
// Show popup
}
What should we change in this code to get it working in Safari Big Sur?
Regards,
Przemek Tranda
Post marked as unsolved
164
Views
Hi,
I am struggling getting callkit/pushkit working reliably. After receiving multiple calls while app is in background and I reject them, eventually the app crashes due to SIGTERM with the code 0xbaadca11 (means CallKit is killing the app due to no notification of incoming call).
I am notifying CallKit of incoming calls and calling the proper completions. After 2 app crashes, the app no longer receives calls until it is deleted and reinstalled.
Below I have attached my test app with all the code placed in the app delegate.
What is causing this problem? Thanks
App Delegate with all code - https://developer.apple.com/forums/content/attachment/30497dd2-025a-4195-89c3-ac599df7a790
Post marked as unsolved
97
Views
As per older Apple documentation about debugging push notifications, there was a very helpful link and companion file here.
https://developer.apple.com/library/content/technotes/tn2265/_index.html
The Companion File on the top right is a mobile configuration profile to help configure log push messages on iOS, but the certificate in it is expired.
This PersistentConnectionLogging.mobileconfig is very helpful as it enables logging to determine if push notifications make it to the device or the device or don't even get to the device at all.
https://developer.apple.com/library/content/technotes/tn2265/tn2265_PersistentConnectionLogging.zip
Sadly, it's expired and with an outdated certificate backing it, it's not useful at all.
Has this been updated anywhere on Apple's dev site or is there any other modern means to accomplish the same thing?
Thanks,
Alex Zavatone
Post marked as unsolved
131
Views
Im trying to send voip notification so that on other end user can get call notification like any other video calling app. I used pushkit for this purpose but issue is when i send push from pusher app giving token received from pushkit, call is initiated while i want to send this push notification for voip from my app. So that when user taps on call , the second user can get call on screen.
Post marked as unsolved
135
Views
Is it possible to use the CKNotificationInfo's desiredKeys property for the CKDatabaseSubscription?
I'd like to use have access to those values in the AppDelegate function...
application:didReceiveRemoteNotification:fetchCompletionHandler:
When I try to create subscriptions with desiredKeys, I get an error reading "cannot add additionalFields to this subscription type."
Is that for real? Can we not use desiredKeys with CKDatabaseSubscriptions?
Post marked as unsolved
236
Views
Currently we are using UserNotification framework for remote notification. We are planning to use Pushkit framework and now when will receive notification from pushkit (DidReceiveIncomingPush),we will generate local notification for user with banner, alert & sound in the call back method. This is due to the fact that the notifications have to be delivered as quickly as possible, wake up the app if it is backgrounded or the phone is locked.
we have following queries:
1) Will apple accept this implementation (without implementing callkit) ?
2) Blank callkit method i.e only method without logic is accepted or not?
Post marked as solved
168
Views
I am building a WebRTC based app that enables peer-to-peer voice calls between two users. The app works flawlessly when the device is connected to WI-FI, but I am encountering low level TCP related network issues when one of the devices is connected to the internet with 4G.
This happens when two devices are exchanging WebRTC candidate informations.
Once the problem occurs, the device produces errors like below every few seconds.
2021-02-22 10:31:52.952548-0800 App[9718:624872] [tcp] nw_proto_tcp_route_init [C3:2] no mtu received
2021-02-22 10:31:52.953908-0800 App[9718:624872] Connection 3: encountered error(1:53)
2021-02-22 10:31:56.371279-0800 App[9718:625253] [tcp] nw_proto_tcp_route_init [C3:2] no mtu received
2021-02-22 10:31:58.067480-0800 App[9718:625253] [tcp] nw_proto_tcp_route_init [C3:2] no mtu received
2021-02-22 10:32:01.330340-0800 App[9718:625340] [tcp] nw_proto_tcp_route_init [C3:2] no mtu received
The thing is that once the device encounters the above error, the device isn't able to receive PushKit notification (or so any kinds of 'push' from the server, including WebSocket push), while the device can still initiate HTTP calls. It is as if the device's some part of the network connection goes into a "stall" or "locked-in" state where it starts operating abnormally.
This problem resets as soon as I change the internet connection back to WI-FI, but comes back when I switch back to 4G/LTE.
The above error statement seems to be low-level network error statements, and I have no idea what I can do to diagnose the problem. Are there tools in macOS that I can use to analyze what is going on under the hood in an iOS device?
Of course, I want to avoid publishing my app if it works only with a WI-FI connection, and not with 4G/5G, so this is a blocker for me.
I have submitted feedback to Apple using Feedback Assistance, but I have not received a response from any one of my previous submissions, so I am a bit hopeless here and decided to ask to dev community.
