Hello! I am self-hosting an Appwrite instance and ran into this issue https://github.com/appwrite/appwrite/issues/9906 I saw that the bug has already been fixed, but not in version 1.7.4. When I tried upgrading to 1.8.0-RC1, the Appwrite console only shows a 500 error.
Has anyone successfully upgraded to 1.8.0-RC1? Any tips on how to resolve this error would be greatly appreciated 🙏
RC is Release Candidate. Not publicly available so you should stay at 1.7.4 until non-RC 1.8 comes out
Oh, I see. So I’ll need to wait until 1.8 is officially released for this bug to be fixed? Is there any way I can get a slightly newer build (with the fix already merged) before the stable release?
Yes
OK🥲 .. Thanks for your reply
I waited a day and it fixed itself. I think it's because of the cache.
Yes, the non-RC will have that fixed
Great! Since my app is still in active development, I think I am going to RC😃
Recommended threads
- Error upgrading from 1.8.1 to 1.9.0
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...