Request failed: client error (422) on sendVoipPush

[Maks273]

I'm calling from Ukraine to UK and get next. It's working well when calling in Ukraine. Could you help me to figure about what's wrong pls?

Error reasons:{ errors = { base = ( "No recipients. At least one user should be subscribed for 'apnsvoip' (through SDK or REST API)" ); }; }

Request failed: client error (422)

[djmckee]

Yep I have found this issue in inverse too 👍

[Maks273]

I got success here

let deviceIdentifier = UIDevice.current.identifierForVendor?.uuidString
        let subscription = QBMSubscription()
        subscription.notificationChannel = chanel
        subscription.deviceUDID = deviceIdentifier
        subscription.deviceToken = token
        QBRequest.createSubscription(subscription, successBlock: { _, _ in
            completion(true)
        }) { errorResponse in
            Crashlytics.crashlytics().log("ERROR createSubscription = \( errorResponse.error?.error?.localizedDescription ?? "")")
            completion(false)
        }

[IlliaChemolosov]

Привіт, @Maks273!

Слава Україні!

Ця помилка вказує на те, що користувач, якому йде дзвінок, не має підписки на voip push-сповіщення.

У твоєму випадку може бути кілька причин такої поведінки. Ймовірно, це пов'язано з різними середовищами (environments): тестовим (test) чи живим (live). Це може залежати від збірки білда (develop або production). Таким чином, у тебе може виникнути ситуація, коли "develop to develop" чи "prod to prod" дзвінки працюють, але "develop to prod" - ні.

Спочатку раджу перевірити, чи використовуються білди, підписані різними сертифікатами.

[IlliaChemolosov]

Hello @djmckee!

This error indicates that the user receiving the call does not have a subscription for voip push notifications.

In your case, there could be several reasons for this behavior, most likely due to different environments (test or live). It directly depends on the build (develop or production). So, you may have a situation where "develop to develop" or "prod to prod" calls work, but "develop to prod" does not. First and foremost, I recommend checking if you are using builds signed with different certificates.

[Maks273]

Героям Слава! @IlliaChemolosov

Так, причина з середовищами є! Але помітив, коли телефонував з dev to prod, то цей аккаунт видає таку саму помилку коли телефоную з dev => dev

Тепер протестував 2 акк на деві і все працює, але на test flight ні :( отримую 422 error

[Maks273]

@IlliaChemolosov so the issue is when I testing on test flight. Any tips to check what's causing the issue?

[IlliaChemolosov]

Hello @Maks273! Maybe you're currently using a sandbox certificate. I recommend creating a universal certificate and updating it within the QuickBlox admin panel.

[Maks273]

@IlliaChemolosov could you send a link to that article pls?

[IlliaChemolosov]

@Maks273 https://docs.quickblox.com/docs/ios-push-notifications#generate-a-certificate-signing-request

[Maks273]

@IlliaChemolosov do I need to generate aspn cer or it can be voip one?

[IlliaChemolosov]

@Maks273 It varies based on your app's requirements, especially if you need to receive regular pushes, such as when the app is in the background and notifications arrive. Typically, I create a universal certificate that supports both calls and regular messages (voip and apns). However, you can create individual certificates and add them depending on your requirements, our admin panel supports up to 3 certificates.