Neil Marcellini

@paultsimura the new rate field PR has been merged. Agata is working on some follow ups, but that should be done soon [[CP Staging] Feat/36985 create new rate field followups](https://github.com/Expensify/App/pull/40711#top)....

Ok yeah good point. I forgot how slowly that's coming along on the backend 😅. I'll let you know when it's ready, and I'll put it on HOLD for now.

I've been investigating in the Slack thread

@roryabraham do you have any ideas about this, since you implemented the concierge compose updates?

We found that this only happens for certain messages sent using the Concierge compose tool. The problematic message is the following. If you manually edit a report action message to...

Ah great thanks so much @paultsimura . I'm going to HOLD this issue on that one, since this one is a bit different I think it would be wise to...

@paultsimura good point, but I think you can use Flipper dev tools to modify the props of components, and set an invalid message that way.

You can only really test on dev like this, but it's enough to verify that it's fixed! https://github.com/Expensify/App/assets/26260477/7289872c-4e48-419f-b172-f1c71b5730a2

Checking off https://github.com/Expensify/App/issues/36075 since it's a very minor issue

@getusha it's a frontend only beta so you can just change Permissions.ts to return true for you