Can't send "contentAvailable" on it's own

[vapor]

Can't send "contentAvailable" on it's own

[0xTim]

I'm going to close this as it looks like there's a workaround and if you're having issues you should create an issue at https://github.com/kylebrowning/APNSwift

[marekpridal]

This is the workaround which work for me

request.apns.send(rawBytes: payload,
                                  pushType: APNSwiftConnection.PushType.background,
                                  to: apnsToken,
                                  expiration: nil,
                                  priority: nil,
                                  collapseIdentifier: nil,
                                  topic: nil,
                                  logger: request.logger,
                                  apnsID: nil)

[idelfonsog2]

Hi @MacFriis did you enable the background+remote notifications in the background modes?

which is different from the capability of push notification

[MacFriis]

Hi @idelfonsog2, yes I have had this on all along, and I have made a lot of Remote Notification on Apple devices using other libraries for C#, and finished services where I can get the "content-available" to work without having a message within the notification.
I can't see what I'm doing wrong if it is working in the library.

[0xTim]

This is probably better suited to https://github.com/kylebrowning/APNSwift as this package just proxies directly to that and that package does the actual sending.

Any idea on why this may be happening @kylebrowning ?

[kylebrowning]

Yup. This should be handle upstream. I’ll take a look!

[magnolialogic]

+1, running into this while porting a service from Python/PyAPNs2 to vapor/apns

[magnolialogic]

@MacFriis FWIW using apns.send(rawBytes: ...) works for me, instead of apns.send(payload: ...) or apns.send(notification: ...)

[FriisConsultApS]

@magnolialogic I'll give it a try

[marekpridal]

@magnolialogic can you please send example code how you were able to send an update notification using rawBytes? I wasn't able to do so with code below.

Payload:
"{
    "aps" : { 
         "content-available" : 1 
    }
}"

request.apns.send(rawBytes: payload,
                                  pushType: APNSwiftConnection.PushType.alert,
                                  to: apnsToken,
                                  expiration: nil,
                                  priority: nil,
                                  collapseIdentifier: nil,
                                  topic: nil,
                                  logger: request.logger,
                                  apnsID: nil)

EDIT: Got this working by using APNSwiftConnection.PushType.background although testing of this feature on iOS is really tricky.

[DanSessions]

Can anyone share the code for the workaround? Can't seem to get it working.

[FriisConsultApS]

Sorry, I have abandon the servicer side swift all together... now back on dotnet 6

[idelfonsog2]

Thank you so much @marekpridal for sharing.

Mine was the followoing:

private func sendPushes(_ tokens: [String], alert: APNSwiftAlert , on req: Request) async throws {
...
      for token in tokens {
         do {
            try await req.apns.send(payload,
                                    pushType: .alert,
                                    to: token,
                                    with: JSONEncoder(),
                                    expiration: Date().addingTimeInterval(3600),
                                    priority: 10,
                                    collapseIdentifier: nil,
                                    topic: applicationTopic,
                                    logger: req.logger,
                                    apnsID: apnsID).get()
...
// to complete

[kylebrowning]

    let payload = APNSPayload(hasContentAvailable: true)
        let acme = AcmeNotification(acme1: "hey", acme2: 2, aps: payload)
        try! await req.apns.client.send(acme, pushType: .background, to: dt, priority: 5)

this worked for me.