I am new to Android App development and Kotlin. My wife and I had recently created a project using Android Studio. Messaging capability is needed for the android application we are developing. I was checking out Trixnity for this reason.

I added three Trixnity Client trixnity-client-* artifacts all having version 4.13.2 to our project after which the project was broken. Later I managed to get the project in good condition with the help of documentations online.

Below were the issues I observed while fixing our project setup.

1. There was a version conflict in the artifacts of Room Database our project depended on. The project directly depended on a specific version of artifacts for Room Database. Trixnity Client Repository Room internally depended on a different version of Room Database artifacts.

2. Kotlin Gradle Plugin (KGP) 2.1.0 was required for our project to work after I added the three Trixnity Client artifacts of version 4.13.2. But our project was configured to use KGP 1.9.0.

3. Our project was configured with Gradle 8.2 and Android Gradle Plugin (AGP) 8.2.1. The version of KGP - 1.9.0 - configured in our project was not compatible with aforementioned Gradle and AGP version according to their officially published compatibility matrix.

4. Room Database artifacts required KSP instead of KAPT for annotation processing after I upgraded those artifacts for solving issue #1.

5. Gradle configuration attribute to specify Kotlin Compiler Extension Version became obsolete after I upgraded to KGP version 2.1.0 for solving problem #2 and #3. Official documentation said the Kotlin Compose Plugin had to be applied instead of following the obsolete approach.

6. Trixnity Client required Ktor engine at runtime. I hadn’t added Ktor engine in our project setup after adding Trixnity Client artifacts.

7. My attempts to resolve above issues seemingly created inconsistencies in the app installation on my android device used for running the app during development. The app run process from Android Studio was getting stuck with a loading indicator.

Our project got into working condition after fixing above series of issues. Below were the actions I took for fixing our project setup.

1. Upgraded version of Room Database artifacts defined in our project to match the version of the same artifacts internally used by Trixnity Client Repository Room.

2. Upgraded KGP to version 2.1.0 as it was required. Upgraded AGP to version 8.2.2 as it was suggested by Android Studio. Verified that the versions specified for Gradle, AGP and KGP in oir project are compatible according to their compatibility matrix.

3. Migrated to KSP instead of KAPT for annotation processing.

4. Applied Kotlin Compose Plugin version 2.1.0

5. Added Ktor Client OkHttp version 3.1.1. This version of Ktor was chosen because it was the latest version available.

6. Manually uninstalled the broken app installation from my android device used for running the app during development.

Our project was working fine after making above changes and Trixnity Client became usable. I tested the project setup using my Matrix account on matrix.org public Matrix server. I was able to login to my account programmatically by making use of MatrixClient offered by Trixnity. I was able to pull messages from a Matrix Room to my application’s database and see it in Android Studio’s database inspector.

Snippets from my project setup is attached in the next section of this article. Please keep in mind that the specific actions I took to fix my project setup might not be right for other project setups. My suggestion is to refer official documentation to identify and fix project configuration problems if you are facing any. Links to online sources that helped me to fix my project setup are provided at the end of this article.

Thank you for reading.

Snippets from my Project Setup

The three Trixnity Client dependencies which I added to module level build.gradle.kts

dependencies {
    implementation("net.folivo:trixnity-client:4.13.2")
    implementation("net.folivo:trixnity-client-media-okio:4.13.2")
    implementation("net.folivo:trixnity-client-repository-room:4.13.2")
    ...

AGP and KGP versions defined in project level build.gradle.kts

plugins {
    id("com.android.application") version "8.2.2" apply false
    id("org.jetbrains.kotlin.android") version "2.1.0" apply false
}

Gradle and AGP version selected in Android Studio Project Structure

KSP Plugin specified in module level build.gradle.kts .

plugins {
    id("com.google.devtools.ksp") version "2.1.0-1.0.29"
    ...

Kotlin Compose Plugin specified in module level build.gradle.kts

plugins {    
    id("org.jetbrains.kotlin.plugin.compose") version "2.1.0"
    ...

Ktor Client OkHttp specified in module level build.gradle.kts

dependencies {
    implementation("io.ktor:ktor-client-okhttp:3.1.1")
    ...

Links to Online Sources which were Helpful

• https://kotlinlang.org/docs/gradle-configure-project.html#apply-the-plugin - has information regarding gradle project configuration and KGP - AGP - Gradle compatibility matrix.

• https://docs.gradle.org/current/userguide/viewing_debugging_dependencies.html - has information about inspecting dependency tree in gradle.

• https://kotlinlang.org/docs/ksp-quickstart.html#add-a-processor - has information about using KSP annotation processor.

• https://developer.android.com/jetpack/androidx/releases/compose-kotlin - has information about Compose to Kotlin compatibility.

• https://ktor.io/docs/client-engines.html - has information about setting up Ktor OkHttp Client Engine.

• https://trixnity.gitlab.io/trixnity/docs/start - has information about Trixnity.

services:
  zookeeper:
    image: confluentinc/cp-zookeeper:7.6.1
    container_name: zookeeper
    ports:
      - "2181:2181"
    environment:
      ZOOKEEPER_CLIENT_PORT: 2181
    networks:
      - app-network

  kafka:
    image: confluentinc/cp-kafka:7.6.1
    container_name: kafka
    ports:
      - "9092:9092"
    environment:
      KAFKA_LISTENER_SECURITY_PROTOCOL_MAP: INTERNAL:PLAINTEXT,EXTERNAL:PLAINTEXT
      KAFKA_INTER_BROKER_LISTENER_NAME: INTERNAL
      KAFKA_LISTENERS: INTERNAL://kafka:29092,EXTERNAL://kafka:9092
      KAFKA_ADVERTISED_LISTENERS: INTERNAL://kafka:29092,EXTERNAL://localhost:9092
      KAFKA_ZOOKEEPER_CONNECT: zookeeper:2181
      KAFKA_OFFSETS_TOPIC_REPLICATION_FACTOR: 1
    depends_on:
      - zookeeper
    networks:
      - app-network

networks:
  app-network:
    name: app-network
    driver: bridge

List networks managed by docker engine. Ensure that the network you have defined is listed.

C:\some\path>podman network ls
NETWORK ID    NAME                              DRIVER
ba0ccfa0295b  app-network                       bridge

Define another compose file for kafka-ui. Specify the network you have defined earlier as an external network here and join kafka-ui service with it. Run this compose file to start Provectus' Kafka Management Web Interface.

services:
  kafka-ui:
    container_name: kafka-ui
    image: provectuslabs/kafka-ui:v0.7.2
    ports:
      - 8080:8080
    environment:
      DYNAMIC_CONFIG_ENABLED: 'true'
      KAFKA_CLUSTERS_0_NAME: local
      KAFKA_CLUSTERS_0_BOOTSTRAPSERVERS: kafka:29092
    networks:
      - app-network

networks:
    app-network:
        name: app-network
        external: true

Done!

Kafka listener will be accessible on host machine at localhost:9092 and this address must be used as bootstrap server(s) for your application running in host machine. Web interface to manage kafka will be accessible from web browser at localhost:8080 .

Footnotes

At the time of writing this article, I have used Compose V2 specification to define compose files and Podman v5.0.1 to run compose files. A desktop running Windows 11 was used as host machine.

References

• https://www.confluent.io/blog/kafka-listeners-explained/

• Networks top-level elements | Docker Docs