持续部署

• 导航到 expo.dev/settings/access-tokens，然后：

  ¥Navigate to expo.dev/settings/access-tokens and then:

• 单击“创建令牌”以创建新的个人访问令牌。

  ¥Click Create token to create a new personal access token.

• 复制生成的令牌。

  ¥Copy the generated token.

• 将 "your-username" 和 "your-repo-name" 替换为你的项目信息，导航到 https://github.com/your-username/your-repo-name/settings/secrets/actions。

  ¥Navigate to https://github.com/your-username/your-repo-name/settings/secrets/actions by replacing "your-username" and "your-repo-name" with your project's info.

• 在存储库密钥下，单击新建存储库密钥。

  ¥Under Repository secrets, click New repository secret.

• 创建一个名为 EXPO_TOKEN 的密钥，并将复制的访问令牌粘贴为值。

  ¥Create a secret with the name EXPO_TOKEN, and paste the copied access token in as the value.

在调试模式下运行 GitHub 工作流程将自动将 --debug 标志添加到作为操作的一部分运行的命令中，并且输出将在工作流程运行日志中可用。

¥Running your GitHub workflows in debug mode will automatically add the --debug flag to the commands run as part of the action, and the output will be available in the workflow run logs.

指纹哈希中包含的默认项目文件在托管工作流项目和裸工作流项目之间有所不同。EAS 通过检查 android 和 ios 和目录是否被 gitignored 来自动检测你的工作流。如果是，EAS 会将该项目视为托管工作流项目，从而表明 package.json 依赖的哈希值足以确定指纹兼容性。

¥The default project files included in the fingerprint hash differs between managed and bare workflow projects. EAS automatically detects your workflow by checking if the android and ios and directories are gitignored. If they are, EAS will treat the project as a managed workflow project, thus dictating that a hash of the package.json dependencies are sufficient to determine fingerprint compatibility.

如果你注意到在不同的机器或环境中生成了不同的指纹，则可能意味着哈希计算中包含了意外的文件。@expo/fingerprint 有一组预定的文件用于包含/排除哈希计算，但你的项目设置通常可能需要额外的排除。对于包含原生目录（android 和 ios）的项目，这更常见。

¥If you notice different fingerprints being generated across different machines or environments, it may mean that unanticipated files are being included in the hash calculation. @expo/fingerprint has a predetermined set of files to include/exclude for hash calculation, but often your project setup may require additional excludes. For projects that include native directories (android and ios) this is more common.

我们提供用于识别哪些文件导致指纹不一致的工具，以及将这些文件从项目指纹计算中排除的机制。

¥We provide tools for identifying which files are causing fingerprint inconsistencies and mechanisms to exclude those files from fingerprint calculations for your project.

要识别不同机器或环境中的指纹差异：

¥To identify differences in fingerprints on different machines or environments:

• 在每台机器/环境（npx expo-updates fingerprint:generate）上运行指纹生成命令时，传递 --debug 标志。

  ¥When running fingerprint generation commands on each machine/environment (npx expo-updates fingerprint:generate), pass --debug flag.

• 这些命令运行的差异输出以确定导致差异的文件。这些工具可能会有所帮助：

  ¥Diff outputs from those command runs to determine files causing the difference. These tools may be helpful:

  • JSON Pretty Print 格式化输出。

    ¥JSON Pretty Print to format the output.

  • JSON Diff 比较输出并识别导致差异的文件。

    ¥JSON Diff to compare the output and identify the files causing the discrepancies.

要排除导致差异的文件，请将它们添加到 .fingerprintignore 文件中，如 @expo/fingerprint 文档中所述。

¥To exclude files causing the differences, add them to the .fingerprintignore file as described in the documentation for @expo/fingerprint.