Forum Post: RE: OpenEdge.Mobile.PushNotificationService

  • Thread starter Thread starter rblanchard
  • Start date Start date
Status
Not open for further replies.
R

rblanchard

Guest
Peter, You look to be correct for the X-Progress-App-Id. If I compare that value from the notification database to that of the mobile app guid it matches. DeviceId - what API is that. I have access to the device.uuid but that is not what is being sent. Is there documentation for this API? Add fields to the database. That is cool so I can add whatever I want so I can filter by this. As far as registration I was referring to more on the mobile app side so when the app initializes we would send deviceid, token, etc. and register the device in the notification database. I then would be able to sen push notifications and use any of those values to filter. I have been toying with filter using the ABL classes. The sample from the docs works great. ASSIGN oPayload = PushNotificationMessageBuilder :Send(cMessage, iBadgeCount) :IncludeDevice(cDeviceId[1]) :IncludeDevice(cDeviceId[2]) :IncludeDevice(cDeviceId[3]) :Payload. This crashes the ABL; ASSIGN oPayload = PushNotificationMessageBuilder :Send(cMessage, iBadgeCount) :AddStringFilter ("token", "7b2a2ee7a59ba5c2d452b204ff2d391e5f4936f204dc6d93ce5e998b009fa9e4", OpenEdge.Mobile.PushNotificationFilterOperandEnum:Equals ) :Payload . I have a call open with PTS.

Continue reading...
 
Status
Not open for further replies.
Back
Top