cancel
Showing results for 
Search instead for 
Did you mean: 

"value": "Unknown push target type" while sending PUSH Notification from REST client

Former Member
0 Kudos

Hi experts,

We configured appid in SMP3 SP07. Configured Kapsel PUSH plugin and followed exactly the steps in

When we sent PUSH notification from REST client we received :

{

    "status": {

        "value": "OK",

        "code": 0

    },

    "results": [

        {

            "status": {

                "value": "Unknown push target type",

                "code": 2

            },

            "registrationId": "74ad6f0c-b10c-4a34-825e-a82ac04dac17"

        }

    ]

}

May we know what Unknown push target type and code:2 means?

Best Regards,

Affaan

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Issue solved. Device was not registered properly. We unregistered and then registered the device and received the notification on device.

Best Regards,

Affaan

agentry_src
Active Contributor
0 Kudos

Discussion successfully moved from SAP for Mobile to SMP Developer Center as the more appropriate venue for this topic.

Please mark this Discussion with a Correct Answer (closes, but does not lock the Discussion) and Helpful Answer where appropriate. See http://scn.sap.com/community/support/blog/2013/04/03/how-to-close-a-discussion-and-why   Even if you discovered the solution without any outside contributions, it helps others to understand what the solution turned out to be.

Regards, Mike (Moderator)

SAP Technology RIG

Former Member
0 Kudos

Hi Mohammed,

Can you explain what you changed to reach successfully send your push?

Because I currently have the same error as you.

My device appears correctly recorded on SMP with a Registration ID, an application ID, a Device Type, a User Name and Registration Time valid.

But I have still "Unknow push target type" when I try to send a push with a rest client.

FYI, I use a SAML registration, and I use this lines to use my Device Token in didRegisterForRemoteNotificationsWithDeviceToken method :

    NSString *devToken=[[NSString alloc]initWithData:deviceToken encoding:NSUTF8StringEncoding];

   

    NSError* error = nil;

    SMPClientConnection * clientConnec = [SMPClientConnection initializeWithAppID:@"appId" domain:@"default" secConfiguration:@"Notification (Cannot be deleted)"];

    SMPAppSettings* appSettings = [SMPAppSettings initializeWithConnection:clientConnec userName:@"notificationUser" password:@"passwordForNotif"];

    NSDictionary *props = [NSMutableDictionary dictionary];

    [props setValue:deviceToken forKey:@"d:ApnsDeviceToken"];

    [appSettings setConfigProperty:props error:&error];

    if (error) {

        NSLog(@"ERROR:  %@",error);

    }


Best Regards.

Former Member
0 Kudos

You are using Native way of registering device. In our case, we were facing this issue with Kapsel PUSH plugins and as soon as device was registered successfully it received notification. I am not sure what could be reason in your case.

However, make sure that device token is not expired or has become invalid. I would like to invite others in providing you their feedback in terms of how this works in case of native app.

Regards,

Answers (1)

Answers (1)

Former Member
0 Kudos

Make sure you save the APNS.p12 certificate to "application->push", then re-register the device with SMP3.0 should work fine.

Regards

Choong