1.3.8 yes
Okay were you able to run migration successfully?
yes
how did you install/upgrade?
As usual
Is this a serious problem?
how exactly?
from 1.3.8 to 1.4.1
You installed using the install command like:
docker run -it --rm \
--volume /var/run/docker.sock:/var/run/docker.sock \
--volume "$(pwd)"/appwrite:/usr/src/code/appwrite:rw \
--entrypoint="install" \
appwrite/appwrite:1.3.8
and upgraded using the upgrade command like:
docker run -it --rm \
--volume /var/run/docker.sock:/var/run/docker.sock \
--volume "$(pwd)"/appwrite:/usr/src/code/appwrite:rw \
--entrypoint="upgrade" \
appwrite/appwrite:1.4.1
?
yes yes
weird...i haven't seen these type of errors yet
Well, Its not like causing any big known issues realtime works fine.
Just worried
i am too π
I hope it doesn't effect data
also, is there any documentation on how realtime works behind the scenes, since realtime of flutter sdk is not working right yet, will go with custom solution for now
In docs it shows install instead of upgrade π
I don't think, maybe retrieved data, but not sent data, so probably nothing will get corrupted or anything
it should be upgrade now π§
Hmm
appwrite logs
Any update on this?
im really not sure about this...i haven't seen this
btw, you might want to upgrade to 1.4.2 (and run migrate command)
Recommended threads
- [SOLVED] Error upgrading from 1.8.1 to 1...
DO Self-hosted server failed to upgrade with this error "Error response from daemon: client version 1.52 is too new. Maximum supported API version is 1.42". U...
- MariaDB refuses to connect to appwrite
Earlier, I tried updating my Appwrite version from 18.1.x to the latest release because my Flutter package required it to function properly. I used the official...
- executeFunction intermittently throws Fo...
Environment: Flutter app using the Appwrite Flutter SDK, calling executeFunction for [describe endpoint, e.g. live-stream-related function]. *Description*: Int...