[SOLVED] Exception: This domain is not connected to any Appwrite resource yet.

I recently upgraded my Appwrite installation from 1.2.1 to 1.4.4 on both my localhost and my production server. When I connect to my production server from my Flutter mobile app, everything works fine. However, when I connect to my localhost, I get a stream of errors in the appwrite/appwrite:1.4.4 container log:

TypeScript

2023-10-30 07:19:52 [Error] Method: GET
2023-10-30 07:19:52 [Error] URL: /v1/databases/:databaseId/collections/:collectionId/documents
2023-10-30 07:19:52 [Error] Type: Appwrite\Extend\Exception
2023-10-30 07:19:52 [Error] Message: This domain is not connected to any Appwrite resource yet. Please configure custom domain or function domain to allow this request.
2023-10-30 07:19:52 [Error] File: /usr/src/code/app/controllers/general.php
2023-10-30 07:19:52 [Error] Line: 67 
2023-10-30 07:19:53 [Error] Timestamp: 2023-10-30T07:19:53+00:00
2023-10-30 07:19:53 [Error] Method: GET
2023-10-30 07:19:53 [Error] URL: /v1/account
2023-10-30 07:19:53 [Error] Type: Appwrite\Extend\Exception
2023-10-30 07:19:53 [Error] Message: This domain is not connected to any Appwrite resource yet. Please configure custom domain or function domain to allow this request.
2023-10-30 07:19:53 [Error] File: /usr/src/code/app/controllers/general.php
2023-10-30 07:19:53 [Error] Line: 67```

I've compared the localhost's and production server's `.env` file and aside from a few expected variables being different, they are the same. The .env file used to work on localhost for 1.2.1 but seems no longer to work for 1.4.4. I assume I'm missing a variable setting on localhost. Any thoughts what it is?

TL;DR

I upgraded my Appwrite installation and encountered an error on localhost where I received the message "This domain is not connected to any Appwrite resource yet." The solution is to add the variable `_APP_DOMAIN_FUNCTIONS=localhost` to the `.env` file. This variable was not set in my production environment but everything still worked correctly.

For anyone with the same issue, it appears resolved by adding: