Note that there are some explanatory texts on larger screens.

plurals
  1. POUrban Airship can't receive rich push
    primarykey
    data
    text
    <p>I'm having issues with Urban Airship, specifically for registering users for Rich Push. I have the following code in <code>AppDelegate</code></p> <pre><code>//Create Airship options dictionary and add the required UIApplication launchOptions NSMutableDictionary *takeOffOptions = [NSMutableDictionary dictionary]; [takeOffOptions setValue:launchOptions forKey:UAirshipTakeOffOptionsLaunchOptionsKey]; [UAirship takeOff:takeOffOptions]; [[UAPush shared] resetBadge]; // Register for remote notfications with the UA Library. This call is required. [[UAPush shared] registerForRemoteNotificationTypes:(UIRemoteNotificationTypeBadge | UIRemoteNotificationTypeSound | UIRemoteNotificationTypeAlert)]; - (void)application:(UIApplication *)application didRegisterForRemoteNotificationsWithDeviceToken:(NSData *)deviceToken { // Updates the device token and registers the token with UA. NSString *myAlias = @"Your Alias"; [UAPush shared].alias = myAlias; [[UAPush shared] registerDeviceToken:deviceToken]; } </code></pre> <p>This allows my code to register the device under Device Tokens, as well as auto-generate a user for Rich Push. However, the alias and device token are not passed into the Rich Push user, which I suspect is not allowing UA to send a rich push down to my device.</p> <p>What am I missing? I looked through the docs for iOS push and have all the same code. Any help would be appreciated!</p> <p>Update:</p> <p>So I've created a user hitting the <code>/api/user API</code> endpoint and brute-forcing the alias/device_token. However, my device is still not getting the rich push. I went to <code>/api/user/user_id</code> and verified that badge > 0, so Urban Airship is attempting to send these rich push. Anyone know why it's getting lost?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload