Changes in Updates-test.ts

f0d67e12 - [expo-updates] Add fingerprintExperimental runtime version policy (#24126)

Mon, 11 Sep 2023 19:42:32 +0000

[expo-updates] Add fingerprintExperimental runtime version policy (#24126)# Why Manually handling runtimeVersions is a big pain for projects that uses native modules. This PR adds a new runtime policy that handles this automatically. See: https://discord.com/channels/695411232856997968/1142023605908156476/1142023605908156476 # How Using [expo-fingerprint](https://github.com/expo/expo/tree/main/packages/@expo/fingerprint#readme) to auto-generate a hash for the project. # Test Plan I made the changes locally on a working project and the build was successfully with expo prebuild. I checked the native files and the runtime version was set to the project hash. # Checklist - [x] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [x] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [x] This diff will work correctly for `npx expo prebuild` & EAS Build (eg: updated a module plugin). --------- Co-authored-by: Expo Bot <34669131+expo-bot@users.noreply.github.com> Co-authored-by: Aman Mittal Co-authored-by: Kudo Chien Co-authored-by: Douglas Lowder List of files: /expo/packages/@expo/config-plugins/src/android/__tests__/Updates-test.ts

82ade864 - [config-types] Remove classic updates (#24066)

Wed, 23 Aug 2023 18:15:02 +0000

[config-types] Remove classic updates (#24066) List of files: /expo/packages/@expo/config-plugins/src/android/__tests__/Updates-test.ts

2fae8288 - [config-plugins][updates] Add support for config.updates.useClassicUpdates defaulting behavior (#22169)

Fri, 21 Apr 2023 18:18:09 +0000

[config-plugins][updates] Add support for config.updates.useClassicUpdates defaulting behavior (#22169) List of files: /expo/packages/@expo/config-plugins/src/android/__tests__/Updates-test.ts

ed3bd27b - chore(prebuild-config, config-plugins): rewrite tests to use latest template for fixtures (#21339)

Wed, 01 Mar 2023 18:18:27 +0000

chore(prebuild-config, config-plugins): rewrite tests to use latest template for fixtures (#21339)# Why - The previous tests were using static representations of the versioned fixtures. This meant that many tests were possibly outdated. - Now that the CLI is versioned, we can test against the latest templates to ensure our config plugins are always up to date. # How - Pull in fixtures from the local template. - Rewrite tests to work with new fixtures. # Test Plan - Tests should continue to pass. --------- Co-authored-by: Expo Bot <34669131+expo-bot@users.noreply.github.com> List of files: /expo/packages/@expo/config-plugins/src/android/__tests__/Updates-test.ts

fc285a6f - [config-plugins][config-types] rebuild files (#20168)

Wed, 23 Nov 2022 21:23:41 +0000

[config-plugins][config-types] rebuild files (#20168) List of files: /expo/packages/@expo/config-plugins/src/android/__tests__/Updates-test.ts

09bd1012 - Add requestHeaders option in app.js to avoid issues with expo prebuild when using release channels outside EAS build (#18737)

Tue, 22 Nov 2022 23:14:51 +0000

Add requestHeaders option in app.js to avoid issues with expo prebuild when using release channels outside EAS build (#18737)# Why On the documentation [https://docs.expo.dev/bare/updating-your-app/](https://docs.expo.dev/bare/updating-your-app/) is stated that you can configura the release channel manually by adding `expo.modules.updates.UPDATES_CONFIGURATION_REQUEST_HEADERS_KEY` or `EXUpdatesRequestHeaders` in their respective places. However, `expo prebuild` does not consider this option resulting in missing or removed release channel configuration. The proposed solution introduces a new configuration option in app.json updates section called `requestHeaders` that allows to handle this configuration automatically, just like `codeSigningMetadata`. # How I followed precisely how `codeSigningMetadata` option is implemented (styles, names, etc) and modified: `packages/@expo/config-types/src/ExpoConfig.ts` Added `requestHeaders` option under updates in order to update the schema `packages/@expo/config-plugins` I updated iOS and Android Updates.ts and added the relative helpers and tests, closely follwing how `codeSigningMetadata` was implemented It is possible now to add the updates request headers directly in `app.json` and have `expo prebuild` handle this configuration automatically. # Test Plan I have included the relative tests following the behavior of `codeSigningMetadata` option. I have also tested on a real project by copying the builds of config-plugins in the node_modules folder. ![image](https://user-images.githubusercontent.com/25666241/185808082-09fb1d20-78c3-46de-a73d-b9afdb4e9c71.png) # Checklist - [X] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [X] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [X] This diff will work correctly for `expo prebuild` & EAS Build (eg: updated a module plugin). NOTE: I have updated the relevant documentation page `docs/pages/bare/updating-your-app.md` but not the `app.json / app.config.js` as I thought adding instructions to add release channel information in app.js may confuse managed expo users. Co-authored-by: Will Schurman Co-authored-by: Douglas Lowder Co-authored-by: Bartosz Kaszubowski Co-authored-by: Douglas Lowder List of files: /expo/packages/@expo/config-plugins/src/android/__tests__/Updates-test.ts

166385e2 - [config-plugins] Fix runtime version parsing on Android (#19821)

Fri, 11 Nov 2022 19:40:56 +0000

[config-plugins] Fix runtime version parsing on Android (#19821)# Why Fix the issue described in https://linear.app/expo/issue/ENG-6212/fix-runtime-version-parsing-on-android where trailing zeroes are removed from Android runtime version values. # How Modify the existing updates code in `@expo/config-plugins/src/android/Update.ts` to write the runtime version as a string resource, and modify `UpdatesConfiguration.kt` (expo-updates) to check for the runtime version in the string resource first, and fall back to checking the manifest as before if the string resource is not found. # Test Plan - New unit test added - Tested in EAS builds and verified the expected metadata shows up in the Android manifest, and the expected string shows up in the app's `strings.xml`. # Checklist - [ ] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [x] This diff will work correctly for `expo prebuild` & EAS Build (eg: updated a module plugin). List of files: /expo/packages/@expo/config-plugins/src/android/__tests__/Updates-test.ts

082815dc - chore: migrate config, config-plugins, config-types, prebuild-config (#17958)

Tue, 28 Jun 2022 00:09:27 +0000

chore: migrate config, config-plugins, config-types, prebuild-config (#17958) List of files: /expo/packages/@expo/config-plugins/src/android/__tests__/Updates-test.ts