ADM - Unable to enqueue message for dispatch

Question

question

konrad_g1 asked · Dec 03, 2018 at 12:04 PM

ADM - Unable to enqueue message for dispatch

Hi, I'm having an issue with ADM integration. Retrieving the registration ID works fine, the problem appears later when triggering an actual notification. Testing on a Kindle Fire. Here's an interesting bit from logcat (parts in curly braces replaced by me):

I/ADM: [ADM][TCommPush]Skipping message crc check since it was not provided. id = {msg_id_1}
I/ADM: [ADM][TCommPush]Received message: account = amzn1.account.{acc_id_1},  id = ABCDE, topic = {topic_1}, payload size = 2357 bytes
I/ADM: [ADM][TCommPush]Unable to enqueue message {msg_id_1} for dispatch. User not found for account amzn1.account.{acc_id_1}.

There is a user logged in on the device, another app using the same backend manages to dispatch the message correctly:

I/ADM: [ADM][TCommPush]Skipping message crc check since it was not provided. id = {msg_id_2}
I/ADM: [ADM][TCommPush]Received message: account = amzn1.account.{acc_id_2},  id = {msg_id_2}, topic = {topic_2}, payload size = 1170 bytes
I/ADM: [ADM][TCommPush]Enqueueing message {msg_id_2} for dispatch to current user
I/ADM: [ADM][Dispatch]Dispatching 1 messages.
I/ADM: [ADM][Dispatch][1 of 1]Dispatching message {msg_id_2}, topic: {topic_2}, payload: 1170 bytes via class com.amazon.device.messaging.V2Dispatcher
I/ADM: [ADM][Dispatch][1 of 1]Dispatched ADM message. ID: {msg_id_2} Package: {package} # Extras: 6

Does it matter that {acc_id_1} is different from {acc_id_2}?

amazon device messaging app

0

10 |2000 characters needed characters left characters exceeded

Attachments: Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

2 Answers

Answer 1 · 2018-12-06T08:20:45Z

konrad_g1 answered · Dec 06, 2018 at 08:20 AM

An update here. Turns out changing the SNS app helped (the project uses multiple SNS apps, different ones for APNS and GCM, various environments etc.) No idea how the SNS app and Amazon user on the device are related, but it now works.

0 · Share

10 |2000 characters needed characters left characters exceeded

Attachments: Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

Answer 2 · 2018-12-03T19:03:11Z

Levon@Amazon answered · Dec 03, 2018 at 07:03 PM

Hi konrad_g1,

In the first case -

I/ADM: [ADM][TCommPush]Skipping message crc check since it was not provided. id = {msg_id_1}
I/ADM: [ADM][TCommPush]Received message: account = amzn1.account.{acc_id_1}, id = ABCDE, topic = {topic_1}, payload size = 2357 bytes
I/ADM: [ADM][TCommPush]Unable to enqueue message {msg_id_1} for dispatch. User not found for account amzn1.account.{acc_id_1}.

What this means -> The account acc_id_1 is not on the Fire tablet.

In the second case -

I/ADM: [ADM][TCommPush]Skipping message crc check since it was not provided. id = {msg_id_2}
I/ADM: [ADM][TCommPush]Received message: account = amzn1.account.{acc_id_2}, id = {msg_id_2}, topic = {topic_2}, payload size = 1170 bytes
I/ADM: [ADM][TCommPush]Enqueueing message {msg_id_2} for dispatch to current userI/ADM: [ADM][Dispatch]Dispatching 1 messages.
I/ADM: [ADM][Dispatch][1 of 1]Dispatching message {msg_id_2}, topic: {topic_2}, payload: 1170 bytes via class com.amazon.device.messaging.V2Dispatcher
I/ADM: [ADM][Dispatch][1 of 1]Dispatched ADM message. ID: {msg_id_2}

The active account and the targeted account are the same and hence message is dispatched to the current user.

We took a look at the code and it looks like the device does not support multiple profiles. The log line "Unable to enqueue message %s for dispatch. User not found for account %s." is generated only when multiUserEnabled is set to false.

Could you please answer these questions so we could understand the context better:

1. What device is being used for the test?

2. What is the software version? You can get this by going to Settings -> Device Options -> System Updates -> Click on the "FireOS vNext" to get the FireOS build info.

3. What is the version of ADM? You can get this by going to Settings -> Apps & Games -> Manage all applications -> scroll to tab "All" -> Scroll down to "Amazon Device Messaging (ADM)" -> check the version

4. Is the device registered with multiple Amazon accounts?

5. If the answer to 4) is yes, can you verify that the account id to which the message was NOT enqueued is the same as the active account? Let us know if it is for secondary user when primary is active or vice versa.

0 · Show 1 · Share

10 |2000 characters needed characters left characters exceeded

Attachments: Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

konrad_g1 · Dec 04, 2018 at 10:50 AM

Hi Levon and thanks for the quick response, please find the answers below:

1. What device is being used for the test? Kindle Fire (5th Generation)

2. What is the software version? Fire OS 5.3.6.4 (626533320)

3. What is the version of ADM? 6.2.180_2188510

4. Is the device registered with multiple Amazon accounts? No

The last bit is the most interesting IMO - there's only one Amazon user logged in, yet the messages are apparently targeted to another one. How could this be possible?

0 · Share ·

ADM - Unable to enqueue message for dispatch

question details

Related Questions