Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: internal preview build iOS #1093

Closed

Conversation

thierryskoda
Copy link
Collaborator

@thierryskoda thierryskoda commented Oct 24, 2024

@alexrisch this is a small fix to fix what happened here with my internal build on iOS https://github.com/ephemeraHQ/converse-app/actions/runs/11499980582/job/32011918449

I think there's a lot of clean up that could be done for deployment but didn't want to put more time now until you think it could be a huge gain.

I know you also have some work in progress on that.

Summary by CodeRabbit

  • Chores
    • Removed the GitHub Actions workflow for creating TestFlight builds for iOS, which eliminates automated build submissions.
    • Simplified the eas.json configuration by removing extends properties for iOS and Android configurations, while adding specific ascAppId values for iOS.

@thierryskoda thierryskoda requested a review from a team as a code owner October 24, 2024 17:37
Copy link

coderabbitai bot commented Oct 24, 2024

Warning

Rate limit exceeded

@thierryskoda has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 5 minutes and 57 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Files that changed from the base of the PR and between 0593194 and c111761.

Walkthrough

The changes include the deletion of the .github/workflows/testflight.yml file, which contained a GitHub Actions workflow for creating TestFlight builds for iOS applications. Additionally, the eas.json configuration file was modified by removing several extends properties from the iOS and Android configurations, simplifying the inheritance model. New ascAppId values were added for the iOS configurations, while retaining the track settings for Android.

Changes

File Path Change Summary
.github/workflows/testflight.yml Deleted the workflow for creating TestFlight builds for iOS applications.
eas.json Removed extends properties from production-ios, preview-ios, and production-android; added ascAppId values for production-ios and preview-ios; retained track properties for Android configurations.

Poem

In the meadow where rabbits play,
A workflow's gone, but that's okay!
With eas.json now more clear,
New IDs shine, no need to fear.
Hops of joy for builds ahead,
In our burrow, no worries spread! 🐇✨


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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, 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 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 for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@thierryskoda thierryskoda changed the title remove testflight action fix: internal preview build iOS Oct 24, 2024
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 5d87302 and 0593194.

📒 Files selected for processing (2)
  • .github/workflows/testflight.yml (0 hunks)
  • eas.json (1 hunks)
💤 Files with no reviewable changes (1)
  • .github/workflows/testflight.yml
🧰 Additional context used
🪛 Biome
eas.json

[error] 85-85: expected , but instead found Ø

Remove Ø

(parse)


[error] 86-86: expected : but instead found }

Remove }

(parse)

eas.json Outdated
Comment on lines 85 to 87
}
}
}
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Fix JSON syntax errors

There are syntax errors in the JSON structure that need to be addressed:

  1. Remove the unexpected Ø character
  2. Fix the JSON structure

Apply this diff to fix the syntax:

    "preview": {
      "android": {
        "track": "internal"
      },
      "ios": {
        "ascAppId": "6478027666"
      }
-
-  }
-}
+    }
+  }
+}
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
}
}
}
"preview": {
"android": {
"track": "internal"
},
"ios": {
"ascAppId": "6478027666"
}
}
}
}
🧰 Tools
🪛 Biome

[error] 85-85: expected , but instead found Ø

Remove Ø

(parse)


[error] 86-86: expected : but instead found }

Remove }

(parse)

Comment on lines +73 to 84
},
"ios": {
"ascAppId": "1658819514"
}
},
"production-android": {
"extends": "production"
},
"preview": {
"android": {
"track": "internal"
}
},
"preview-ios": {
"extends": "production",
},
"ios": {
"ascAppId": "6478027666"
}
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codebase verification

Based on the gathered information, I can now provide a final response:

Deployment workflow changes confirmed - action required

The changes indicate a transition from GitHub Actions TestFlight workflow to EAS Submit:

  1. TestFlight GitHub Action has been removed
  2. EAS Submit configuration has been added with correct App Store Connect IDs:
    • Production: 1658819514
    • Preview: 6478027666
  3. However, no deployment documentation updates were found to reflect this change

Action items:

  • Documentation needs to be updated to reflect the new EAS Submit deployment process
  • Team should be notified about the deployment workflow change
  • Consider creating a deployment guide for the new EAS Submit process
🔗 Analysis chain

Verify App Store Connect IDs and deployment strategy

The changes indicate a shift from GitHub Actions TestFlight workflow to EAS Submit for iOS deployments. Please verify:

  1. The App Store Connect IDs are correct:
    • Production: 1658819514
    • Preview: 6478027666
  2. The team is aware of the deployment process change
  3. Documentation has been updated to reflect the new deployment workflow

Let's verify if these are the correct App Store IDs:


Let me gather more information about the deployment workflow changes to verify if documentation has been updated.


Let me search for documentation and deployment workflow changes.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for any references to these App Store IDs in the codebase
# to ensure consistency and verify their usage

echo "Searching for Production App Store ID..."
rg -i "1658819514"

echo "Searching for Preview App Store ID..."
rg -i "6478027666"

# Also check for any remaining TestFlight references that might need updating
echo "Checking for remaining TestFlight references..."
rg -i "testflight" -g '!.git'

Length of output: 523


Script:

#!/bin/bash
# Check for documentation updates related to deployment changes
echo "Searching for deployment-related documentation..."
fd -e md -e mdx | xargs rg -i -l "deploy|eas submit|app store|testflight"

# Check for removed GitHub Actions workflow
echo "Checking for TestFlight GitHub Action removal..."
fd -g '.github/workflows/*.yml' | xargs rg -i "testflight|ios|app store"

# Check for EAS Submit configuration
echo "Checking for EAS Submit configuration..."
rg -i "eas submit|submit-type" -g 'eas*'

Length of output: 181279


Script:

#!/bin/bash
# Search for documentation files and deployment related changes
echo "Searching for deployment documentation..."
fd -e md -e mdx | xargs rg -l "deployment|submit|testflight|app store"

# Check for removed TestFlight workflow file
echo "Checking for removed TestFlight workflow file..."
git log --diff-filter=D -p | rg "testflight|ios.*workflow"

# Check for EAS Submit related changes in app.json/app.config.js
echo "Checking EAS Submit config..."
rg "submit|ascAppId" app.config.ts app.json eas.json

Length of output: 2355

@alexrisch
Copy link
Collaborator

@thierryskoda going to close this out since it should be resolved with the other changes

@alexrisch alexrisch closed this Oct 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants