[HOLD for payment 2023-08-16] [$1000] Android emulator mWeb stuck at splash screen

[Julesssss]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Action Performed:

• Build newDot web an unknown amount of times...
• Open NewDot mWeb via an Android emulator Chrome app

Expected Result:

• mWeb should run as expected

Actual Result:

• mWeb app is stuck at the splash screen

Workaround:

• You can use a secondary NGROK to test dev mWeb on a physical Android device

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android / Chrome

Version Number: Many
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1688665141544519

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01c9b138754f430c1c
• Upwork Job ID: 1677231785028624384
• Last Price Increase: 2023-07-31
• Automatic offers:
• jjcoffee | Contributor | 25898337

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~01c9b138754f430c1c

[melvin-bot]

Triggered auto assignment to @slafortune (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[melvin-bot]

Triggered auto assignment to Contributor Plus for review of internal employee PR - @mananjadhav (Internal)

[mananjadhav]

Ohh I thought it was my high traffic and low connectivity as I was travelling. After 3-4 attempts the mWeb won't load. It worked fine for me on one of my physical device, but never works on Emulator.

If I wipe data on the emulator, and reload then it works fine. Just clearing cache on Chrome didn't help either.

[slafortune]

Is this a bug for External contributors @Julesssss ? or is this something you are looking into?

[Julesssss]

@slafortune we can keep this internal 👍

[Julesssss]

I think it's unlikely a code fix will resolve this issue, but @mananjadhav lets keep you assigned for now just in case

[melvin-bot]

@mananjadhav, @Julesssss, @slafortune Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[melvin-bot]

@mananjadhav @Julesssss @slafortune this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

[Julesssss]

Hmm, there is another issue that should resolve this one, but I can't find any link to it now 😕

[Julesssss]

The other issue didn't end up resolving this.

[Julesssss]

I'll keep it for myself and look into solutions when I have a moment.

[mananjadhav]

do we have any insights on what's wrong? I don't see any logs in the emulator, no errors messages too?

[jjcoffee]

@mananjadhav Hmm that sounds like it's probably a separate issue from what's described here and in the source Slack thread (where people report updating Chrome fixing the issue). Just to be sure are you able to check what Chrome version you have on the emulator, and also if there are any console errors (specifically key.split(...).at is not a function)?

[mananjadhav]

Naah I don't see this error being logged, but you're right this could be different than mine.

@Julesssss, overall I think @jjcoffee's proposal looks good.

🎀 👀 🎀 C+ Reviewed.

[melvin-bot]

Current assignee @Julesssss is eligible for the choreEngineerContributorManagement assigner, not assigning anyone new.

[Julesssss]

Hmm, I'm a bit skeptical about the solution in that case. Let's try it though and see if a new bug is revealed in it's place.

[melvin-bot]

📣 @mananjadhav Please request via NewDot manual requests for the Reviewer role ($1000)

[melvin-bot]

📣 @jjcoffee 🎉 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 📖

[jjcoffee]

PR coming today!

[Julesssss]

FYI I'm going OOO tomorrow so we'll take that into account when calculating the quick turnaround bonus

[jjcoffee]

PR ready for review! cc @mananjadhav

[melvin-bot]

Based on my calculations, the pull request did not get merged within 3 working days of assignment. Please, check out my computations here:

• when @jjcoffee got assigned: 2023-08-02 08:13:40 Z
• when the PR got merged: 2023-08-07 10:04:49 UTC
• days elapsed: 3

On to the next one 🚀

[Julesssss]

^ The bonus should apply, I was ooo for two working days.

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.51-2 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [NO-QA] Add core-js polyfill for pdfjs to support older Chrome & Safari versions #24068

If no regressions arise, payment will be issued on 2023-08-16. 🎊

After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.

• External issue reporter
• Contributor that fixed the issue
• Contributor+ that helped on the issue and/or PR

For reference, here are some details about the assignees on this issue:

• @mananjadhav does not require payment (Eligable for Manual Requests)
• @jjcoffee requires payment offer (Contributor)

As a reminder, here are the bonuses/penalties that should be applied for any External issue:

• Merged PR within 3 business days of assignment - 50% bonus
• Merged PR more than 9 business days after assignment - 50% penalty

[mananjadhav]

In terms of checklist, I don't think we have any offending PR. Neither do we need any regression steps as it is browser compatibility issue.

[Julesssss]

Yeah lets skip the checklist here, it was a dev only issue.

[mananjadhav]

@slafortune Can you post the payment summary here for the payout?

[slafortune]

External issue reporter - no payment, internal report
Contributor that fixed the issue - @jjcoffee $1500 - PD
Contributor+ that helped on the issue and/or PR - @mananjadhav $1500, requested via NewDot manual requests

Speed bonus should apply, solution and pr was presented within a day.

[JmillsExpensify]

Reviewed the details for @mananjadhav. $1,500 is approved for payment in NewDot based on the summary above.