[CAL-3377] Issue with stripe meta data corrupts many different endpoints

[keithwillcode]

[ { "code": "invalid_type", "expected": "string", "received": "undefined", "path": [ "apps", "stripe", "currency" ], "message": "Required" } ]

Go to Sentry to see all the places it's affecting

_{From SyncLinear.com | CAL-3377}

[keithwillcode]

[SkipDead]

Possible way to reproduce the bug :

Two last actions I did :

1. I was trying to remove Stripe app from my account app. It did not work because I got a Bad Request error on the remove app button click.
2. I had another window (my website) and I was on the confirmation summary step. I clicked on the cancel button and confirmed it after being prompted to write a reason to cancel.

Current observed behavior :

integration on website
I receive an error 500 when trying to display on my website any Event :

behaviors on the cal dashboard
On the dashboard of cal, I cannot access my Event.

Payload on https://app.cal.com/api/trpc/eventTypes/getByViewer? call when I look at the console :

[
    {
        "error": {
            "json": {
                "message": "[\n  {\n    \"code\": \"invalid_type\",\n    \"expected\": \"string\",\n    \"received\": \"undefined\",\n    \"path\": [\n      \"apps\",\n      \"stripe\",\n      \"currency\"\n    ],\n    \"message\": \"Required\"\n  }\n]",
                "code": -32603,
                "data": {
                    "code": "INTERNAL_SERVER_ERROR",
                    "httpStatus": 500,
                    "path": "getByViewer"
                }
            }
        }
    }
]

It looks like a validation error related to stripe possibly because of the payload ? My honest take is that for some reasons, the currency selected for a stripe payment got emptied for an unkown reason. I can visually see the error on the cancelled booking tab :

but on the others tabs shows that I have no booking. It is obivously because of the same error 500. Would say the same for the event Type page.

[sean-brydon]

Context: Me and @emrysal are doing some digging on this - we see this on the update event type and think its an issue with dirty fields.

We are also seeing this in another few places which are looking into right now - eventType viewer

[SkipDead]

Ok thank you for the follow up.

Also, I would recommend some kind of validation / catching when a a specific event type has a problem with its schema.

For example, I would see the error for a specific event without affecting the whole page / system.

If I have 2 event type but one of them does not pass the validation, the system could show the error only for that event type but will show the second event type regardless.

Will make the system more robust and not lock the account because of one invalid event type. I am not familiar with the architecture of cal so I am not sure if this check is possible to do. But it would be interesting as it seems that it is affecting the whole booking feature page and the event type page.