pushkit | required components to set up independent web push | Notification library

i configured apiKey in huawei console for PushKit and i want send push from web app to my android app, so i prepared following CURL:

problem is postman still return

I use cURL to send pushkit notifications to Apple. My Rails code looks like this:

curl --http2 -v -d '#{payload.to_json}' --cert #{pem} #{pushkit_base_uri}/#{registration_id}

Since 19th Jan, 20201, running this command on Ubuntu has been returning the following:

I have an already existing flutter app that uses firebase auth, MLVision for face recognition and cloud messaging for push notification. I'm using flutter. My problem now is how to integrate Huawei auth. I'm new with this huawei integration. I haven't tried it yet, I just want to know before starting.

From what I've read from some post. I need to integrate Huawei Mobile Services (HMS), Huawei Account Kit and AppGallery Connect Auth Service. For non huawei phone with google services, I can authenticate using both firebase and huawei auth with different button right? But how about huawei phones without google services?

1. How will the app know? So it can hide the firebase login or run huawei only scripts for authenticaion?
2. MLVision needs google play services. Is there the same for huawei kit?
3. If its a large revision of code, will it be easier to create the app only for huawei phone with HMS, auth, Pushkit and with no google services script.

I removed the all gms related apis and added hms ones. My debug version is working awesome, I have the agconnect file in my project root. But If I download my app directly from appGallery, my hms core related apis are not working. (like pushkit and iap). I checked the console when my app's release version is running and I saw this error:

I working on a video call application in iOS Swift 5, where call can only initiate from the backend web app and the mobile app can only answer to those calls,. Means there is no mobile-mobile communication, communication between web app and mobile app. In my application I'm using PushKit with CallKit for notifying the incoming call in the background or killed state. So in the background or killed state, if I get an incoming call, it will show the calling screen using CallKit and if I pressed Answer button, it will navigate to my own custom video call screen where I have end button for dismissing the call. But when I press the end button, the VoIP call get disconnected. But the CallKit call is not dismissing(Still show the green bar on the top of Homescreen). And I checked for how ending the CallKit call via code, but in most of the solution the CallKit is dismissing with the use of callUUID. But I don't know from where I will get that UUID. In some code I saw the UUID is received from the push payload, but in my case the call is initiated from the web app, so I'm not receiving the caller UUID. Please help me. This is my code,

I'm working on an iOS swift project in which I need to integrate video call and chat using WebRTC and PubNub, I'm using PubNubSwift', '~> 3.0.1 SDK for PubNub. I have integrated the video call and chat in foreground state. But I want to notify users when receiving a call in background or killed state. And for push notification, the backend team is using pubnub. So In PubNub admin panel, I enabled the mobile Mobile Push Notifications, and I added TeamID, AuthKeyID and uploaded the Auth Key token(.p8 file). See the following image.

And In my code, in AppDelegate, I register for PushKit notification. And once run the application, I will get the pushKit token in
the following method. func pushRegistry(_ registry: PKPushRegistry, didUpdate credentials: PKPushCredentials, for type: PKPushType) {

The question is getting from here and seem no one give a proper answer yet.

==================================

Hi Devs,

I'm developing a Social networking app which includes audio call feature. I integrated with SocketIO + WebRTC for this audio call. I'm receiving audio call by two ways. Socket call when socket is connected & active VoIP call by default irrespective of socket is connected or not.

FYI, Why i had two ways of receiving call as mentioned above,

• Enabled VoIP by default, because sometimes socket call is unresponsive and never show call at that time.
• Enabled socket when app is in foreground, to ensure that call is received in case of MissingDeviceToken/BadDeviceToken errors occurred for VoIP push.

Considering iOS 13 guidelines for VoIP usage, I followed below steps for integration.

1. When app is killed or socket not connected, will get VoIP call and responding with provider.reportNewIncomingCall(). So here no issue for VoIP usage.

2. When socket is connected, will get both socket call & VoIP call. But socket call will get instantly before getting VoIP call. So here's what i did:

   1. Responded socket call with provider.reportNewIncomingCall().
   2. After a little delay will get VoIP push for the same call which is already invoked by socket. Here, I should respond this VoIP push with CallKit. But i have already invoked the call. So, I used below code to handle.

provider.reportCall(with: call.uuid, updated: update) with same uuid & update used for socket call initiation. Hope, this VoIP call also responded with CallKit and there's no issue in VoIP blocking/app termination.

Question 1 : Is this a proper way of handling above issue ?

===========================================================================================================

As per my app requirement, there's should be one active call at a time from my app.

Consider, I'm in active call and one more incoming call is received via VoIP. So here, I don't want to show the additional call. So I'm ignoring the VoIP push for the additional call. But it leads to this crash "Killing app because it never posted an incoming call to the system after receiving a PushKit VoIP push callback."

Question 2 : How to handle above mentioned scenario ?

===========================================================================================================

For question 2, I try answer from this one.

Though it does not work in some case for example when user happen to answer a call fast enough, the second incoming call from push will result in Call Stacking screen.

This approach also create additional call in recent call list and a bar incoming call saying call ended during incoming screen for the first incoming event which is bad user experience.

I also found this one to look promising but it is very had known this will be fine.

Does anyone have any solution to this? Thanks

I have set up PushKit in my app and I want to send upstream message. On a device it fails with the following exception:

Is it possible to initialize HMS without a agconnect-services.json and provide the keys at runtime?

Using a similar service (Fcm) we can initialize an app: