Operator.increment via updateRow returns 500 on tables with a point column (1.9.5) #12866

👟 Reproduction steps

Minimal A/B (same project, same integer column, only difference is a point column):

1. Create table A with only an integer column count (not required, default 0).
2. Create table B with integer column count and a required point column location.
3. Insert a row in each table with count: 10 (table B also gets a valid point, e.g. [-122.0, 37.0]).
4. On each row, call:

PATCH /v1/tablesdb/{databaseId}/tables/{tableId}/rows/{rowId}
Content-Type: application/json

{
  "data": {
    "count": "{\"method\":\"increment\",\"values\":[1]}"
  }
}

SDK equivalent:

await tablesDB.updateRow(
  databaseId: databaseId,
  tableId: tableId,
  rowId: rowId,
  data: {
    'count': Operator.increment(),
  },
);

Observed:

• Table A (no point): succeeds
• Table B (with point): fails with 500 general_unknown

5. On the failing table B row, the dedicated increment route still works:

PATCH /v1/tablesdb/{databaseId}/tables/{tableId}/rows/{rowId}/count/increment

{ "value": 1 }

👍 Expected behavior

updateRow with Operator.increment() should atomically increment the integer column on any table, including tables that also have a point column — same as incrementRowColumn / the /increment route.

👎 Actual Behavior

On tables that include a point column:

{
  "message": "Server Error",
  "code": 500,
  "type": "general_unknown",
  "version": "1.9.5"
}

• No useful error body.
• Explicit assignment (e.g. "count": 11) on the same row works.
• incrementRowColumn / /increment on the same row works.
• Also fails when staged inside a multi-table transaction (commit returns the same 500).

On an otherwise identical table without a point column, the same Operator.increment() via updateRow works.

🎲 Appwrite version

Different version (specify in environment)

💻 Operating system

Linux

🧱 Your Environment

• Appwrite 1.9.5
• Reproduced with the Dart server SDK and with raw HTTP
• Confirmed with a minimal A/B: integer-only table vs integer + required point column
• Workaround: use TablesDB.incrementRowColumn(...) (supports transactionId) instead of Operator.increment() in updateRow when the table has a point column

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct