Does the new command 2 binary format work with Apple Push Notification Service? I receive an invalid response status code of 128.

Question

Does the new command 2 binary format work with Apple Push Notification Service? I am sending 2 messages with the same payload to 2 different devices. None of the messages display on either of the devices. It seems that at least 3 should have been displayed. For my first device, I received a response with an invalid status code of 128 and the message identifier is 2 indicating that the first message was OK. However no message was displayed on the phone. For the second device, I did not receive any error response, but no message was displayed on the device.
Does ANS perform any validation on the message identifier? The Local and Push Notification Programmin Guide says the message identifier is:
An arbitrary, opaque value that identifies this notification. This identifier is used for reporting errors to your server.
I know that the device tokens are valid because the same tokens work when I use the legacy basic or enhanced formats. The phones display the messages correctly when I send to ANS using the old ANS message format.
Here is the data and the response:
Sent to ANS: 2 0 0 0 158 1 0 32 120 107 166 143 171 157 143 169 70 135 12 135 246 142 64 224 244 44 116 4 154 65 115 192 206 28 189 56 174 0 172 16 2 0 23 123 34 97 112 115 34 58 123 34 97 108 101 114 116 34 58 34 65 66 67 34 125 125 3 0 4 0 0 0 2 4 0 4 83 7 119 141 5 0 1 5 1 0 32 120 107 166 143 171 157 143 169 70 135 12 135 246 142 64 224 244 44 116 4 154 65 115 192 206 28 189 56 174 0 172 16 2 0 23 123 34 97 112 115 34 58 123 34 97 108 101 114 116 34 58 34 65 66 67 34 125 125 3 0 4 0 0 0 3 4 0 4 83 7 119 141 5 0 1 5
ANS returned an error: 8 128 0 0 0 2
Sent to ANS: 2 0 0 0 158 1 0 32 4 239 182 26 13 237 170 136 41 243 181 57 120 208 135 19 101 102 212 70 55 244 251 255 160 125 82 9 10 143 72 17 2 0 23 123 34 97 112 115 34 58 123 34 97 108 101 114 116 34 58 34 65 66 67 34 125 125 3 0 4 0 0 0 5 4 0 4 83 7 119 147 5 0 1 5 1 0 32 4 239 182 26 13 237 170 136 41 243 181 57 120 208 135 19 101 102 212 70 55 244 251 255 160 125 82 9 10 143 72 17 2 0 23 123 34 97 112 115 34 58 123 34 97 108 101 114 116 34 58 34 65 66 67 34 125 125 3 0 4 0 0 0 6 4 0 4 83 7 119 147 5 0 1 5
ANS did not return a response.

Answer 1

Hello, can you please help me ?
You specified sample payload here:
TerrellFromLockhart wrote:
I finally got this to work. The picture in the Programming Guide is very confusing. The solution was to prefix every message's frame data with command 2 and that messsage's frame data length. Here is a sample:
ANS frame: 2 0 0 0 77 1 0 32 120 107 166 143 171 157 143 169 70 135 12 135 246 142 64 224 244 44 116 4 154 65 115 192 206 28 189 56 174 0 172 16 2 0 21 123 34 97 112 115 34 58 123 34 97 108 101 114 116 34 58 34 63 34 125 125 3 0 4 0 0 0 2 4 0 4 83 7 199 195 5 0 1 10 2 0 0 0 77 1 0 32 120 107 166 143 171 157 143 169 70 135 12 135 246 142 64 224 244 44 116 4 154 65 115 192 206 28 189 56 174 0 172 16 2 0 21 123 34 97 112 115 34 58 123 34 97 108 101 114 116 34 58 34 63 34 125 125 3 0 4 0 0 0 3 4 0 4 83 7 199 195 5 0 1 10 2 0 0 0 77 1 0 32 120 107 166 143 171 157 143 169 70 135 12 135 246 142 64 224 244 44 116 4 154 65 115 192 206 28 189 56 174 0 172 16 2 0 21 123 34 97 112 115 34 58 123 34 97 108 101 114 116 34 58 34 63 34 125 125 3 0 4 0 0 0 4 4 0 4 83 7 199 195 5 0 1 10
About to read response at Thu Feb 20 15:40:20 CST 2014
SocketTimeoutException
2 - is clearly command
0 0 0 77 - frame length
1 - item Id
what's 0 32 ? According to this page https://developer.apple.com/library/ios/documentation/NetworkingInternet/Concept ual/RemoteNotificationsPG/Chapters/Commu…
Item id  should be followed by item length. But item length is obviously greater than 32 because device token's length is 32. Can you please explain why 0 32 were used? and do you have any insight on item id meaning ?