[$1000] Desktop app is crashing

[mvtglobally]

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. App has been opened for a while,
2. Background app,
3. Bring it up to foreground using cmd+space
4. Type New..

Expected Result:

App to open

Actual Result:

App is crashed Uh-oh, something went wrong!

Workaround:

unknown

Platform:

Where is this issue occurring?

• Desktop App

Version Number: 1.1.37-0
Reproducible in staging?: Y
Reproducible in production?:
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

Expensify/Expensify Issue URL:
Issue reported by: @mallenexpensify
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1644343981504179

View all open jobs on GitHub

[MelvinBot]

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

[marcochavezf]

I wasn't able to reproduce it, but according to the slack convo seems it's still happening. I'm going to mark it as External in case an external contributor is able to reproduce it, also I'm going to change it to Weekly because seems to be an edge-case and the user can re-open the app if it crashes.

[MelvinBot]

Triggered auto assignment to @kadiealexander (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

[kadiealexander]

I'm also not able to reproduce this! I've reached out here to see if anyone is still experiencing this.

[roryabraham]

This looks to me like it might be a react-navigation issue. If it really is reproducible only on desktop but not web, it's possible that the new Electron architecture I implemented in this PR isn't playing nice with react-navigation (particularly linkingConfig/parsing URLs).

Disclaimer: The above comments are purely speculation. If we can't reproduce this I'd recommend we add it to weekly KI retests.

[kadiealexander]

@roryabraham I haven't had any further reports of people able to reproduce this. How do I add it to the KI retests?

[roryabraham]

I think we can just ask @Expensify/applauseleads to add it to the KI retests

[MelvinBot]

@kadiealexander Huh... This is 4 days overdue. Who can take care of this?

[kadiealexander]

This has been added to the KI retest list.

[mvtglobally]

We are able to reproduce it, Just FYI

[kadiealexander]

Thanks Maria!

@roryabraham should we go ahead and get this on Upwork since it's reproducible?

[roryabraham]

Yeah, let's move it to upwork.

[MelvinBot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @rushatgabhane (Exported)

[MelvinBot]

Triggered auto assignment to @AndrewGable (Exported), see https://stackoverflow.com/c/expensify/questions/7972 for more details.

[mallenexpensify]

Posted to Upwork since I was reviewing this. @kadiealexander , leaving you assigned as CM https://www.upwork.com/jobs/~011c3d7b7ee5f47ac1

[kadiealexander]

Thanks Matt! I had it on the list but customers came first today so far!

[kadiealexander]

Doubled the price!

[kadiealexander]

Doubled again 💰💰

[ctkochan22]

A similar issue with the same console error was fixed recently: #7907

Can we double check if this is still happening?

Also @mvtglobally, you mentioned that this is reproducible -- #7642 (comment) What are those reproduction steps? Are they ?

App has been opened for a while,
Background app,
Bring it up to foreground using cmd+space
Type New..

[kadiealexander]

@mvtglobally could you please confirm if this issue is still reproducible? I haven't been able to reproduce it on my end.

[mvtglobally]

Issue not reproducible during KI retests. (First week)

[ctkochan22]

Cool I think this is fixed. Whoo! Closing