Skip to content
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

matchUri is getting an error #4288

Open
1 task done
qiaoyun680 opened this issue Nov 12, 2024 · 1 comment
Open
1 task done

matchUri is getting an error #4288

qiaoyun680 opened this issue Nov 12, 2024 · 1 comment
Labels

Comments

@qiaoyun680
Copy link

qiaoyun680 commented Nov 12, 2024

Steps To Reproduce

In the AutofillParserImpl.kt class within the com.x8bit.bitwarden.data.autofill.parser package, the parseInternal method, specifically the line 97

val uri = traversalDataList.buildUriOrNull( packageName = packageName, )

does not correctly retrieve the URI. If the URI is "http://102.168.5.6:5700", the result for uri is "http://102.168.5.6", and the port number is not correctly obtained.
image

Expected Result

If the URI is "http://192.168.5.6:5700", the result for uri is "http://192.168.5.6:5700",

Actual Result

If the URI is "http://192.168.5.6:5700", the result for uri is "http://192.168.5.6", no port info

Screenshots or Videos

No response

Additional Context

No response

Build Version

2024.11.3(19432)

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

No response

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
@qiaoyun680 qiaoyun680 added the bug label Nov 12, 2024
@bitwarden-bot
Copy link

Thank you for your report! We've added this to our internal board for review.
ID: PM-14846

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants