We are having difficulties reaching our devices via a county alias. The implementation is an existing Urban Airship app that that will be addressed in a new way. We are attempting to contact a group of devices by the fips_6-4 alias and feeding it in a 5 digit code. The format of the request is:
{ "audience": { "or": [ { "location": { "fips_6-4": "<5 digit county code>", "date": { "recent": { "hours": 24 } } } }, { "location": { "fips_6-4": "<5 digit county code>", "date": { "recent": { "hours": 24 } } } } ] }, "notification": { "alert": "blah blah blah message." }, "device_types": [ "ios", "android" ] }
To which I am getting back
{"ok":true,"operation_id":"fed235d8-a58f-459c-8644-b356c627dea2","push_ids":["fb4ae1aa-3d5e-4de7-a1e7-9ae22312c173"],"message_ids":[],"content_urls":[]}
Note that there are no messages in the ids array.
Our client library is using v 6.2, and is proven to receive singly targeted messages. As an added control I attempted to send a segment targeted message from the portal, which also did not send to the device. At this point it is unclear what is not correctly configured. My guess is something on the client end
My questions are:
Is there a version dependence for these types of location message?
Is our account enabled to send these location targeted messages(does it matter)?
Is there any additional client initialization needed to target them(what specifically is needed)?
Is my format above correct for the request to reach the entire county?
Thanks in advance.
Comments
4 comments