I see device opens but no device tokens

I used UA successfully last year. So I decided to delete the app and generate a new one with new secret keys.I embedded those in the plist file however when I publish the app using my MDM, I can't register any device tokens when users open the app. It's odd because the dashboard show the app opens so it is communicating. Nothing is recorded in the error console. Any ideas?

All of my certs are active and only have a production version.

Thanks in advance.

Didn't find what you were looking for?

New post

Comments

5 comments

  • Hi Josh, If you're not getting APNS device tokens, it is likely that your iOS/APNS provisioning is not set up correctly. If you're seeing app opens, our SDK is speaking with Urban Airship correctly but the device token is provided by Apple.

    Please take a pass through our APNS setup documentation here:

    http://docs.urbanairship.com/reference/push-providers/apns.html#ios-apns-setup

    0
  • Thanks for your response.

    I followed the steps exactly and still can't get it to work.

    How can I troubleshoot the APNS or at least see where the tokens fail?

    0
  • Here is the error code from my Mac Console:

    [E] void UAApplicationDidFailToRegisterForRemoteNotificationsWithError(__strong id, SEL, UIApplication *__strong, NSError *__strong) [Line 170] Application failed to register for remote notifications with error: Error Domain=NSCocoaErrorDomain Code=3000 "no valid 'aps-environment' entitlement string found for application" UserInfo={NSLocalizedDescription=no valid 'aps-environment' entitlement string found for application}

    0
  • This is an APNS provisioning error rather than something specific to Urban Airship. The key here is the "no valid 'aps-environment" error. This support center article and the information linked from it should be of some help.

    https://support.urbanairship.com/hc/en-us/articles/213492323-Unable-to-register-a-device-token-no-valid-aps-environment-entitlement-error

    Thanks! 

    0
  • After 2 days of trying to solve this it turns out that Push Notifications had to be turned on in the capabilities area in XCode. This must have been added in the newest version of XCode because this same build worked last year. Thanks for your help!

    0

Please sign in to leave a comment.