Add default values for package name and bundle identifier

[Sergemuhundu]

Description

Please include a summary of the changes and the related issue.

Type of Change

• [ ] Bug fix
• [ ] New feature
• [ ] Breaking change
• [ ] Documentation update

Checklist

• [ ] My code follows the style guidelines of this project
• [ ] I have performed a self-review of my code
• [ ] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [ ] My changes generate no new warnings

Previous screenshots

Please add here videos or images of previous status

Current screenshots

Please add here videos or images of previous status

Summary by CodeRabbit

• New Features

  • Enhanced error handling by adding checks for the EXPO_TOKEN secret in Android and iOS workflows.
  • Introduced fallback default values for EXPO_PROJECT_PACKAGE_NAME and EXPO_PROJECT_IOS_BUNDLE_IDENTIFIER in case of missing secrets.

• Bug Fixes

  • Improved robustness of the build and deployment processes by ensuring workflows do not proceed without necessary credentials.

• Chores

  • Updated workflow configurations for both Android and iOS builds to streamline the build, deploy, and publish processes.

[coderabbitai[bot]]

[!CAUTION]

Review failed

The pull request is closed.

Walkthrough

The pull request updates the workflow configurations for building, deploying, and publishing Android and iOS mobile applications. It introduces checks for the EXPO_TOKEN secret to ensure necessary credentials are provided before proceeding. Additionally, default values for EXPO_PROJECT_PACKAGE_NAME and EXPO_PROJECT_IOS_BUNDLE_IDENTIFIER are set to allow workflows to continue even if specific secrets are not defined. Overall, the changes focus on enhancing error handling and maintaining the existing structure of the workflows.

Changes

File	Change Summary
.github/workflows/mobile.apps.android.yml	Updated to check for EXPO_TOKEN, added fallback values for app.json, and modified Google credentials masking.
.github/workflows/mobile.apps.ios.yml	Added EXPO_TOKEN check, fallback values for app.json, and maintained existing steps for App Store credentials.
.github/workflows/mobile.apps.stage.android.yml	Included EXPO_TOKEN check, updated to use latest Node.js actions, and added fallback values for app.json.
.github/workflows/mobile.apps.stage.ios.yml	Added EXPO_TOKEN check, fallback values for app.json, and retained existing steps for EAS configuration.

Possibly related PRs

• #3160: This PR adds environment variables EXPO_PROJECT_PACKAGE_NAME and EXPO_PROJECT_IOS_BUNDLE_IDENTIFIER, which are directly referenced in the main PR's workflow updates for generating app.json.
• #3207: Although this PR focuses on adding iOS credentials, it modifies the eas.json file, which is relevant to the overall configuration and deployment process discussed in the main PR.

Suggested reviewers

• evereq

Poem

🐰 In the garden where workflows bloom,
Secrets checked to avoid the gloom.
With defaults set, we hop along,
Building apps, where we belong!
A token here, a bundle there,
Together we’ll deploy with care! 🌼

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

- [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

🪧 Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , please review it.` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` - `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (Invoked using PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. ### Other keywords and placeholders - Add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. - Add `@coderabbitai summary` to generate the high-level summary at a specific location in the PR description. - Add `@coderabbitai` anywhere in the PR title to generate the title automatically. ### CodeRabbit Configuration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.