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

Push prerelease builds to new prerelease app #7986

Merged
merged 5 commits into from
Oct 9, 2024

Conversation

angusbayley
Copy link
Contributor

@angusbayley angusbayley commented Oct 2, 2024

✅ Checklist

  • npx changeset was attached.
  • Covered by automatic tests.
  • Impact of the changes:
    • ...

📝 Description

A new app has been created in App Store Connect for prerelease builds. This PR specifies that prerelease builds should be sent to that app, by defining the following new properties during prerelease app build and testflight upload:

configuration: "Prerelease"
bundle id: com.ledger.live.prerelease
app identifier: com.ledger.live.prerelease

These correspond to a newly created configuration in Xcode and a newly created Identifier and Provisioning Profile in identities/developer portal.

One prerelease build has successfully been sent to this app - here's what it looks like in Testflight:

image

❓ Context

An extension of https://ledgerhq.atlassian.net/browse/LIVE-13485


🧐 Checklist for the PR Reviewers

  • The code aligns with the requirements described in the linked JIRA or GitHub issue.
  • The PR description clearly documents the changes made and explains any technical trade-offs or design decisions.
  • There are no undocumented trade-offs, technical debt, or maintainability issues.
  • The PR has been tested thoroughly, and any potential edge cases have been considered and handled.
  • Any new dependencies have been justified and documented.
  • Performance considerations have been taken into account. (changes have been profiled or benchmarked if necessary)

Copy link

vercel bot commented Oct 2, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

5 Skipped Deployments
Name Status Preview Comments Updated (UTC)
ledger-live-docs ⬜️ Ignored (Inspect) Visit Preview Oct 9, 2024 9:33am
ledger-live-github-bot ⬜️ Ignored (Inspect) Visit Preview Oct 9, 2024 9:33am
native-ui-storybook ⬜️ Ignored (Inspect) Visit Preview Oct 9, 2024 9:33am
react-ui-storybook ⬜️ Ignored (Inspect) Visit Preview Oct 9, 2024 9:33am
web-tools ⬜️ Ignored (Inspect) Visit Preview Oct 9, 2024 9:33am

@live-github-bot live-github-bot bot added the mobile Has changes in LLM label Oct 2, 2024
@angusbayley angusbayley force-pushed the support/new-nightly-app-id branch 2 times, most recently from 347fe47 to 1b1c64f Compare October 3, 2024 09:43
Base automatically changed from support/new-nightly-app-id to develop October 3, 2024 13:12
@angusbayley angusbayley force-pushed the support/new-prerelease-app-id branch 2 times, most recently from 3055f56 to 672b374 Compare October 7, 2024 15:08
@angusbayley angusbayley marked this pull request as ready for review October 7, 2024 16:34
@angusbayley angusbayley requested a review from a team as a code owner October 7, 2024 16:34
themooneer
themooneer previously approved these changes Oct 8, 2024
# This should come from env files - as we move each release type to its own app we will
# move them away from "Release" and to their own .env-file defined configuration
configuration: options[:nightly] ? ENV["APP_CONFIGURATION"] : "Release",
configuration: ENV["APP_CONFIGURATION"],
Copy link
Contributor Author

Choose a reason for hiding this comment

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

configuration is correctly set in .env files for this one 🥳

@angusbayley angusbayley merged commit b64a0ee into develop Oct 9, 2024
43 checks passed
@angusbayley angusbayley deleted the support/new-prerelease-app-id branch October 9, 2024 10:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
mobile Has changes in LLM
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants