Hybrid Android app – Copilot – Unable to switch to own account from copilot account

[IuliiaHerets]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: v9.0.50-0
Reproducible in staging?: N
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5097100
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team

Action Performed:

1. Go to Hybrid app
2. Login as the account that has full copilot access
3. Tap on Settings/header arrows
4. Switch to copilot accounts
5. Tap on Settings/header arrows again
6. Switch to your own accounts

Expected Result:

User able to switch to own account from copilot account

Actual Result:

Error appears: Oops something went wrong

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6637677_1729169752290.video_2024-10-17_15-55-31.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @dangrous

[melvin-bot]

Triggered auto assignment to @dylanexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[melvin-bot]

Triggered auto assignment to @jasperhuangg (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[melvin-bot]

Triggered auto assignment to @stitesExpensify (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[IuliiaHerets]

Sorry, was confused with blocker label

[jasperhuangg]

@IuliiaHerets next time add both labels, they're used to indicate that the bug could either be from the front-end or the back-end.

[jasperhuangg]

These logs seem suspect, I'll try to reproduce on my own account to see if I run into the same issue. Need to wait for the beta cache to refresh though.

The logs indicate that the authPartnerID stored with the restored token we're passing to the CreateLogin command isn't recognized.

[twisterdotcom]

Nobody needs paying here right?

[dangrous]

I think @mollfpr will need payment for C+ review.

But I still need to double check that this is working on prod; @war-in suggests that it might not be yet. I'm about to try locally and on browserstack

[dangrous]

Okay so this doesn't work for me on hybrid app (though it works on regular android app). I don't know what changed!

[war-in]

I'm gonna build the app from the main branches and try to find some logs. I'll post them here 🫡

[war-in]

I managed to make it work by merging the main branches (not sure what exactly changed but it works 🤷).
Now I have a question about those few set actions

A few lines above we update the authToken and encryptedAuthToken but immediately we override them by calling the set with old (stashed) data.
I think we should update tokens after calling set. Do you think it makes sense?

[dangrous]

oh huh, yeah I think you're right!

[melvin-bot]

@dangrous, @twisterdotcom Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[melvin-bot]

@dangrous, @twisterdotcom Eep! 4 days overdue now. Issues have feelings too...

[melvin-bot]

@dangrous, @twisterdotcom Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it!

[melvin-bot]

@dangrous, @twisterdotcom 10 days overdue. Is anyone even seeing these? Hello?

[melvin-bot]

@dangrous, @twisterdotcom 12 days overdue. Walking. Toward. The. Light...

[melvin-bot]

This issue has not been updated in over 14 days. @dangrous, @twisterdotcom eroding to Weekly issue.

[dangrous]

Hi Melvin, still in progress. Aiming for early next week

[dangrous]

Estimated merge is on Friday!

[dangrous]

50% there - ND PR is merged, and the Mobile-Expensify one is up for final review from SWM

[dangrous]

okay! both PRs are merged. Not quite deployed. Once we're there, I think we can just test and close!

[dangrous]

Waiting on https://github.com/Expensify/Mobile-Expensify/pull/13289 to deploy

[dangrous]

Oh wait maybe we don't get comments on deploys in M-E? Checking in Slack, but hopefully that means we can get this re-tested and closed!

[Julesssss]

Yeah, there's no staging branch or deploy on Mobile-E. Once merged to main the next App build (including CP builds) will include the mobile changes.

[dangrous]

ah great! @IuliiaHerets are you able to retest this?

[IuliiaHerets]

@dangrous Issue is not reproduced now

screen-20250131-070911.mp4

[dangrous]

Amazing! I think we can close this - I don't believe any payment is required. If someone disagrees, ping here!