-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[$250] Onfido terms fonts in the verify identity page are not legit (Get Onfido to use our fonts) #44570
Comments
Triggered auto assignment to @JmillsExpensify ( |
@JmillsExpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Opening up to the community. |
Job added to Upwork: https://www.upwork.com/jobs/~0162040e800bb2d883 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @sobitneupane ( |
Waiting for proposal |
I am Michał from Callstack - expert contributor group. I’d like to work on this job. Can you provide some more info on expected result? How should it look like? At the moment we're providing set of styles in order to achieve this custom Onfido look so there is room to change some things App/src/components/Onfido/BaseOnfidoWeb.tsx Lines 25 to 66 in 987c965
|
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Ok, I'm looking for a cause for this weird look. We're passing custom fontStyles so in theory it should be working but for some reason it isn't. |
What I've found so far is that few months ago we've upgraded to v14 of Onfido from v13 and this seems to cause the trouble. I've reverted back to v13 locally to confirm that and passed font seems to be working fine. ![]() Currently we're on version 14.15.0. I've tried upgrading it to the latest one (14.30.0) but the issue persists. I'm beginning to think that this is an issue on the sdk side and we can't really do anything about it apart from changing it to one of the fonts they officially support that will resemble our own one (list on the bottom). I will look into a bit more and try to find a workaround for this. |
@JmillsExpensify @sobitneupane this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
ProposalPlease re-state the problem that we are trying to solve in this issue.Fonts are looking suspicious and do not match rest of the app on Onfido screen What is the root cause of that problem?There weren't any changes on our end when it comes to fonts used in Onfido iframe so after investigating that everything looks fine on our end I've started looking for the cause on the package side. When onfido-sdk-ui package was upgraded to v14 the fonts stopped working. I've confirmed that by downgrading to v13 (see screenshot). After lowering version it simply started working again. ![]() I'm suspecting that this is something that is broken on the Onfido package side so definitve root cause isn't known. What happens is that the font we're providing is not being detected so it defaults to some serif font causing this look reported in the issue. Why it is not being picked up - I don't know. There is no What changes do you think we should make in order to solve the problem?Custom font provided by us via customUI prop when initializing Onfido is not being picked up by iframe so font defaults to some serif one. We can comment out (and leave a comment why is that) ![]() What alternative solutions did you explore? (Optional)I've tried upgrading package from 14.15.0 (current version in app) to latest one (14.30.0) but the issue persists. There is also an option to change the font to one of the google fonts they support. I've tried one of them and it worked. This is the list of them |
@MrMuzyk I believe this is the best approach. First, let's inform them about the issue. If they respond quickly and decide to fix it, we can wait. |
Payment Summary:
No regression test required here. |
$250 approved for @sobitneupane based on this summary. |
Do we have any idea on when they would have a fix for this on their side? Just wondering if we have plans to follow up and undo our hotfix here when the time is right. Thanks! |
Just looking back through my emails and found this actually from about a month ago - they cc'd contributors@ so it hit a filter in my inbox, apologies:
I guess I could send them the names and font files and we could see if they can add them? |
The problem would be that they are our own custom fonts - I'm not sure if they can host on their side or not. Spotnana does this for us for example though. Perhaps you can reach out and ask what the best path forward is for us given that we have custom fonts we want to use? |
I have asked. |
|
Just reopening for me to track. @shawnborton can you point me to the font files and I'll share them? |
Not overdue, just reooened. |
I would just tell them that we use custom .woff files for web and .otf files for the native apps and see what they say? Give that we're open source, you could show them this: https://github.com/Expensify/App/tree/main/assets/fonts |
Will leave this until @shawnborton gets back, but my take on this is that we probably don't care about paying $10k, or even negotiating to get our fonts used here when there are likely fonts they have available that are close enough available in google fonts: https://fonts.google.com/. I'd say we should:
|
Going on parental leave and gotta hand this off. It's not clear to me whether we'll need internal engineering help so not going to reassign for now |
@twisterdotcom I think the path you laid out above sounds great to me. |
Okay, they're gonna allow custom fonts again next year!
I asked them to just let me know when and we can create an issue then. |
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: 9.0.2.4
Reproducible in staging?: y
Reproducible in production?: y
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
Expensify/Expensify Issue URL:
Issue reported by: @twisterdotcom
Slack conversation:
https://expensify.slack.com/archives/C049HHMV9SM/p1719491934827009
Action Performed:
Expected Result:
The terms page should be easily legible
Actual Result:
The fonts and colours are difficult to read
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @twisterdotcomThe text was updated successfully, but these errors were encountered: