[GH-ISSUE #80] [BUG] Decoding error when using Setup mode #44

New Issue

2026-02-17T17:11:55-05:00

yindo commented

2026-02-17 17:11:55 -05:00

Originally created by @nikolan123 on GitHub (Jul 29, 2025).
Original GitHub issue: https://github.com/Drop-OSS/drop-app/issues/80

Describe the bug
I get a decoding error when trying to install a game if Setup mode is on. This happens with both of the games in my library.

The error message is error decoding response body: invalid type: null, expected a string at line 1 column 153
There is nothing about it in app's logs using DEBUG level logging or in the server logs.

To Reproduce
Steps to reproduce the behavior:

Import a game from the admin panel leaving metadata stuff as default
Import a version using Setup mode
Go to library in the app and click on install
See error

Expected behavior
The version should be listed and download as normal.

Screenshots

Desktop

OS: Windows 11 24H2
App Version 0.2.1-beta
Server: 0.2.0-beta running in Docker

Originally created by @nikolan123 on GitHub (Jul 29, 2025). Original GitHub issue: https://github.com/Drop-OSS/drop-app/issues/80 **Describe the bug** I get a decoding error when trying to install a game if Setup mode is on. This happens with both of the games in my library. The error message is `error decoding response body: invalid type: null, expected a string at line 1 column 153` There is nothing about it in app's logs using DEBUG level logging or in the server logs. **To Reproduce** Steps to reproduce the behavior: 1. Import a game from the admin panel leaving metadata stuff as default 2. Import a version using Setup mode 3. Go to library in the app and click on install 4. See error **Expected behavior** The version should be listed and download as normal. **Screenshots** <img width="535" height="405" alt="Image" src="https://github.com/user-attachments/assets/23de5cc2-4e54-4748-91a5-af8a32e800e7" /> **Desktop** - OS: Windows 11 24H2 - App Version 0.2.1-beta - Server: 0.2.0-beta running in Docker

yindo closed this issue

2026-02-17 17:11:55 -05:00

yindo commented

2026-02-17 17:11:55 -05:00

@DecDuck commented on GitHub (Jul 29, 2025):

I couldn't reproduce it, could you provide instructions on how you set it up, and see if you can reproduce the issue with a different game?

@DecDuck commented on GitHub (Jul 29, 2025): I couldn't reproduce it, could you provide instructions on how you set it up, and see if you can reproduce the issue with a different game? <img width="910" height="755" alt="Image" src="https://github.com/user-attachments/assets/6c3d3d5d-97ff-4fb3-af05-83190212604a" />

yindo commented

2026-02-17 17:11:55 -05:00

@nikolan123 commented on GitHub (Jul 29, 2025):

It happens with both games in my library, the app installation is fresh.
This is how I imported the version:
and here's my docker compose:

version: '3.8'

services:
  postgres:
    container_name: drop-postgres
    image: postgres:14-alpine
    healthcheck:
      test: pg_isready -d ${POSTGRES_DB} -U ${POSTGRES_USER}
      interval: 30s
      timeout: 60s
      retries: 5
      start_period: 10s
    volumes:
      - /srv/dev-disk-by-uuid-x/car/omvdocker/appdata/droposs/db:/var/lib/postgresql/data
    environment:
      - POSTGRES_PASSWORD=${POSTGRES_PASSWORD}
      - POSTGRES_USER=${POSTGRES_USER}
      - POSTGRES_DB=${POSTGRES_DB}

  drop:
    image: decduck/drop-oss:v0.2.0-beta
    depends_on:
      postgres:
        condition: service_healthy
    ports:
      - 3007:3000
    volumes:
      - /srv/dev-disk-by-uuid-x/car/omvdocker/appdata/droposs/library:/library
      - /srv/dev-disk-by-uuid-x/car/omvdocker/appdata/droposs/certs:/certs
      - /srv/dev-disk-by-uuid-x/car/omvdocker/appdata/droposs/objects:/objects
    environment:
      - DATABASE_URL=postgres://${POSTGRES_USER}:${POSTGRES_PASSWORD}@postgres:5432/${POSTGRES_DB}
      - FS_BACKEND_PATH=/objects
      - CLIENT_CERTIFICATES=/certs
      - LIBRARY=/library
      - GIANT_BOMB_API_KEY=${GIANT_BOMB_API_KEY}

@nikolan123 commented on GitHub (Jul 29, 2025): It happens with both games in my library, the app installation is fresh. This is how I imported the version: <img width="706" height="811" alt="Image" src="https://github.com/user-attachments/assets/ac521724-cd6e-48a7-acd5-e4606fc4a39e" /> and here's my docker compose: ``` version: '3.8' services: postgres: container_name: drop-postgres image: postgres:14-alpine healthcheck: test: pg_isready -d ${POSTGRES_DB} -U ${POSTGRES_USER} interval: 30s timeout: 60s retries: 5 start_period: 10s volumes: - /srv/dev-disk-by-uuid-x/car/omvdocker/appdata/droposs/db:/var/lib/postgresql/data environment: - POSTGRES_PASSWORD=${POSTGRES_PASSWORD} - POSTGRES_USER=${POSTGRES_USER} - POSTGRES_DB=${POSTGRES_DB} drop: image: decduck/drop-oss:v0.2.0-beta depends_on: postgres: condition: service_healthy ports: - 3007:3000 volumes: - /srv/dev-disk-by-uuid-x/car/omvdocker/appdata/droposs/library:/library - /srv/dev-disk-by-uuid-x/car/omvdocker/appdata/droposs/certs:/certs - /srv/dev-disk-by-uuid-x/car/omvdocker/appdata/droposs/objects:/objects environment: - DATABASE_URL=postgres://${POSTGRES_USER}:${POSTGRES_PASSWORD}@postgres:5432/${POSTGRES_DB} - FS_BACKEND_PATH=/objects - CLIENT_CERTIFICATES=/certs - LIBRARY=/library - GIANT_BOMB_API_KEY=${GIANT_BOMB_API_KEY} ```

yindo commented

2026-02-17 17:11:55 -05:00

@DecDuck commented on GitHub (Jul 29, 2025):

Oh this issue may have been fixed already, I just realised you're on v0.2.0. I'll see if it's present on v0.2.0, but you're welcome to upgrade to nightly or wait until v0.3.0.

@DecDuck commented on GitHub (Jul 29, 2025): Oh this issue may have been fixed already, I just realised you're on v0.2.0. I'll see if it's present on v0.2.0, but you're welcome to upgrade to nightly or wait until v0.3.0.

yindo commented

2026-02-17 17:11:55 -05:00