[Question] How is setupAPN() supposed to get the deviceToken?

I see that the library includes setupAPN(deviceToken). How is the deviceToken supposed to find its way into the JS environment?

It’s not an issue because you can just add [Intercom setDeviceToken:deviceToken]; but wanted to know if there was an alternative way or if it’s there for API parity.

[jplethier]

@ryankask I am using this flow too after the login, but before the login I have a UnidentifiedUser registered, and after login, seems that intercom is not setting the push token for the logged user.

This flows worked nicely for you?

[javiercr]

I think @rogchap is right. If you use react-native-push-notification (based in PushNotificationIOS) to register for remote notifications, and later use the resulting token to call setupAPN, you will probably run into problems as the encoding from String to NSData doesn’t seem to match the encoding on PushNotificationIOS:

+ (void)didRegisterForRemoteNotificationsWithDeviceToken:(NSData *)deviceToken
{
  NSMutableString *hexString = [NSMutableString string];
  NSUInteger deviceTokenLength = deviceToken.length;
  const unsigned char *bytes = deviceToken.bytes;
  for (NSUInteger i = 0; i < deviceTokenLength; i++) {
    [hexString appendFormat:@"%02x", bytes[i]];
  }
  [[NSNotificationCenter defaultCenter] postNotificationName:RCTRemoteNotificationsRegistered
                                                      object:self
                                                    userInfo:@{@"deviceToken" : [hexString copy]}];
}

As @rogchap suggested, if you call [Intercom setDeviceToken:deviceToken] directly from didRegisterForRemoteNotificationsWithDeviceToken it seems to work because it avoids the encoding problem. However this solution is not ideal, as in our case we would prefer to set the token (call setupAPN after the user logs in), while keeping the registration for the token handed by PushNotificationIOS (before the login).