Closed lanitochka17 closed 1 month ago
Triggered auto assignment to @isabelastisser (Bug
), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.
We think that this bug might be related to #Live Markdown
@isabelastisser FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors
Job added to Upwork: https://www.upwork.com/jobs/~01bc8d3436a587add7
Triggered auto assignment to Contributor-plus team member for initial proposal review - @alitoshmatov (External
)
cc @tomekzaw π
No proposals yet.
@isabelastisser, @alitoshmatov Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
@isabelastisser, @alitoshmatov Huh... This is 4 days overdue. Who can take care of this?
Still waiting for proposals.
π£ It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? πΈ
@isabelastisser, @alitoshmatov 6 days overdue. This is scarier than being forced to listen to Vogon poetry!
Waiting for proposals
@isabelastisser @alitoshmatov 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!
@isabelastisser, @alitoshmatov Whoops! This issue is 2 days overdue. Let's get this updated quick!
No proposals yet.
π£ It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? πΈ
@isabelastisser, @alitoshmatov Eep! 4 days overdue now. Issues have feelings too...
No proposals yet
@isabelastisser, @alitoshmatov Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
Still waiting for proposals.
π£ It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? πΈ
@isabelastisser, @alitoshmatov Huh... This is 4 days overdue. Who can take care of this?
no proposals yet.
@isabelastisser, @alitoshmatov 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it!
@tomekzaw might be able to help here.
Edited by proposal-police: This proposal was edited at 2024-09-03 07:48:57 UTC.
App crashes when deleting text with markdown in a sentence containing a heading on Android.
This is a react-native-live-markdown issue where markdown formatting is applied in the onTextChanged
event.
When applying formatting, there may be a race condition if we are trying to remove a span that has already been removed.
The issue is not keyboard-specific; certain keyboards may experience delays that result in accidental errors. The most straightforward way to replicate the issue is:
#a
a
, ensure only a letter selectedcut
https://github.com/user-attachments/assets/21bac680-bbd7-43d4-87d3-78baa454a769
To avoid the race condition, move applyMarkdownFormatting
from onTextChanged
to afterTextChanged
after the text has changed.
Change:
To
@Override
public void onTextChanged(CharSequence s, int start, int before, int count) {
if (mShouldSkip) {
return;
}
// Set the flag to indicate text is being changed
mShouldSkip = true;
}
@Override
public void afterTextChanged(Editable editable) {
if (!mShouldSkip) {
return;
}
if (editable instanceof SpannableStringBuilder) {
mMarkdownUtils.applyMarkdownFormatting((SpannableStringBuilder) editable);
}
// Reset the flag after formatting is applied
mShouldSkip = false;
}
https://github.com/user-attachments/assets/27248373-b430-4c30-bbf0-63b9ac623004
RN Markdown Branch for this solution
N/A
@wildan-m Thank you for your proposal, I think your RCA is correct and we can go with you solution
C+ reviewed π π π
Triggered auto assignment to @neil-marcellini, see https://stackoverflow.com/c/expensify/questions/7972 for more details.
@neil-marcellini @isabelastisser @alitoshmatov this issue is now 4 weeks old, please consider:
Thanks!
We have chosen a proposal and are waiting for @neil-marcellini's review.
@wildan-m Thank you for your proposal, I think your RCA is correct and we can go with you solution
C+ reviewed π π π
Wow great job! Hiring
π£ @alitoshmatov π An offer has been automatically sent to your Upwork account for the Reviewer role π Thanks for contributing to the Expensify app!
π£ @wildan-m π An offer has been automatically sent to your Upwork account for the Contributor role π Thanks for contributing to the Expensify app!
Offer link Upwork job Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review π§βπ» Keep in mind: Code of Conduct | Contributing π
@alitoshmatov The upstream PR is ready. https://github.com/Expensify/react-native-live-markdown/pull/469
@wildan-m, @neil-marcellini, @isabelastisser, @alitoshmatov Eep! 4 days overdue now. Issues have feelings too...
@alitoshmatov @wildan-m, can you please provide an update? Thanks!
@isabelastisser discussing optimal approach to avoid duplicate calls in upstream. https://github.com/Expensify/react-native-live-markdown/pull/469#issuecomment-2335002872
https://github.com/Expensify/react-native-live-markdown/pull/469 has just been merged
Thank you, @tomekzaw!
@alitoshmatov @neil-marcellini Should we simply update the version in the E/App to apply it? I see that the live markdown version in E/App is not the latest. Are there specific steps to follow?
There's already a PR that bumps react-native-live-markdown here: https://github.com/Expensify/App/pull/48626
@tomekzaw can we bump the version to 0.1.140 there or we should temporarily create patch until that PR closed?
Let's avoid patches and bump directly to latest if possible
@wildan-m, @neil-marcellini, @isabelastisser, @alitoshmatov 6 days overdue. This is scarier than being forced to listen to Vogon poetry!
Should be fixed with https://github.com/Expensify/App/pull/48626
Waiting for react-native-live-markdown
bump on https://github.com/Expensify/App/pull/48626
Issue not reproducible during KI retests. (First week)
@wildan-m, @neil-marcellini, @isabelastisser, @alitoshmatov Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
Not overdue, The fix PR passed the test and is now live in production https://github.com/Expensify/App/pull/48626#issuecomment-2353604788.
If you havenβt already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 9.0.17-0 Reproducible in staging?: Y Reproducible in production?: Y If this was caught during regression testing, add the test name, ID and link from TestRail: N/A Email or phone of affected tester (no customers): applausetester+kh050806@applause.expensifail.com Issue reported by: Applause - Internal Team
Action Performed:
Precondition:
Expected Result:
App will not crash
Actual Result:
App crashes This issue is only reproducible with Samsung keyboard and not Gboard
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
https://github.com/user-attachments/assets/b0bc1b8b-a385-4021-a81a-38a074fb0cb6
logs (2).txt
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @isabelastisser