fix: make project android 16kb compatible

[WoLewicki]

Fixes APP-2812

What changed (plus any additional context for devs)

I bumped @shopify/react-native-skia, expo and react-native-vision-camera to versions supporting 16kb, those were small version bumps so hopefully don't destroy anything.

Made patches for mmkv, quick-md5 and turbo-haptics since there are no versions supporting it yet.

Screen recordings / screenshots

Went through different app screens and did not see anything special, though I don't have extensive knowledge of the flows.
Unfortunately right now I am working on Android emulator which makes it impossible to check the flows with react-native-vision-camera and react-native-turbo-haptics.

Based on @janicduplessis comment, some skia cards:

What to test

There is no such warning when building app on Android:

and just generally that the app works well with those new versions of libraries.

Based on changed libraries:

• Check if haptics work correctly (would be weird if they didn't since I didn't change library code at all)
• Test if screens using camera behave correctly (vision-camera bump)
• Check as many animations/icons as you can (rn-skia bump)

[linear]

APP-2812 Google Playstore Policy Warning

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​@​expo/​env@​1.0.5 ⏵ 1.0.7
	npm/​@​react-native/​babel-plugin-codegen@​0.79.3 ⏵ 0.79.5
	npm/​@​expo/​image-utils@​0.7.4 ⏵ 0.7.6
	npm/​@​expo/​config@​11.0.10 ⏵ 11.0.13	+1			-1
	npm/​expo@​53.0.11 ⏵ 53.0.20	+1		+1	-1
	npm/​@​expo/​osascript@​2.2.4 ⏵ 2.2.5				-1
	npm/​@​expo/​prebuild-config@​9.0.6 ⏵ 9.0.11				-1
	npm/​@​shopify/​react-native-skia@​2.0.1 ⏵ 2.0.7	+1		+1	+2
	npm/​expo-constants@​17.1.6 ⏵ 17.1.7				+1
	npm/​expo-asset@​11.1.5 ⏵ 11.1.7
	npm/​@​react-native/​babel-preset@​0.79.3 ⏵ 0.79.5
	npm/​expo-modules-autolinking@​2.1.11 ⏵ 2.1.14	+1		+1
	npm/​@​expo/​package-manager@​1.8.4 ⏵ 1.8.6
	npm/​expo-font@​13.3.1 ⏵ 13.3.2			+1	+1
	npm/​expo-file-system@​18.1.10 ⏵ 18.1.11	+1		+1
	npm/​react-native-vision-camera@​4.6.4 ⏵ 4.7.1	+1		+1	+1
	npm/​@​expo/​cli@​0.24.14 ⏵ 0.24.20	+1			-1
	npm/​babel-preset-expo@​13.2.0 ⏵ 13.2.3				-1
	npm/​expo-modules-core@​2.4.0 ⏵ 2.5.0

View full report

[janicduplessis]

Looks good!

Can you open upstream PRs so we can remove these patches later?

[WoLewicki]

I already did for react-native-turbo-haptics and md5. mmkv is now on v3 but it only supports new arch so not sure if it would even be merged.

[janicduplessis]

Ok I agree, let's leave mmkv out

[jinchung]

Launch in simulator or device for 1018d1c

[jinchung]

I know you mentioned for testing that the reviewer should check that the app generally works well as the rn-skia changes impact across the app, but can you add under the "What to test" the areas that should get specific attention as well (e.g, usage of camera, haptics). This section is to make QA's life easier.

And then for screen recordings - though there is nothing to really show, can you add in that section at least written acknowledgement that you confirmed on device and went through a few screens to confirm animations across the app still look the same, etc.

[WoLewicki]

Sorry for the lack of information @jinchung. I updated the PR description. It might be a case that I missed something due to my lack of knowledge of how the things should look like.

[WoLewicki]

I went through release notes in those libraries and haven't found anything looking bad, but you never know ofc.

[janicduplessis]

For vision camera you can check the QR code scanner and skia these cards are basically all skia and the most likely to break

[WoLewicki]

Ok I checked those, camera launches and cards look the same 🎉