-
Notifications
You must be signed in to change notification settings - Fork 4
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
MOB-1817 Environment staging updates #479
Conversation
af4ef68
to
3470898
Compare
@@ -12351,14 +12351,14 @@ | |||
}; | |||
name = Release; | |||
}; | |||
3B43E3D91D95C48E00BBA9DB /* Beta */ = { | |||
3B43E3D91D95C48E00BBA9DB /* Development_TestFlight */ = { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's kind of counter-intuitive for me to find both words Development
and TestFlight
in the the name of the configuration. My brain associates the term Development
with a Debug
configuration, and when building for TestFlight
usually a Release
-like config is used.
So for clarity, the term Development
must be included, so that SPM in iOS-core does infer it as non-#Production
environment? Did I catch that correctly?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the comment @ecotopian . I agree it does sound counter intuitive. I've gone through the reason of choosing this approach more thoroughly in the Core PR.
I was planning to update the README as well as I do think that indeed providing additional knowledge to it would concretely help clarifying.
6f7802d
to
925aafd
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good to me 🚀
Will just wait for the final review and approval after Core is properly updated.
@@ -34,9 +34,6 @@ class AppDelegate: UIResponder, UIApplicationDelegate { | |||
|
|||
appLaunchUtil = AppLaunchUtil(profile: profile) | |||
appLaunchUtil?.setUpPreLaunchDependencies() | |||
|
|||
// Setup environment | |||
Environment.current = AppConstants.BuildChannel == .release ? .production : .staging |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧹 💯
#### Build configurations | ||
|
||
The app is equipped by two custom Build Configurations for ad-hoc distribution over TestFlight and AppCenter. | ||
The `Development_` prefix added to those two, serves the purpose of picking the correct `Core` module build configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Quick and clear 👏
If you think it is worth it, could even link to the ADR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The only reason I woulnd't want to link it is due to this repo being public and people will land into the 404
Github page 😕 . I know it's widely practiced for Jira tickets for other OSS projects but when it comes to Github repo it may be somewhat unpleasant to find into a README doc 🤔
7419170
to
17ccaf4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🟢
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking great now!
MOB-1817
Context
This PR integrates the changes done in the
Core
module.Approach
The key updates here are the build configuration renaming, in order to match the requirement endpoints.
Debug
->Staging
endpointsBetaDebug
->Staging
endpointsDevelopment_TestFlight
->Staging
endpointsDevelopment_AppCenter
->Staging
endpointsRelease
->Production
endpointsIt also integrates the updates to make the autocomplete done via the staging endpoint bypassing the challenge.
Tests performed
Build and run the
EcosiaBeta
scheme =>BetaDebug
configurationBuild and run the
Ecosia
scheme =>Debug
configurationTriggered AppCenter build over CircleCI
EcosiaBeta
scheme =>Development_AppCenter
configurationTriggered TestFlight build over CircleCI
EcosiaBeta
scheme =>Development_TestFlight
configurationTriggered TestFlight build over CircleCI
Ecosia
scheme =>Release
configurationOther
🚨Last commit to be reverted. Needed to pass tests only 😉