404 Api request about engage-digital-messaging-android HOT 7 CLOSED

Hello,

This error "Unknown API key", if random, probably means that the chat wasn't properly initialized a thus tried to query the server without an API key. You need to make sure the SDK is initialized with the proper API key whenever the app resumes from a notification (see https://github.com/dimelo/Dimelo-Android#push-notifications)

As it's random, how frequently do you have this problem? do you have steps to reproduce it? or at least stats in which the problem seems to be more frequent to you?

from engage-digital-messaging-android.

Hello,

Thank you for your answer.
The SDK is correcty initialized because I receive notifications. But in few cases, the new notification unload history.
I can't get you a frequency or steps to reproduce it, because it's very random :).

Thanks.

from engage-digital-messaging-android.

Ok thanks, yes I guess the chat is properly initialized when you start the app, but I was thinking more about what happen when the app is closed and the notification tapped, because it's not necessarily the same code path and it's frequent for users to miss this case.

The fact that it unloads history is coherent with the error you showed earlier, if there's no API key the chat won't be able to load the history and will display a blank screen. Can you confirm that if you kill the app and tap the notification, it works most of the time?

from engage-digital-messaging-android.

Thanks,
But I can't reproduce bug systematically, so I can't confirm you if I kill app, notifications works fine.

from engage-digital-messaging-android.

Yes sure, I just wanted you to confirm that if you kill the app it works "most of the time", because if it works at least some times it probably means you're setting the API key properly in this code path.

from engage-digital-messaging-android.

Yes, if I killed the application and if I receive a new notification, it works "most of time".
I think the API key is set properly, because I can receive some notifications without problem.

from engage-digital-messaging-android.

As seen with @DrissTM, the 404 was caused by a call to setUserIdentifier after setJwt, which actually clears the JWT (to avoid any conflict). We added a note to the readme about that: 198ba87

from engage-digital-messaging-android.