Dev: Console error on android app launch Possible Unhandled Promise Rejection Error: Not supported on Android

[kavimuru]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Action Performed:

1. Launch android app

Expected Result:

No console error

Actual Result:

Console error: Possible Unhandled Promise Rejection Error: Not supported on Android

Workaround:

unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android / native
• Android / Chrome
• iOS / native
• iOS / Safari
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: 1.2.95-0
Reproducible in staging?: Occurs in Dev
Reproducible in production?: Occurs in Dev
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

Expensify/Expensify Issue URL:
Issue reported by: @aneequeahmad
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1680735934980719

View all open jobs on GitHub

[MelvinBot]

Triggered auto assignment to @dylanexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[MelvinBot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[MelvinBot]

@dylanexpensify Eep! 4 days overdue now. Issues have feelings too...

[dylanexpensify]

reviewing today!

[dylanexpensify]

Posted here for an engineer to look into!

[MelvinBot]

Triggered auto assignment to @aldo-expensify (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[dylanexpensify]

bump @aldo-expensify just so this is on your radar my friend 😄

[dylanexpensify]

not overdue!

[aldo-expensify]

uhh, sorry @dylanexpensify I forgot about it, I'll check this today in a bit!

[aldo-expensify]

I can't reproduce this. Maybe it got fixed?
I found a mention of it here: #15130 (comment)

@dylanexpensify should we close or wait?

[aldo-expensify]

@aneequeahmad , can you check if you are still able to reproduce this issue? 🙏

[MelvinBot]

@dylanexpensify @aldo-expensify this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

[dylanexpensify]

bump @aneequeahmad, can you please confirm this is still reproducible?

[aneequeahmad]

@dylanexpensify, @aldo-expensify i'll confirm this today. Thanks for mentioning.

[aneequeahmad]

@aldo-expensify You're right this bug has has been fixed in the PR that you mentioned. Not reproducible on v1.3.4-0. We can close this issue.

cc: @dylanexpensify

[dylanexpensify]

nice one, thanks all!