Broadcast with iOS Devices Not Working

Hi!

I am having trouble sending a broadcast push notification to all iOS / iOS & Android devices. Im currently using a Development account and have success sending a message to a specific device id on iOS & Android, as well as Broadcasting to only Android devices. 

 

Can you please help me troubleshoot this issue? 

 

Thank you

 

Ray

Didn't find what you were looking for?

New post

Comments

7 comments

  • Hi Jared,

    I'm seeing quite a bit of errors in your Error Console (Located in the bottom, right-hand corner of the screen).

    When you get Rejected Device Tokens from Apple, this is likely the cause why your iOS pushes are not going out, so you'll need to resolve that before you can send to your iOS devices.

    To fix it, you can follow the guide we have on Troubleshooting Rejected Device Tokens

    0
  • Thanks Michael,

     

    I went through an verified the configuration i have, unfortunately the Cert, Bundle Id, API Key and Environment seem to be correct. 

    Log from iOS Console: 
    [UAirship executeUnsafeTakeOff:] [Line 186] UAirship Take Off! Lib Version: 6.4.0 App Key: XXXXXXXXXXXXX Production: NO

    ..
    [UAPush appRegisteredForRemoteNotificationsWithDeviceToken:] [Line 1101] Application registered device token: XXXXXXXXXXX

    The APN Device Token can be looked up here: https://go.urbanairship.com/apps/9NdmefX8Ru-ANK5EiNlVVA/device_lookup/ and I see that it has green lights for (Installed, Opted In, and Background)

     

    Thank you for showing my the Error Console, I verified that there was not a message for my specific device id. 

     

    Thank you for looking into this!

    Ray

    0
  • Ray,

    Can you verify within your logs the following:

    1. You do not see a log line that says something like "no valid 'aps-environment' entitlement string found for application" in your Xcode logs

    2. API Key is currently set to 9NdmefX8Ru-ANK5EiNlVVA

    3. Also, if you could log the Device Token, that would be great!

    0
  • Hi Michael

     

    1. Sorry I don't see those logs present, I attached the relevant logs from the app start below

    2. This seems to be the correct key

    3. Device Token: cad33e66d74c0d109cf165499d29b3669956b9d0829f0dcda048f549f4715071

     

    Logs: 

    2016-07-12 14:34:12.315 BarkBox[380:70992] [I] +[UAirship executeUnsafeTakeOff:] [Line 186] UAirship Take Off! Lib Version: 6.4.0 App Key: 9NdmefX8Ru-ANK5EiNlVVA Production: NO.
    2016-07-12 14:34:12.316 BarkBox[380:70992] [D] +[UAirship executeUnsafeTakeOff:] [Line 194] Setting User-Agent for UA requests to BarkBox 30 (iPhone; iPhone OS 9.3.2; UALib 6.4.0; 9NdmefX8Ru-ANK5EiNlVVA; en_US)
    2016-07-12 14:34:12.322 BarkBox[380:70992] Channel ID: b918c0a7-d990-4e09-a4cd-aee69cf458ca
    2016-07-12 14:34:12.322 BarkBox[380:70992] [D] -[UANamedUser update] [Line 60] New or re-install, skipping named user update.
    2016-07-12 14:34:12.336 BarkBox[380:70992] [I] +[UAirship executeUnsafeTakeOff:] [Line 263] Automatic setup enabled.
    2016-07-12 14:34:12.336 BarkBox[380:70992] [D] +[UAAppDelegateProxy swizzle:implementation:class:] [Line 101] Swizzling implementation for application:handleActionWithIdentifier:forRemoteNotification:completionHandler: class BCAppDelegate
    2016-07-12 14:34:12.340 BarkBox[380:70992] [D] +[UAAppDelegateProxy swizzle:implementation:class:] [Line 106] Adding implementation for application:handleActionWithIdentifier:forRemoteNotification:withResponseInfo:completionHandler: class BCAppDelegate
    2016-07-12 14:34:12.340 BarkBox[380:70992] [D] +[UAAppDelegateProxy swizzle:implementation:class:] [Line 106] Adding implementation for application:didReceiveRemoteNotification:fetchCompletionHandler: class BCAppDelegate
    2016-07-12 14:34:12.340 BarkBox[380:70992] [D] +[UAAppDelegateProxy swizzle:implementation:class:] [Line 106] Adding implementation for application:didReceiveRemoteNotification: class BCAppDelegate
    2016-07-12 14:34:12.340 BarkBox[380:70992] [D] +[UAAppDelegateProxy swizzle:implementation:class:] [Line 101] Swizzling implementation for application:didRegisterForRemoteNotificationsWithDeviceToken: class BCAppDelegate
    2016-07-12 14:34:12.342 BarkBox[380:70992] [D] +[UAAppDelegateProxy swizzle:implementation:class:] [Line 106] Adding implementation for application:didRegisterUserNotificationSettings: class BCAppDelegate
    2016-07-12 14:34:12.342 BarkBox[380:70992] [D] +[UAAppDelegateProxy swizzle:implementation:class:] [Line 106] Adding implementation for application:didFailToRegisterForRemoteNotificationsWithError: class BCAppDelegate
    2016-07-12 14:34:12.347 BarkBox[380:70992] [D] -[UAPush updateRegistration] [Line 906] APNS registration is out of date, updating.
    2016-07-12 14:34:12.347 BarkBox[380:70992] [D] -[UAPush updateAPNSRegistration] [Line 1052] Registering for user notification types 7.
    2016-07-12 14:34:12.367 BarkBox[380:70992] [D] -[UAAnalytics addEvent:] [Line 248] Adding app_init event CC270198-9059-4B25-9122-5D2F9BACBC01.
    2016-07-12 14:34:12.385 BarkBox[380:70992] [D] -[UAChannelRegistrar updateChannel:channelLocation:withPayload:] [Line 99] Updating channel b918c0a7-d990-4e09-a4cd-aee69cf458ca
    2016-07-12 14:34:12.402 BarkBox[380:70992] [D] -[UAChannelRegistrar registerWithChannelID:channelLocation:withPayload:forcefully:] [Line 58] Ignoring registration request, one already in progress.
    2016-07-12 14:34:12.402 BarkBox[380:70992] [D] -[UAInboxMessageList retrieveMessageListWithSuccessBlock:withFailureBlock:] [Line 118] Retrieving message list.
    2016-07-12 14:34:12.448 BarkBox[380:70992] [I] -[UAPush appRegisteredUserNotificationSettings] [Line 1116] Application did register with user notification types 7.
    2016-07-12 14:34:12.454 BarkBox[380:70992] [I] __56-[UAInboxMessageList refreshInboxWithCompletionHandler:]_block_invoke_2 [Line 379] Inbox messages updated.
    2016-07-12 14:34:12.457 BarkBox[380:70992] [D] __56-[UAInboxMessageList refreshInboxWithCompletionHandler:]_block_invoke_2 [Line 381] Loaded saved messages: (
    ).
    2016-07-12 14:34:12.460 BarkBox[380:70992] Device token: cad33e66d74c0d109cf165499d29b3669956b9d0829f0dcda048f549f4715071
    2016-07-12 14:34:12.460 BarkBox[380:70992] [I] -[UAPush appRegisteredForRemoteNotificationsWithDeviceToken:] [Line 1101] Application registered device token: cad33e66d74c0d109cf165499d29b3669956b9d0829f0dcda048f549f4715071
    2016-07-12 14:34:12.460 BarkBox[380:70992] [D] -[UAAnalytics addEvent:] [Line 248] Adding device_registration event B04D84EB-4917-4142-89BA-6FE29A633747.
    2016-07-12 14:34:12.475 BarkBox[380:70992] [D] -[UAChannelRegistrar registerWithChannelID:channelLocation:withPayload:forcefully:] [Line 58] Ignoring registration request, one already in progress.
    2016-07-12 14:34:12.958 BarkBox[380:70992] [I] -[UAPush registrationSucceededWithPayload:] [Line 1122] Channel registration updated successfully.
    2016-07-12 14:34:13.264 BarkBox[380:70992] [D] __59-[UAInboxAPIClient retrieveMessageListOnSuccess:onFailure:]_block_invoke_3 [Line 172] Setting Last-Modified time to '(null)' for user BIjpomU9Qy6yw4JTjMZEyA's message list.
    2016-07-12 14:34:13.264 BarkBox[380:70992] [D] __75-[UAInboxMessageList retrieveMessageListWithSuccessBlock:withFailureBlock:]_block_invoke71 [Line 156] Refreshing message list.
    2016-07-12 14:34:13.268 BarkBox[380:70992] [I] __56-[UAInboxMessageList refreshInboxWithCompletionHandler:]_block_invoke_2 [Line 379] Inbox messages updated.
    2016-07-12 14:34:13.268 BarkBox[380:70992] [D] __56-[UAInboxMessageList refreshInboxWithCompletionHandler:]_block_invoke_2 [Line 381] Loaded saved messages: (
    ).
    2016-07-12 14:34:14.832 BarkBox[380:70992] [I] __20-[UAUser updateUser]_block_invoke150 [Line 234] Updated user BIjpomU9Qy6yw4JTjMZEyA successfully.
    2016-07-12 14:34:28.743 BarkBox[380:70992] [D] __41-[UAAnalytics uploadOperationWithEvents:]_block_invoke [Line 533] Analytics data sent successfully. Status: 200

     

     

    0
  • Hi Ray,

    I looked in our system to see what could be the cause of the issue.

    It looks like we have throttled and turned off the application due to the huge amount of Rejected Device Tokens we have received from Apple for your app. In order to keep our services running, we have prevented the app from sending push for a set amount of time until that Rejected Device Tokens issue is resolved. (This is an automatic thing that runs on our end, not trying to single you out or anything!)

     

    As of right now, there appears to be an alarming amount of Device Tokens registered to your Development app, which is usually indicative of a problem with the Production build of the app (It may be using the Development Keys).

    I would ensure that the Production build of the app is currently built and deployed with the correct App Key, certs, and Bundle IDs, and delete the Development app and start over with a new App Key for testing. This should get you on the right path moving forward.

    0
  • Thanks! 

     

    That seems to work!

    0
  • No problem, happy to help!

    0

Please sign in to leave a comment.