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}?