Relationship Attributes not returned in GET Calls

REST Calls to my database do not return the values of Relationship Attributes in a document, which has caused several functionalities in my application to break.

I recently updated the schema of my prod db and ever since GET Calls to my DB have not been returning values of any Relationship Attribute from my Collection

As you can see in this image (Highlighted Row number 70), friends is a relationship attribute which contains a document (is not empty)

However this is the result recieved on GET Calls to the same document

As you can see, none of the Relationship Attributes are present (followers, friends, userReports)

But I was not expecting the attrs with no documents to show up anyways, because I know that on Schema updates by default the added fields remain null until an update call is recieved by the document

However, this behaviour also occurs even when the field is clearly populated

On line number 19 of the GET Response we can see 68e642bd0006010fc35e which, according to my Appwrite.json is a two-way key for a relationship attribute

If you guys need to take a look, entire appwrite.json is available on https://github.com/AOSSIE-Org/Resonate-Backend/blob/dev/appwrite.json

@Jake Could you please take a look at this? Prod is broken since last night and I need to get this fixed asap

<@462046107556511744> Can you please take a look at this, been waiting all day for some resolution and support

Key features have been broken for over 2 days between the OAuth issue from yesterday and this

I'm also facing same issue, relationship attributes are not getting fetched

This is expected: https://appwrite.io/docs/products/databases/relationships#performance-loading

loading while using * as a wildcard query also returns none of the relationship attributes

Also, the blog post announcing this change (https://appwrite.io/blog/post/announcing-opt-in-relationship-loading) mentions this:

"Adopting this new feature is seamless and requires no additional code changes for your existing setups. Old SDK versions maintain their existing behavior, ensuring full backward compatibility. Meanwhile, new queries and projects immediately benefit from optimized loading, achieving maximum efficiency without hassle."

However, atleast for my application, these were not backward compatible, as key functionalities broke down in Prod

If you upgraded your SDK, you adopted the opt in relationship.

You can't just use *. You need to explicitly specify the relationship

Alright, thanks for the response. I've pushed an update to my prod.