Based on my read of the docs, what's going on here is that in React 19, ref just becomes like any other prop. So we no longer needs a special type param for it.

Requesting changes for Podfile updates

I think it will be easier to track work here if I request changes for the task creation, that way @angelika knows where in the stack there are to-dos

This doesn't feel right. React.Ref and React.ElementRef are different. Why are we replacing them?

There is a code in Podfile that says it's needed to compile expo secure store in Notification Service. I tried to remove it, but I was getting errors like "sharedApplication not available for use in an App Extension". My guess is the notification service still compiles some RN stuff.

The new patch fixes this issue: https://github.com/software-mansion/react-native-reanimated/issues/7109#issuecomment-2841588588

Created ENG-11033 to track eventually making the image pasting work in the new arch

Spoke to @tomek about this offline, we're going to make this message encrypted if it's easy

If some JS logic is "duplicated" here in C++, we should add comments to both sides to make sure the implementations don't diverge

Nice work! Looks good to me :)

If yes, we'll sooner or later catch them, and apply this logic

Thanks! This looks great :)

Okay, let's try this to keep the height consistent, even for the error screen:

Thanks, this looks better!

Thanks, this looks way better! We're almost there... only thing left is to align the dimensions. I feel strongly that dimensions of a modal should not randomly change in size. It's okay that it looks kind of empty, we can eg. vertical-align the progress step indicator to make it look better. Additionally, realizing that the process of the subtitle in the header in only some cases (not on the starting screen) will be weird, so probably best to move the subtitle below the "underline" that appears under the header, so that the underline looks look like it jumps around.

UI feedback

Copy looks good!

The current text is a little long. I've tried to suggest shorter phrases below

Thanks, makes sense. Wonder if we should rename serverCanHandle to canHandle and serverTranscodesImage to canTranscodeImage, since it's not really server-related anymore

Does this disable it just for images sent in thin threads on web, where (I think) we use sharp on the keyserver for transcoding? Or does it disable it more globally, eg. in thick threads, or in thin threads sent from mobile?

Looks good!

Copy looks great!

Copy looks great!