App - 'The data couldn't be read because it is missing'

[MrMeeb]

Hi all,

Following what I believe was the 2.0.0 update, lots of the functions no longer seem to work. I can login to my SL instance without issue, but when navigating to create an alias, or view account details I get the error 'The data couldn't be read because it is missing'.

I am confident these issues didn't happen prior to this update

No errors in the docker logs, just an entry from sl-app and my nginx proxy when trying:

sl-app         | 2022-10-01 10:35:48,081 - SL - DEBUG - "/code/server.py:444" - after_request() -  - 172.23.0.6 GET /api/user_info ImmutableMultiDict([]) 200
sl-nginx       | [IP Redacted] - - [01/Oct/2022:10:35:48 +0000] "GET /api/user_info HTTP/1.1" 200 109 "-" "SimpleLogin/22102 CFNetwork/1335.0.3 Darwin/21.6.0" "-"

Steps to reproduce:

1. Open SimpleLogin app
2. Select My Account from the bottom row
3. Observe error

Trying to do either action via the web app or Chrome extension still works as expected. This is only limited to the mobile app

iOS Version 2.2.1 (Build 22102)

Tested on SimpleLogin v3.4.0 and 4.6.2-beta

Docker Compose file:

version: '3'

services:

  sl-postfix:
    image: git.mrmeeb.stream/mrmeeb/postfix:latest
    container_name: sl-postfix
    restart: unless-stopped
    networks:
      - simple-login
    depends_on:
      - "sl-db"
    ports:
      - "${SL_IP}:25:25"
    volumes:
      - ${DROOT}/postfix:/config
      - ${DROOT}/nginx/nginx_secrets:/etc/letsencrypt:ro

  sl-db:
    image: postgres:12.1
    container_name: sl-db
    restart: unless-stopped
    networks:
      - simple-login
    volumes:
      - ${DROOT}/db:/var/lib/postgresql/data
    environment:
      - POSTGRES_PASSWORD=${POSTGRES_PW}
      - POSTGRES_USER=simplelogin
      - POSTGRES_DB=simplelogin

  sl-app:
    image: simplelogin/app:${SL_VERSION}
    container_name: sl-app
    restart: unless-stopped
    networks:
      - simple-login
    depends_on:
      - "sl-db"
    volumes:
      - ${DROOT}:/sl
      - ${DROOT}/upload:/code/static/upload
      - ${DROOT}/dkim.key:/dkim.key
      - ${DROOT}/dkim.pub.key:/dkim.pub.key
      - ${DROOT}/simplelogin.env:/code/.env

  sl-email:
    image: simplelogin/app:${SL_VERSION}
    container_name: sl-email
    restart: unless-stopped
    networks:
      - simple-login
    depends_on:
      - "sl-db"
    command: python email_handler.py
    volumes:
      - ${DROOT}:/sl
      - ${DROOT}/upload:/code/static/upload
      - ${DROOT}/dkim.key:/dkim.key
      - ${DROOT}/dkim.pub.key:/dkim.pub.key
      - ${DROOT}/simplelogin.env:/code/.env

  sl-job-runner:
    image: simplelogin/app:${SL_VERSION}
    container_name: sl-job-runner
    restart: unless-stopped
    networks:
      - simple-login
    depends_on:
      - "sl-db"
    command: python job_runner.py
    volumes:
      - ${DROOT}:/sl
      - ${DROOT}/upload:/code/static/upload
      - ${DROOT}/dkim.key:/dkim.key
      - ${DROOT}/dkim.pub.key:/dkim.pub.key
      - ${DROOT}/simplelogin.env:/code/.env

#  sl-migration:
#    image: simplelogin/app:${SL_VERSION}
#    container_name: sl-migration
#    restart: "no"
#    networks:
#      - simple-login
#    depends_on:
#      - "sl-db"
#    command: alembic upgrade head
#    volumes:
#      - ${DROOT}:/sl
#      - ${DROOT}/upload:/code/static/upload
#      - ${DROOT}/dkim.key:/dkim.key
#      - ${DROOT}/dkim.pub.key:/dkim.pub.key
#      - ${DROOT}/simplelogin.env:/code/.env

#  sl-init:
#    image: simplelogin/app:${SL_VERSION}
#    container_name: sl-init
#    restart: "no"
#    networks:
#      - simple-login
#    depends_on:
#      - "sl-db"
#    command: python init_app.py
#    volumes:
#      - ${DROOT}:/sl
#      - ${DROOT}/upload:/code/static/upload
#      - ${DROOT}/dkim.key:/dkim.key
#      - ${DROOT}/dkim.pub.key:/dkim.pub.key
#      - ${DROOT}/simplelogin.env:/code/.env


  sl-nginx:
    image: jonasal/nginx-certbot:latest
    container_name: sl-nginx
    restart: unless-stopped
    networks:
      - simple-login
    depends_on:
      - "sl-app"
    ports:
      - "${SL_IP}:80:80"
      - "${SL_IP}:443:443"
    volumes:
      - ${DROOT}/nginx/nginx_secrets:/etc/letsencrypt
      - ${DROOT}/nginx/user_conf.d:/etc/nginx/user_conf.d:ro
    env_file:
      - ${DROOT}/nginx/nginx-certbot.env

networks:
  simple-login:
    name: simple-login
    driver: bridge
    driver_opts:
      com.docker.network.bridge.enable_ip_masquerade: "false"
    ipam:
      driver: default
      config:
        - subnet: 172.23.0.0/24

[nguyenkims]

@MrMeeb I think the latest iOS version requires using the latest SaaS (not self-hosting version). If you want to use the iOS app with your self-hosted instance, there are 2 solutions:

• upgrade your server to the latest version https://hub.docker.com/layers/simplelogin/app-ci/v4.14.13/images/sha256-5749bb1b923c0cdb40d1fead091720aa43b6e9e9ea88f36edec631ddc0528fdd?context=repo, please note that this version wasn't tested for self hosting yet
• build an old version of the ios app with xcode and run it on your iphone.

[MrMeeb]

That's unfortunate - the CI build is not available for ARM (I'm running SimpleLogin on an OCI ARM instance). Even if it was, running an untested version is not my style.

I appreciate your response, but I am quite disappointed by what it reveals. SimpleLogin provide docs for self-hosting their software, yet an update has not been provided for it officially since April 2021. The CI branch has been regularly updated since then. There's 4.6.2-Beta, but it's already outdated. It hasn't been touched since June, and SL is already on 4.15.2.

This would be less of an issue if self-hosted users weren't also losing the ability to use the companion apps - not only are we missing out on whatever functionality is added in the new versions, we're also losing functionality we had previously. No effort appears to have been made to tell us either.

Privacy-motivated people use tools like these, so the ability to self-host is great. I was very excited when I found this tool and deployed it. I don't really know if I have the confidence to run it anymore. The apparent lack of commitment to actually continuing the support of this feature is a real shame. I really think that if this is the angle, there should be a disclaimer (e.g that web works, but apps do not).

[nguyenkims]

@MrMeeb the release cycle of the web app (which is also the API) is different than the clients (mobile apps and web extension) as they are done by different teams. We try our best to keep the self hosted version up to date but unfortunately releasing a new version currently requires manual testing and that's why the self host version is often quite behind the SaaS version. Our plan is to stablize the SaaS version and release it as self-hosted at the same time it's deployed so there would be no difference between SaaS and self-hosted version.

In the meantime, the workaround is to build the latest version ourself using our Dockerfile. The latest version should be compatible with any existing self-hosted instance as we make sure to document if any breaking change is introduced.

[MrMeeb]

Thanks for further clarification. I'm glad there is a plan going forward. I'll experiment with the CI branch, building myself for ARM. Once I've verified it makes the iOS app function, I'll mark as answered. All the best!

[MrMeeb]

Built on CI branch using Dockerfile from repo. App functionality now restored.