apple-push-notifications

Apple Push Notification service must incorporate the new root certificate (AAACertificateServices) - APNS certificate update [duplicate]

帅比萌擦擦* — Sat, 20 Feb 2021 00:34:02 +0000

Apple Push Notification service must incorporate the new root certificate (AAACertificateServices) - APNS certificate update [duplicate] 帅比萌擦擦* 2021-02-20 08:34:02

问题

I got this mail from Apple.

Note that Apple Push Notification service SSL provider certificates issued to you by Apple do not need be to updated at this time."

I configured Firebase as provider server and using APNS authentication Key.

I'm not sure what to do from my end. No documentation for this on apple site or any other site.

To be more specific should I do anything from my end or this should be taken care of by provider server like Firebase?

I'm wondering how come these instructions are not clearly mentioned by Apple?

回答1:

A more complete explanation about this can be found here.

来源：https://stackoverflow.com/questions/66169296/apple-push-notification-service-must-incorporate-the-new-root-certificate-aaace

标签

Missing Push Notification Entitlement: While Resigining ipa

眉间皱痕 — Thu, 18 Feb 2021 23:57:45 +0000

Missing Push Notification Entitlement: While Resigining ipa 眉间皱痕 2021-02-19 07:57:45

问题

Team,

We are releasing new update to our project, In the last version we dont have Push Notifications now are implementing all the process.

We work for a client where we used to send ipa file with our distribution profile (Push notifications are working for the ipa we are sending).

Once we send the working ipa, they will resign the ipa with there Distribution Profiles and Upload to appstore.

We have checked all the scenarios like, App Id enabled with Push Notification,SSl generated for Distribution (Is it mandatory for developing for developer also?).

The Resigning is successfull and we are able to upload the app to App Store.

But still we are getting the Below mail from Apple. Please Suggest what is the Solution for it

Missing Push Notification Entitlement - Your app includes an API for Apple's Push Notification service, but the aps-environment entitlement is missing from the app's signature. To resolve this, make sure your App ID is enabled for push notification in the Provisioning Portal. Then, sign your app with a distribution provisioning profile that includes the aps-environment entitlement. This will create the correct signature, and you can resubmit your app. See "Provisioning and Development" in the Local and Push Notification Programming Guide for more information. If your app does not use the Apple Push Notification service, no action is required. You may remove the API from future submissions to stop this warning. If you use a third-party framework, you may need to contact the developer for information on removing the API.

回答1:

You have to check if you have enabled push notifications in member center for the provisioning profile that you are using
You have to check if you have enabled push notifications in xcode capabilities

i.e

just check Entitlements.plist for the following key values

 <key>aps-environment</key>
    <string>production</string>

来源：https://stackoverflow.com/questions/39091591/missing-push-notification-entitlement-while-resigining-ipa

标签

app-store

provisioning-profile

appstore-approval

How to reset the Badge app icon number?

泄露秘密 — Thu, 18 Feb 2021 22:57:05 +0000

How to reset the Badge app icon number? 泄露秘密 2021-02-19 06:57:05

问题

I integrated the Push Notification to the CloudKit so that every change in the iCloud will pop up a notification on my iPhone and the badge app icon number will add one correspondingly. However, when I used the code:

application.applicationIconBadgeNumber = 0

to reset that number in the applicationDidBecomeActive(_ application: UIApplication), I noticed that the badge app icon number truly disappeared but if another new notification came again, the number won't start from one again as supposed but just add one to the original total number before the reset. Therefore the number is getting bigger and bigger. I wonder how to solve this problem?

回答1:

The problem is your apns payload, it contains badge count more than 1, you need to reset the payload as well.

When you set application.applicationIconBadgeNumber = 0 it just resets the badge count locally, not in the server.

Solution would be reset the badge count for the user in the server too.

Update: Apns Payload

{
    "aps" : {
        "alert" : {
            "title" : "Push",
            "body" : "Hello User"
        },
        "badge" : 5
    }

}

The app shows the badge count same as in the apns payload above, you need to reset the badge value in the payload above from server.

Hope it helps.

Cheers.

回答2:

I find that I should not only set the application side like:

UIApplication.sharedApplication().applicationIconBadgeNumber = 0

but I should also set the iCloud side in CKContainer. Therefore, the complete code is like below:

let operation = CKModifyBadgeOperation(badgeValue: 0)
operation.modifyBadgeCompletionBlock = {(error) in
    if let error = error{
        print("\(error)")
        return
    }
    application.applicationIconBadgeNumber = 0
}
CKContainer.default().add(operation)

来源：https://stackoverflow.com/questions/42720259/how-to-reset-the-badge-app-icon-number

标签

swift3

cloudkit

Unable to set header field “apns-push-type” in Apple Push Notification in javapns

会有一股神秘感。 — Tue, 16 Feb 2021 22:57:07 +0000

Unable to set header field “apns-push-type” in Apple Push Notification in javapns 会有一股神秘感。 2021-02-17 06:57:07

问题

I am unable to find any option (method, class, etc.) to set http header information using apns library.

This question is alrady present here: Unable to set header field "apns-push-type" in Apple Push Notification in javapns

But not answered so asking again. Sorry to post duplicate question.

来源：https://stackoverflow.com/questions/61278008/unable-to-set-header-field-apns-push-type-in-apple-push-notification-in-javapn

标签

javapns

javaapns

Firebase cloud messaging sendToDevice works properly but sendMulticast fails for the same list of tokens

会有一股神秘感。 — Tue, 16 Feb 2021 21:30:16 +0000

Firebase cloud messaging sendToDevice works properly but sendMulticast fails for the same list of tokens 会有一股神秘感。 2021-02-17 05:30:16

问题

For certain types of messages, I want to target users by FIRTokens vs topic, which are stored in my real-time database. I load these tokens with async/await and then decide if I want to send notifications to a topic vs a smaller list of users. The data loading code works as expected. But what's odd is that if I use .sendMulticast(payload), the notifications fail for all tokens in the list. On the other hand if I use .sendToDevice(adminFIRTokens, payload) the notification goes successfully to all my users. Right now my list has 2 tokens and with sendMulticast I have 2 failures and with sendToDevice I have 2 successes. Am I missing the point of what sendMulticast is supposed to do? According to the docs: Send messages to multiple devices:

The REST API and the Admin FCM APIs allow you to multicast a message to a list of device registration tokens. You can specify up to 500 device registration tokens per invocation.

So both should logically work. Then why does one fail and the other work? In fact with sendToDevice I get a multicastId in the response!

Here are some console outputs:

sendToDevice:

Sent filtered message notification successfully: 
{ 
  results: 
    [ 
      { messageId: '0:1...45' }, 
      { messageId: '16...55' } 
    ], 
    canonicalRegistrationTokenCount: 0, 
    failureCount: 0, 
    successCount: 2, 
    multicastId: 3008...7000 
}

sendMulticast:

List of tokens that caused failures: dJP03n-RC_Y:...MvPkTbuV,fDo1S8jPbCM:...2YETyXef

Cloud function to send the notification:

functions.database
  .ref("/discussionMessages/{autoId}/")
  .onCreate(async (snapshot, context) => {
    // console.log("Snapshot: ", snapshot);

    try {
      const groupsRef = admin.database().ref("people/groups");
      const adminUsersRef = groupsRef.child("admin");
      const filteredUsersRef = groupsRef.child("filtered");
      const filteredUsersSnapshot = await filteredUsersRef.once("value");
      const adminUsersSnapshot = await adminUsersRef.once("value");
      var adminUsersFIRTokens = {};
      var filteredUsersFIRTokens = {};

      if (filteredUsersSnapshot.exists()) {
        filteredUsersFIRTokens = filteredUsersSnapshot.val();
      }
      if (adminUsersSnapshot.exists()) {
        adminUsersFIRTokens = adminUsersSnapshot.val();
      }

      const topicName = "SpeechDrillDiscussions";
      const message = snapshot.val();
      const senderName = message.userName;
      const senderCountry = message.userCountryEmoji;
      const title = senderName + " " + senderCountry;
      const messageText = message.message;
      const messageTimestamp = message.messageTimestamp.toString();
      const messageID = message.hasOwnProperty("messageID")
        ? message.messageID
        : undefined;
      const senderEmailId = message.userEmailAddress;
      const senderUserName = getUserNameFromEmail(senderEmailId);

      const isSenderFiltered = filteredUsersFIRTokens.hasOwnProperty(
        senderUserName
      );

      var payload = {
        notification: {
          title: title,
          body: messageText,
          sound: "default",
        },
        data: {
          messageID: messageID,
          messageTimestamp: messageTimestamp,
        },
      };

      if (isSenderFiltered) {
        adminFIRTokens = Object.values(adminUsersFIRTokens);
        // payload.tokens = adminFIRTokens; //Needed for sendMulticast
        return (
          admin
            .messaging()
            .sendToDevice(adminFIRTokens, payload)
            // .sendMulticast(payload)
            .then(function (response) {
              if (response.failureCount === 0) {
                console.log(
                  "Sent filtered message notification successfully:",
                  response
                );
              } else {
                console.log(
                  "Sending filtered message notification failed for some tokens:",
                  response
                );
              }
              // if (response.failureCount > 0) {
              //   const failedTokens = [];
              //   response.responses.forEach((resp, idx) => {
              //     if (!resp.success) {
              //       failedTokens.push(adminFIRTokens[idx]);
              //     }
              //   });
              //   console.log(
              //     "List of tokens that caused failures: " + failedTokens
              //   );
              // }

              return true;
            })
        );
      } else {
        payload.topic = topicName;
        return admin
          .messaging()
          .send(payload)
          .then(function (response) {
            console.log("Notification sent successfully:", response);
            return true;
          });
      }
    } catch (error) {
      console.log("Notification sent failed:", error);
      return false;
    }
  });

回答1:

I think it's an issue of using a different payload structure.

This is the old one (without iOS specific info):

var payload = {
    notification: {
      title: title,
      body: messageText,
      sound: "default",
    },
    data: {
      messageID: messageID,
      messageTimestamp: messageTimestamp,
    },
  };

Whereas this is the new version (apns has iOS specific info)

var payload = {
    notification: {
      title: title,
      body: messageText,
    },
    data: {
      messageID: messageID,
      messageTimestamp: messageTimestamp,
    },
    apns: {
      payload: {
        aps: {
          sound: "default",
        },
      },
    },
  };

With the new structure, both send and sendMulticast are working properly. Which would fail to send or give errors like apns key is not supported in payload.

The new function:

functions.database
  .ref("/discussionMessages/{autoId}/")
  .onCreate(async (snapshot, context) => {
    // console.log("Snapshot: ", snapshot);

    try {
      const groupsRef = admin.database().ref("people/groups");
      const adminUsersRef = groupsRef.child("admin");
      const filteredUsersRef = groupsRef.child("filtered");
      const filteredUsersSnapshot = await filteredUsersRef.once("value");
      const adminUsersSnapshot = await adminUsersRef.once("value");
      var adminUsersFIRTokens = {};
      var filteredUsersFIRTokens = {};

      if (filteredUsersSnapshot.exists()) {
        filteredUsersFIRTokens = filteredUsersSnapshot.val();
      }
      if (adminUsersSnapshot.exists()) {
        adminUsersFIRTokens = adminUsersSnapshot.val();
      }

      // console.log(
      //   "Admin and Filtered Users: ",
      //   adminUsersFIRTokens,
      //   " ",
      //   filteredUsersFIRTokens
      // );

      const topicName = "SpeechDrillDiscussions";
      const message = snapshot.val();

      // console.log("Received new message: ", message);

      const senderName = message.userName;
      const senderCountry = message.userCountryEmoji;
      const title = senderName + " " + senderCountry;
      const messageText = message.message;
      const messageTimestamp = message.messageTimestamp.toString();
      const messageID = message.hasOwnProperty("messageID")
        ? message.messageID
        : undefined;
      const senderEmailId = message.userEmailAddress;
      const senderUserName = getUserNameFromEmail(senderEmailId);

      const isSenderFiltered = filteredUsersFIRTokens.hasOwnProperty(
        senderUserName
      );

      console.log(
        "Will attempt to send notification for message with message id: ",
        messageID
      );

      var payload = {
        notification: {
          title: title,
          body: messageText,
        },
        data: {
          messageID: messageID,
          messageTimestamp: messageTimestamp,
        },
        apns: {
          payload: {
            aps: {
              sound: "default",
            },
          },
        },
      };
      console.log("Is sender filtered? ", isSenderFiltered);

      if (isSenderFiltered) {
        adminFIRTokens = Object.values(adminUsersFIRTokens);
        console.log("Sending filtered notification with sendMulticast()");
        payload.tokens = adminFIRTokens; //Needed for sendMulticast
        return admin
          .messaging()
          .sendMulticast(payload)
          .then((response) => {
            console.log(
              "Sent filtered message (using sendMulticast) notification: ",
              JSON.stringify(response)
            );
            if (response.failureCount > 0) {
              const failedTokens = [];
              response.responses.forEach((resp, idx) => {
                if (!resp.success) {
                  failedTokens.push(adminFIRTokens[idx]);
                }
              });
              console.log(
                "List of tokens that caused failures: " + failedTokens
              );
            }
            return true;
          });
      } else {
        console.log("Sending topic message with send()");
        payload.topic = topicName;
        return admin
          .messaging()
          .send(payload)
          .then((response) => {
            console.log(
              "Sent topic message (using send) notification: ",
              JSON.stringify(response)
            );
            return true;
          });
      }
    } catch (error) {
      console.log("Notification sent failed:", error);
      return false;
    }
  });

来源：https://stackoverflow.com/questions/66075132/firebase-cloud-messaging-sendtodevice-works-properly-but-sendmulticast-fails-for

标签

javascript

firebase

The provided registration token is not registered

谁说胖子不能爱 — Tue, 16 Feb 2021 12:39:19 +0000

The provided registration token is not registered 谁说胖子不能爱 2021-02-16 20:39:19

问题

I'm trying to send push notification for iOS via Google cloud functions but it returns error that The provided registration token is not registered. But I've checked it by debugging my app and the FCM registration token is correct. After that I've tried to send push notification via Firebase console to single device by providing FCM token but it failed due to Unregistered registration token. How this happens because there is no issue with device FCM token?

回答1:

I think it should be some careless mistake, you should make sure the things below:

The token is same with -[FIRMessagingDelegate messaging:(FIRMessaging *)messaging didReceiveRegistrationToken:(NSString *)fcmToken]
The GoogleService-Info.plist is downloaded from the same account with your Firebase push console.
Updated to the latest Firebase SDK.

From the Google Firebase document are some description of your error The provided registration token is not registered.

The provided registration token is not registered. A previously valid registration token can be unregistered for a variety of reasons, including:

The client app unregistered itself from FCM.

The client app was automatically unregistered. This can happen if the user uninstalls the application or, on iOS, if the APNS Feedback Service reported the APNS token as invalid.

The registration token expired. For example, Google might decide to refresh registration tokens or the APNS token may have expired for iOS devices.

The client app was updated, but the new version is not configured to receive messages. For all these cases, remove this registration token and stop using it to send messages.

来源：https://stackoverflow.com/questions/53009207/the-provided-registration-token-is-not-registered

标签

objective-c

firebase

xcodebuild Unsigned IPA - Missing Push Notification Entitlement (Work when signing directly the App in XCode)

风流意气都作罢 — Thu, 11 Feb 2021 08:55:54 +0000

xcodebuild Unsigned IPA - Missing Push Notification Entitlement (Work when signing directly the App in XCode) 风流意气都作罢 2021-02-11 16:55:54

问题

Context : XCODE 12.0.1

I'm using Push Notifications in Ionic. The configuration is OK. I added the Push Notification Capability in Signing and Capabilities . I build my app and I do npx cap open ios, and I do Product > Archive and then it asks me to sign the app, I sign it, and OK. When I test Notifications, everything works well.

Problem : I need to generate unsigned IPA with xcodebuild for my client. He wants to sign it himself. But when I generate the xcarchive (unsigned IPA), then he tells me that after signing it, Notifications don't work, and he received this message when he tried to upload it on App Store :

Missing Push Notification Entitlement - Your app appears to register with the Apple Push Notification service, but the app signature's entitlements do not include the 'aps-environment' entitlement. If your app uses the Apple Push Notification service, make sure your App ID is enabled for Push Notification in the Provisioning Portal, and resubmit after signing your app with a Distribution provisioning profile that includes the 'aps-environment' entitlement. Xcode does not automatically copy the aps-environment entitlement from provisioning profiles at build time. This behavior is intentional. To use this entitlement, either enable Push Notifications in the project editor's Capabilities pane, or manually add the entitlement to your entitlements file. For more information, see https://developer.apple.com/library/content/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/HandlingRemoteNotifications.html#//apple_ref/doc/uid/TP40008194-CH6-SW1.

How I generate the xcarchive : xcodebuild -workspace ios/App/App.xcworkspace -allowProvisioningUpdates -scheme App -sdk iphoneos -configuration Release -destination generic/platform=iOS -archivePath output/ios/App.xcarchive archive CODE_SIGNING_REQUIRED="NO" CODE_SIGNING_ALLOWED="NO"

Signing manually or automatically don't solve the problem.

Do you know why I get these errors when using xcodebuild (App Store Error, Push Notification Error) ?

It looks a little bit like this problem : Missing Push Notification Entitlement: While Resigining ipa

Do you know if i'm using xcodebuild the wrong way?

EDIT 1 : If I use this software https://github.com/maciekish/iReSign , to resign my xcarchive, it works... But clients won't agree to use some mystical softwares. I tried to compare my "normally XCODE signed" .ipa with the .ipa signed by this software. The only thing that differs is that there is an entitlements.plist file in the folder in the second case. And this file looks like this :

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>application-identifier</key>
    <string>**TEAMID*.*APP-ID*</string>
    <key>aps-environment</key>
    <string>production</string>
    <key>com.apple.developer.applesignin</key>
    <array>
        <string>Default</string>
    </array>
    <key>com.apple.developer.team-identifier</key>
    <string>**TEAM ID**</string>
    <key>get-task-allow</key>
    <false/>
    <key>keychain-access-groups</key>
    <array>
        <string>TeamID.*</string>
        <string>com.apple.token</string>
    </array>
</dict>
</plist>

But I can find this in the "normally signed" ipa on the embedded.mobileprovision file, there is the entitlements section containing these lines... I can't understand why this tool made it work

回答1:

I finally solved my problem. The command line I used for generating the xcarchive was wrong. I just had luck by testing this line without the "SIGNING" parameters :

xcodebuild -workspace ios/App/App.xcworkspace -allowProvisioningUpdates -scheme App -sdk iphoneos -configuration Release -destination generic/platform=iOS -archivePath output/ios/App.xcarchive archive

I found these parameters in some Medium page, and I don't know why I was using them.

来源：https://stackoverflow.com/questions/65687353/xcodebuild-unsigned-ipa-missing-push-notification-entitlement-work-when-signi

标签

xcode

ionic-framework

xcodebuild Unsigned IPA - Missing Push Notification Entitlement (Work when signing directly the App in XCode)

你离开我真会死。 — Thu, 11 Feb 2021 08:54:58 +0000

xcodebuild Unsigned IPA - Missing Push Notification Entitlement (Work when signing directly the App in XCode) 你离开我真会死。 2021-02-11 16:54:58

问题

Context : XCODE 12.0.1

Signing manually or automatically don't solve the problem.

Do you know why I get these errors when using xcodebuild (App Store Error, Push Notification Error) ?

It looks a little bit like this problem : Missing Push Notification Entitlement: While Resigining ipa

Do you know if i'm using xcodebuild the wrong way?

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>application-identifier</key>
    <string>**TEAMID*.*APP-ID*</string>
    <key>aps-environment</key>
    <string>production</string>
    <key>com.apple.developer.applesignin</key>
    <array>
        <string>Default</string>
    </array>
    <key>com.apple.developer.team-identifier</key>
    <string>**TEAM ID**</string>
    <key>get-task-allow</key>
    <false/>
    <key>keychain-access-groups</key>
    <array>
        <string>TeamID.*</string>
        <string>com.apple.token</string>
    </array>
</dict>
</plist>

But I can find this in the "normally signed" ipa on the embedded.mobileprovision file, there is the entitlements section containing these lines... I can't understand why this tool made it work

回答1:

I finally solved my problem. The command line I used for generating the xcarchive was wrong. I just had luck by testing this line without the "SIGNING" parameters :

I found these parameters in some Medium page, and I don't know why I was using them.

来源：https://stackoverflow.com/questions/65687353/xcodebuild-unsigned-ipa-missing-push-notification-entitlement-work-when-signi

标签

xcode

ionic-framework

APNS connection failure

北城以北 — Tue, 09 Feb 2021 22:16:05 +0000

APNS connection failure 北城以北 2021-02-10 06:16:05

问题

Facing problem with APNS push services at client end. Server side is ok and it sends push to APNS properly as particular devices get stuck at some moment. Here are the server logs.

VOIP Push: Push notification waiting by APNs gateway.

VOIP Push: Push notification accepted by APNs gateway.

Here are the console logs of effected device


    default 09:16:30.203262 +0400   apsd    Connection 1507: enabling TLS
    default 09:16:30.203409 +0400   apsd    Connection 1507: starting, TC(0x0)
    default 09:16:30.203504 +0400   apsd    [C1507 DBE7C1B4-DC94-4B2A-BD21-63661595E267 Hostname#45fde594:443 tcp, url hash: f51ce5f3, tls] start
    default 09:16:30.204664 +0400   apsd    nw_connection_report_state_with_handler_on_nw_queue [C1507] reporting state preparing
    default 09:16:30.205294 +0400   mDNSResponder   [R80990] DNSServiceCreateConnection START PID[99](apsd)
    default 09:16:30.205592 +0400   mDNSResponder   [R80991] DNSServiceGetAddrInfo(C000D000, 0, 0, ) START PID[99](apsd)
    default 09:16:30.206815 +0400   apsd    Task . setting up Connection 1507
    default 09:16:30.208190 +0400   apsd    nw_connection_report_state_with_handler_on_nw_queue [C1507] reporting state failed error DNS Error: NoSuchRecord
    error   09:16:30.208282 +0400   apsd    Connection 1507: received failure notification
    error   09:16:30.208361 +0400   apsd    Connection 1507: failed to connect 12:8, reason -1
    error   09:16:30.208448 +0400   apsd    Connection 1507: encountered error(12:8)
    default 09:16:30.208522 +0400   apsd    Connection 1507: is being canceled
    default 09:16:30.208600 +0400   mDNSResponder   [R80990] DNSServiceCreateConnection STOP PID[99](apsd)
    default 09:16:30.208678 +0400   mDNSResponder   [R80991] DNSServiceGetAddrInfo() STOP PID[99](apsd)
    default 09:16:30.208848 +0400   apsd    Connection 1507: summary for unused connection {protocol="(null)", domain_lookup_duration_ms=0, connect_duration_ms=0, secure_connection_duration_ms=0, idle_duration_ms=0}
    default 09:16:30.208932 +0400   apsd    [C1507 DBE7C1B4-DC94-4B2A-BD21-63661595E267 Hostname#45fde594:443 tcp, url hash: f51ce5f3, tls] cancel
    default 09:16:30.209009 +0400   apsd    [C1507 Hostname#45fde594:443 tcp, url hash: f51ce5f3, tls] cancelled
    default 09:16:30.209091 +0400   apsd    0.000s [C1507 29735B49-F0FB-40A5-A092-F15E19D8B4B0 Hostname#45fde594:443 resolver path=satisfied (Path is satisfied), interface: en0, ipv4, dns] path:start
    default 09:16:30.209174 +0400   apsd    0.000s [C1507 29735B49-F0FB-40A5-A092-F15E19D8B4B0 Hostname#45fde594:443 resolver path=satisfied (Path is satisfied), interface: en0, ipv4, dns] path:satisfied
    default 09:16:30.209260 +0400   apsd    0.001s [C1507 29735B49-F0FB-40A5-A092-F15E19D8B4B0 Hostname#45fde594:443 resolver path=satisfied (Path is satisfied), interface: en0, ipv4, dns] resolver:start_dns
    default 09:16:30.209341 +0400   apsd    0.003s [C1507 29735B49-F0FB-40A5-A092-F15E19D8B4B0 Hostname#45fde594:443 resolver path=satisfied (Path is satisfied), interface: en0, ipv4, dns] path:trigger
    default 09:16:30.209427 +0400   apsd    0.004s [C1507 29735B49-F0FB-40A5-A092-F15E19D8B4B0 Hostname#45fde594:443 resolver path=satisfied (Path is satisfied), interface: en0, ipv4, dns] resolver:receive_dns DNS Error: NoSuchRecord
    default 09:16:30.209509 +0400   apsd    0.005s [C1507] path:cancel
    default 09:16:30.209821 +0400   apsd    nw_connection_report_state_with_handler_on_nw_queue [C1507] reporting state cancelled error DNS Error: NoSuchRecord
    default 09:16:30.209998 +0400   apsd    Task . can retry(N) with reason(2) for error [12:8]
    default 09:16:30.211029 +0400   apsd    _CFNetworkIsConnectedToInternet returning 1, flagsValid: 1, flags: 0x2
    error   09:16:30.211367 +0400   apsd    Task . HTTP load failed, 0/0 bytes (error code: -1003 [12:8])
    default 09:16:30.211510 +0400   apsd    Task . summary for task failure {transaction_duration_ms=9, response_status=0, cache_hit=0}
    default 09:16:30.211758 +0400   apsd    removing all entries config 0x100f3bfc0
    default 09:16:30.212028 +0400   apsd    removing all entries config 0x100f3bfc0
    default 09:16:30.212151 +0400   apsd     Calling configuration completion blocks, expiration date Thu Dec 12 09:31:30 2019 error: Error Domain=NSURLErrorDomain Code=-1003 "A server with the specified hostname could not be found." UserInfo={NSUnderlyingError=0x102121bc0 {Error Domain=kCFErrorDomainCFNetwork Code=-1003 UserInfo={_kCFStreamErrorCodeKey=8, _kCFStreamErrorDomainKey=12}}, NSErrorFailingURLStringKey=, NSErrorFailingURLKey=, _kCFStreamErrorDomainKey=12, _kCFStreamErrorCodeKey=8, NSLocalizedDescription=A server with the specified hostname could not be found.}
    default 09:16:30.212393 +0400   apsd    APSTCPStream  got config   -- opened? YES
    default 09:16:30.212593 +0400   apsd    Failed to load config bag: Error Domain=NSURLErrorDomain Code=-1003 "A server with the specified hostname could not be found." UserInfo={NSUnderlyingError=0x102121bc0 {Error Domain=kCFErrorDomainCFNetwork Code=-1003 UserInfo={_kCFStreamErrorCodeKey=8, _kCFStreamErrorDomainKey=12}}, NSErrorFailingURLStringKey=, NSErrorFailingURLKey=, _kCFStreamErrorDomainKey=12, _kCFStreamErrorCodeKey=8, NSLocalizedDescription=A server with the specified hostname could not be found.}
    default 09:16:30.212700 +0400   apsd    Using DNS TXT record lookup to determine load balance count for development
    default 09:16:30.212786 +0400   apsd     performing DNS lookup for 
    default 09:16:30.213329 +0400   mDNSResponder   [R80992] DNSServiceQueryRecord(0, 0, , TXT) START PID[99](apsd)
    default 09:16:30.214890 +0400   apsd    Closing  with environment [development]
    default 09:16:30.215049 +0400   mDNSResponder   [R80992] DNSServiceQueryRecord(0, 0, , TXT) STOP PID[99](apsd)
    default 09:16:30.215730 +0400   apsd    : Stream error occurred for  onInterface NonCellular: Error Domain=APSErrorDomain Code=1 UserInfo={NSLocalizedDescription=}
    default 09:16:30.215855 +0400   apsd    : Calling into AWD for ConnectionDisconnected (withError)
    default 09:16:30.217664 +0400   apsd    : AWD for ConnectionDisconnected (withError) finished
    default 09:16:30.217741 +0400   apsd     _disconnectStream for interface: NonCellular
    default 09:16:30.217821 +0400   apsd     asked to change isSuspended=NO to NO
    default 09:16:30.217896 +0400   apsd    Closing  with environment [development]
    default 09:16:30.217972 +0400   apsd    : enableNonCellularConnections changed to NO
    default 09:16:30.218458 +0400   apsd    Connection closed development NonCellular
    default 09:16:30.218633 +0400   apsd     canUseProxy? NO deviceConfiguration NO  isNearby NO
    default 09:16:30.218706 +0400   apsd     received courierConnectionStatusDidChange from .
    default 09:16:30.218877 +0400   apsd     canUseProxy? NO deviceConfiguration NO  isNearby NO
    default 09:16:30.219036 +0400   apsd     canUseProxy? NO deviceConfiguration NO  isNearby NO
    default 09:16:30.219115 +0400   apsd     updating network guidance isConnected? YES
    default 09:16:30.219271 +0400   apsd     canUseProxy? NO deviceConfiguration NO  isNearby NO
    default 09:16:30.219404 +0400   apsd     canUseProxy? NO deviceConfiguration NO  isNearby NO
    default 09:16:30.219532 +0400   apsd    : Disconnected in response to connection failure on interface NonCellular. (Consecutive failures: 24) isConnected NO onInterface None  shouldUseDualChannel YES. Connected on 0 interfaces.
    default 09:16:30.219596 +0400   apsd    Created metric container: 0x130002 succeeded? YES
    default 09:16:30.220000 +0400   apsd     Connection method alternative changed to 1
    default 09:16:30.220094 +0400   apsd    Advising client to enter reconnect mode in response to a connection failure since currently in reconnect mode
    default 09:16:30.220166 +0400   apsd    Resuming push keep alive timer in normal mode with action PCActionShrinkPushKeepAliveInterval
    default 09:16:30.220230 +0400   apsd    Last timer interruption was early: []. Expected fire time was [].
    default 09:16:30.220300 +0400   apsd    WiFi growth algorithm-IPv4: received action PCActionShrinkPushKeepAliveInterval while in stage Backoff
    default 09:16:30.220366 +0400   apsd    {keep alive interval = 600, state = Backoff, next recalibration date = (null)}: adjustGrowthAlgorithmMode. {lastMode: Defaults, currentMode: Defaults}
    default 09:16:30.220431 +0400   apsd     created 
    default 09:16:30.220506 +0400   apsd    Started simple timer  with fire date [2019-12-12 09:27:05 +0400]
    default 09:16:30.220713 +0400   apsd     created preventSleepTimer  and fireTimer  on queue 
    default 09:16:30.221159 +0400   apsd    Enabling power monitoring for  - 6 timers
    default 09:16:30.221275 +0400   apsd     Existing wake at (null) re-scheduling to 2019-12-12 09:26:50 +0400 with leeway of 0
    default 09:16:30.221551 +0400   apsd    Request to schedule wake 1 date 2019-12-12 09:26:50 +0400 leeway 0 service identifier com.apple.apsd(sandbox.push.apple.com)-NonCellular unique identifier 
    default 09:16:30.221693 +0400   apsd     calculating _earlyFireDate. powerStateDetectionSupported = NO = (detectionSupported(YES) && (wwanIsUp(NO) || ! internetReachable(YES)))
    default 09:16:30.221779 +0400   apsd    Last system wake date (2019-12-12 09:11:10 +0400) was longer than half of the timer duration, so setting minimum fire date to fire date.
    default 09:16:30.221867 +0400   apsd     Device is plugged in, overriding earlyFireProportion to be 1.0
    default 09:16:30.222061 +0400   apsd     Calculated minimum fire date [2019-12-12 09:27:05 +0400] (100%) with fire date [2019-12-12 09:27:05 +0400], start date [2019-12-12 09:16:30 +0400], minimum early fire proportion 0, power state detection supported: no, in high power state: no, early fire constant interval 0.000000
    default 09:16:30.222194 +0400   apsd    PCConnectionManager was stopped by client
    default 09:16:30.222261 +0400   apsd    Invalidating timer 
    default 09:16:30.222322 +0400   apsd    Invalidating simple timer 
    default 09:16:30.222699 +0400   apsd    Scheduling a wake for date  leeway 0 wake identifier 
    default 09:16:30.224084 +0400   apsd    Wake schedule for ''() completed for [] (took 0.002 seconds; result code 0)
    default 09:16:30.225070 +0400   apsd    Canceling system wake for simpletimer [2019-12-12 09:26:50 +0400]
    default 09:16:30.225159 +0400   apsd    Request to schedule wake 0 date 2019-12-12 09:26:50 +0400 leeway 0 service identifier com.apple.apsd(sandbox.push.apple.com)-NonCellular unique identifier 
    default 09:16:30.225385 +0400   apsd    APSCourier  adjusting connection. Connected on 0 interfaces. Current link quality: 
    default 09:16:30.225498 +0400   apsd    Disabling power monitoring for  - 5 timers
    default 09:16:30.225646 +0400   apsd     canUseProxy? NO deviceConfiguration NO  isNearby NO
    default 09:16:30.225720 +0400   apsd     calling _connectStream with interface preference NonCellular
    default 09:16:30.225800 +0400   apsd     attempting to _connectStream. currently onInterface None consecutiveFailures 24 preference NonCellular shouldUseDualChannel YES. Connected on 0 interfaces.
    default 09:16:30.225869 +0400   apsd    _getClientIdentity: already had identity: 
    default 09:16:30.225929 +0400   apsd     _connectStream - Stopping the connectionManager on our attemptInterface NonCellular
    default 09:16:30.225990 +0400   apsd    PCConnectionManager was stopped by client
    default 09:16:30.226047 +0400   apsd    : isWWANUsable NO  isWiFiUsable YES onInterface NonCellular
    default 09:16:30.226112 +0400   apsd    : enableNonCellularConnections changed to YES
    default 09:16:30.226165 +0400   apsd     Opening stream on interface NonCellular
    default 09:16:30.226214 +0400   apsd    Cancelling scheduled wake for  wake identifier 
    default 09:16:30.226560 +0400   apsd    Opening  with environment [development]
    default 09:16:30.226659 +0400   apsd    loadConfigurationForEnvironment:  development interface: NonCellular
    default 09:16:30.227135 +0400   apsd    Task . resuming, QOS(0x15) Voucher (null)
    default 09:16:30.227218 +0400   apsd    Wake cancel for ''() completed for [] (took 0.002 seconds; result code 0)
    default 09:16:30.227330 +0400   apsd    Opening stream onInterface: NonCellular, development
    default 09:16:30.227496 +0400   apsd    : Connecting courier stream using configuration bag at  and port TCP 443
    default 09:16:30.227752 +0400   apsd    Closing  with environment [development]
    default 09:16:30.227837 +0400   apsd    Task . {strength 0, tls 4, ct 0, sub 0, sig 1, ciphers 0, bundle 1, builtin 0}
    default 09:16:30.228815 +0400   apsd    Connection 1508: enabling TLS
    default 09:16:30.228964 +0400   apsd    Connection 1508: starting, TC(0x0)
    default 09:16:30.229353 +0400   apsd    [C1508 F67A490F-3214-41AE-AC96-0CD52FC88397 Hostname#45fde594:443 tcp, url hash: f51ce5f3, tls] start
    default 09:16:30.230101 +0400   symptomsd   NBSM: received symptom that apsd is failing on WiFi in state: idle
    default 09:16:30.231119 +0400   apsd    nw_connection_report_state_with_handler_on_nw_queue [C1508] reporting state preparing
    default 09:16:30.231365 +0400   mDNSResponder   [R80993] DNSServiceCreateConnection START PID[99](apsd)
    default 09:16:30.231620 +0400   mDNSResponder   [R80994] DNSServiceGetAddrInfo(C000D000, 0, 0, ) START PID[99](apsd)
    default 09:16:30.232216 +0400   apsd    Task . setting up Connection 1508
    default 09:16:30.233279 +0400   mDNSResponder   [R80993] DNSServiceCreateConnection STOP PID[99](apsd)
    default 09:16:30.233462 +0400   mDNSResponder   [R80994] DNSServiceGetAddrInfo() STOP PID[99](apsd)
    default 09:16:30.233983 +0400   apsd    nw_connection_report_state_with_handler_on_nw_queue [C1508] reporting state failed error DNS Error: NoSuchRecord
    error   09:16:30.234066 +0400   apsd    Connection 1508: received failure notification
    error   09:16:30.234124 +0400   apsd    Connection 1508: failed to connect 12:8, reason -1
    error   09:16:30.234179 +0400   apsd    Connection 1508: encountered error(12:8)
    default 09:16:30.234443 +0400   apsd    Connection 1508: is being canceled
    default 09:16:30.234525 +0400   apsd    Connection 1508: summary for unused connection {protocol="(null)", domain_lookup_duration_ms=0, connect_duration_ms=0, secure_connection_duration_ms=0, idle_duration_ms=0}
    default 09:16:30.234584 +0400   apsd    [C1508 F67A490F-3214-41AE-AC96-0CD52FC88397 Hostname#45fde594:443 tcp, url hash: f51ce5f3, tls] cancel
    default 09:16:30.234681 +0400   apsd    [C1508 Hostname#45fde594:443 tcp, url hash: f51ce5f3, tls] cancelled

回答1:

Encountered a similar situation where no push was arriving, and dns errors were logged when querying sandox.push.apple.com

A fix was to change the phones to use an alternative DNS like Google (8.8.8.8) or Cloudflare (1.1.1.1) in the wifi settings.

来源：https://stackoverflow.com/questions/59298620/apns-connection-failure

标签

swift

push-notification