Adding support for non-hilt Applications

[mrajatttt]

Issue Number:

Description:

What are the changes? Why are we making them?

• Adding support for non-hilt applications, A customer pointed out that their application does not use hilt and our SDK was forcing them to include hilt/dagger dependencies.

---

Functional backward compatibility:

Does this change introduce backwards incompatible changes? [YES/NO]

NO

Does this change introduce any new dependency? [YES/NO]

NO

---

Testing:

Is the code unit tested?
YES
Have you tested the changes with a sample UI (e.g. Android Mobile Chat Example)?
YES
List manual testing steps:

• Add Steps below:

Here are a list of manual test cases to run through:

• Initiating chat and connecting with an agent
• Retrieving transcript
• Disconnecting from chat
• Sending a message to the agent
  • See typing bubbles on agent side
  • See read/delivered receipt on client side
  • Receiving a message from the agent
  • See typing bubbles on client side
  • See read/delivered receipt on agent side
  • Sending an attachment to the agent (try .txt, .pdf, .jpg)
  • Preview the attachment on click
  • Receiving an attachment from the agent
  • Preview the attachment on click
• Close the application (Without ending chat) → open app again → Start chat → Should Retrieve transcript from a previous chat session

[mliao95]

Does this change introduce backwards incompatible changes? [YES/NO]

YES

What backwards incompatible changes are we introducing here? If anything aren't we generalizing support for projects with/without hilt dependency?

[mrajatttt]

Does this change introduce backwards incompatible changes? [YES/NO]
YES

What backwards incompatible changes are we introducing here? If anything aren't we generalizing support for projects with/without hilt dependency?

My bad, I thought it was support backward changes!