-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[$250] Set HybridApp Testflight environment to staging #51193
Comments
Triggered auto assignment to @VictoriaExpensify ( |
Code in question is here: https://github.com/Expensify/App/blob/main/src/libs/Environment/getEnvironment/index.native.ts#L32-L36 |
Happy to review this as C+ since this bug I've been reviewing is related this one. |
Thanks @situchan - assigned. |
Job added to Upwork: https://www.upwork.com/jobs/~021848496225680121076 |
Current assignee @situchan is eligible for the External assigner, not assigning anyone new. |
ProposalPlease re-state the problem that we are trying to solve in this issue.Set HybridApp Testflight environment to staging What is the root cause of that problem?Currently we return the production environment if it's hybrid app App/src/libs/Environment/getEnvironment/index.native.ts Lines 33 to 36 in 36805e2
What changes do you think we should make in order to solve the problem?We should return the staging environment if (NativeModules.HybridAppModule) {
environment = CONST.ENVIRONMENT.STAGING;
return;
} What alternative solutions did you explore? (Optional) |
Asked confirmation here |
Oh wait isn't it dupe of #50843? |
yes dupe |
Hey! 👋 I've left an update here, since this is a duplicated issue! |
Ah cool, I'll close this one. |
Right now, when you use the HybridApp Testflight app, it is treated as a production app. This means our debugging tools are not available to use. Ideally, we should make it so that the HybridApp testflight is treated as a staging app. Just like the NewExpensify staging app is. That way we'll have access to the debug mode and various debugging tools.
cc @AndrewGable @staszekscp
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @The text was updated successfully, but these errors were encountered: