-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Android - Different behavior on tapping invoice and Reconcile cards from issue corporate cards #6539
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
Comments
Triggered auto assignment to @luacmartins ( |
I'm unable to reproduce this on dev. Both links use I don't think this is a high priority, so demoting to |
Triggered auto assignment to @trjExpensify ( |
This is pretty non-descriptive for the issue title. It might be helpful to be more specific as to what exactly is different here. It'll help with understanding the problem, as well as for if we ever need to look for this same problem again.
Yeah, this is interesting. Do you have an Android device @luacmartins, to see if you can reproduce on staging/prod? 🤔 (I'm iOS, sorry!) |
I think this describes the problem well. However, I don't know if this is happening with other links as I wasn't able to reproduce it.
No, I'm on iOS as well. Maybe @marcaaron has an android device to test this? |
Pretty sure this is happening because the Android app will try to open all of the routes listed here as app links https://developer.android.com/training/app-links I'm not sure if there's a clear way to tell the OldApp (Android) to ignore links generated inside NewApp. We can probably block entire paths - but that seems like the wrong solution since a tap outside of NewApp is probably deep linking you into OldApp for other reasons.
Agree. I can test this out, but pretty sure any routes defined in the One potential solution I can think of is to create some kind of redirect page in OldDot so NewDot links will never present the disambiguation prompt. Then update this link to something like Maybe there's a better way. Good question for |
Thanks for the explanation @marcaaron! That makes sense! Since this involves potential changes to OldDot and it's not something urgent, I'll mark this as internal and weekly. Sending this to the pool. |
Issue not reproducible during KI retests. (First week) |
This issue has not been updated in over 15 days. eroding to Monthly issue. P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do! |
Issue not reproducible during KI retests. (Second week) |
Issue not reproducible during KI retests. (Third week) Closing |
Uh oh!
There was an error while loading. Please reload this page.
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Issue was found when executing the PR #6485
Action Performed:
Expected Result:
OldDot page opens with user logged in
Actual Result:
Gives option to select to open in app or in browser when selecting send invoices. Selecting browser works as expected but selecting app opens inbox of olddot app
Workaround:
Unknown
Platform:
Where is this issue occurring?
Version Number: 1.1.17-1
Reproducible in staging?: Yes
Reproducible in production?: Yes
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:

Bug5352032_screen-20211130-111040.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause
Slack conversation:
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: