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

[NoQA] feat: enable bridgeless #48160

Merged

Conversation

WoLewicki
Copy link
Contributor

@WoLewicki WoLewicki commented Aug 28, 2024

Details

PR enabling bridgeless mode in the App. This PR can affects the App as a whole, so should require full regression testing.

PRs for introduced patches:

Fixed Issues

$ #48163
PROPOSAL:

Tests

  • Verify that no errors appear in the JS console

Offline tests

QA Steps

  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
    • MacOS: Desktop
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
      • If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
MacOS: Desktop

This comment has been minimized.

@WoLewicki WoLewicki marked this pull request as ready for review October 4, 2024 13:02
@WoLewicki WoLewicki requested a review from a team as a code owner October 4, 2024 13:02
@melvin-bot melvin-bot bot requested review from fedirjh and roryabraham and removed request for a team October 4, 2024 13:02
Copy link

melvin-bot bot commented Oct 4, 2024

@fedirjh @roryabraham One of you needs to copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

Copy link
Contributor

github-actions bot commented Oct 4, 2024

@roryabraham
Copy link
Contributor

roryabraham commented Oct 4, 2024

react-native-keyboard-controller: The code is already there from 1.13.0 so it just needs a bump and we can remove the patch then.

So let's do this before we merge this PR, rather than creating a patch that has to be cleaned up after

@roryabraham
Copy link
Contributor

Created #50253

@roryabraham
Copy link
Contributor

react-native-firebase: We have a dirty workaround and Meta is already working on a better solution after I reported the problem to them. We won't make a PR with it since it's better to wait for it to be fixed in core.

Can you link to an upstream issue plz? 🙇🏼

@WoLewicki
Copy link
Contributor Author

Can you link to an upstream issue plz? 🙇🏼

Done.

@fedirjh
Copy link
Contributor

fedirjh commented Oct 7, 2024

@WoLewicki On iOS native, I cannot change the profile avatar or select an attachment in composer

CleanShot.2024-10-07.at.15.12.39.mp4
CleanShot.2024-10-07.at.14.56.32.mp4

When creating a distance request, the composer is shinking :

Screenshot 2024-10-07 at 3 21 56 PM
CleanShot.2024-10-07.at.15.09.10.mp4

I got the warning several times when I created a new expenses

Screenshot 2024-10-07 at 3 04 38 PM

@fedirjh
Copy link
Contributor

fedirjh commented Oct 7, 2024

@WoLewicki On android, when sending a new message, the app crashes with this error:

Screenshot 2024-10-07 at 4 10 12 PM

@fedirjh
Copy link
Contributor

fedirjh commented Oct 7, 2024

On Android: When you try to create a new expense, the App crashes with this error, there were other warnings errors as well :

Screenshot 2024-10-07 at 4 14 42 PM Screenshot 2024-10-07 at 4 13 58 PM Screenshot 2024-10-07 at 4 14 07 PM Screenshot 2024-10-07 at 4 14 54 PM Screenshot 2024-10-07 at 4 15 01 PM

@fedirjh
Copy link
Contributor

fedirjh commented Oct 7, 2024

On Android: When you create a scan expense, the App crashes with these errors:

Screenshot 2024-10-07 at 4 19 38 PM Screenshot 2024-10-07 at 4 19 48 PM Screenshot 2024-10-07 at 4 20 04 PM

@fedirjh
Copy link
Contributor

fedirjh commented Oct 7, 2024

When you navigate to troubleshoot page, the app will crash with this error :

Screenshot 2024-10-07 at 4 35 10 PM

@WoLewicki
Copy link
Contributor Author

I wouldn't expect enormous gains, but some at least due to Static View Configs.

@mountiny
Copy link
Contributor

I can run it now. Running here https://github.com/Expensify/App/actions/runs/11438433039

@WoLewicki
Copy link
Contributor Author

Idk why but it seems to have failed @mountiny. I just merged the newest main, maybe it will work now?

@mountiny
Copy link
Contributor

@hannojg
Copy link
Contributor

hannojg commented Oct 22, 2024

Hm seems like the action to run the e2e tests for a PR is broken. We'll take a look!

@WoLewicki
Copy link
Contributor Author

I merged newest main, is it ready now?

@kirillzyusko
Copy link
Contributor

I merged newest main, is it ready now?

@WoLewicki yes, tests should pass now (well, apk-manipulation stages shouldn't fail). However I see that your PR contains "merge" commits. In #48251 I re-worked pipeline, where baseline is taken as last merge commit (and at this point of time I'm not sure which merge commit will be taken in your PR - will it compare with main or with one of merge commits in PR). I think it's just better to run e2e pipeline and check that 👀

Additionally (just want to warn in advance) I think tests will not pass, because they are currently broken on main as well (unfortunately). I'm currently working on this PR: #51248
It works, but it's draft changes and I want to improve some aspects 🙂

If your PR can wait few days, then it would be simply amazing. Alternatively I can run tests locally to check performance benefits (since e2e pipeline is not fully working at the moment).

@WoLewicki
Copy link
Contributor Author

I think having any feedback from this PR regarding performance is valuable, so even running it locally could be enough for now.

If your PR can wait few days, then it would be simply amazing

I'd merge this PR nonetheless since it is the way forward either way and it would help me with pushing RN 0.76 and expo update. But I don't have a strong opinion on that tbh.

@kirillzyusko
Copy link
Contributor

Okay @WoLewicki , give me ~1.5hr and I'll post my results here 😊

@kirillzyusko
Copy link
Contributor

kirillzyusko commented Oct 22, 2024

Okay, I can not run tests locally, because I'm getting:

2024-10-22 17:53:35.734  3133-3375  AndroidRuntime          com.expensify.chat.e2edelta          E  FATAL EXCEPTION: mqt_native_modules (Ask Gemini)
                                                                                                    Process: com.expensify.chat.e2edelta, PID: 3133
                                                                                                    com.facebook.react.common.JavascriptException: Error: Exception in HostFunction: Could not enqueue microtask because they are disabled in this runtime, js engine: hermes, stack:
                                                                                                    setImmediate@1:527723
                                                                                                    setDriver@1:1660584
                                                                                                    LocalForage@1:1659118
                                                                                                    anonymous@1:1640327
                                                                                                    s@1:1635136
                                                                                                    e@1:1634879
                                                                                                    anonymous@1:1634781
                                                                                                    anonymous@1:1634629
                                                                                                    loadModuleImplementation@1:194267
                                                                                                    guardedLoadModule@1:193495
                                                                                                    metroRequire@1:192777
                                                                                                    anonymous@1:1634119
                                                                                                    loadModuleImplementation@1:194267
                                                                                                    guardedLoadModule@1:193495
                                                                                                    metroRequire@1:192777
                                                                                                    anonymous@1:1606115
                                                                                                    loadModuleImplementation@1:194267
                                                                                                    guardedLoadModule@1:193495
                                                                                                    metroRequire@1:192777
                                                                                                    anonymous@1:1603178
                                                                                                    loadModuleImplementation@1:194267
                                                                                                    guardedLoadModule@1:193495
                                                                                                    metroRequire@1:192777
                                                                                                    anonymous@1:1402528
                                                                                                    loadModuleImplementation@1:194267
                                                                                                    guardedLoadModule@1:193495
                                                                                                    metroRequire@1:192777
                                                                                                    anonymous@1:206788
                                                                                                    loadModuleImplementation@1:194267
                                                                                                    guardedLoadModule@1:193495
                                                                                                    metroRequire@1:192777
                                                                                                    anonymous@1:206603
                                                                                                    loadModuleImplementation@1:194267
                                                                                                    guardedLoadModule@1:193495
                                                                                                    metroRequire@1:192777
                                                                                                    anonymous@1:204066
                                                                                                    loadModuleImplementation@1:194267
                                                                                                    guardedLoadModule@1:193452
                                                                                                    metroRequire@1:192777
                                                                                                    global@1:191704
                                                                                                    
                                                                                                    	at com.facebook.react.modules.core.ExceptionsManagerModule.reportException(SourceFile:76)
                                                                                                    	at com.facebook.jni.NativeRunnable.run(Native Method)
                                                                                                    	at android.os.Handler.handleCallback(Handler.java:959)
                                                                                                    	at android.os.Handler.dispatchMessage(Handler.java:100)
                                                                                                    	at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(SourceFile:1)
                                                                                                    	at android.os.Looper.loopOnce(Looper.java:232)
                                                                                                    	at android.os.Looper.loop(Looper.java:317)
                                                                                                    	at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(SourceFile:38)
                                                                                                    	at java.lang.Thread.run(Thread.java:1012)

I don't know why it happens 🤷‍♂️ I think we can proceed with merging and in a meantime I will try to fix e2e pipeline to make sure we can run tests independently to a local environment 👀

For transparency: builds from main also fail with the same error. I think it's a problem with my local setup 🤔

@mountiny mountiny changed the title feat: enable bridgeless [NoQA] feat: enable bridgeless Oct 23, 2024
@kirillzyusko
Copy link
Contributor

After merging these 3 PRs we can run test against the PR:

Highly desirable to merge #51182 as well, but it can be optional

Copy link
Contributor

@mountiny mountiny left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lets give this one a go

@mountiny mountiny merged commit 3ddc1dd into Expensify:main Oct 23, 2024
10 checks passed
@OSBotify
Copy link
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

Copy link
Contributor

🚀 Deployed to staging by https://github.com/mountiny in version: 9.0.54-0 🚀

platform result
🤖 android 🤖 success ✅
🖥 desktop 🖥 success ✅
🍎 iOS 🍎 success ✅
🕸 web 🕸 success ✅

Copy link
Contributor

🚀 Deployed to production by https://github.com/Beamanator in version: 9.0.54-11 🚀

platform result
🤖 android 🤖 success ✅
🖥 desktop 🖥 failure ❌
🍎 iOS 🍎 failure ❌
🕸 web 🕸 success ✅
🤖🔄 android HybridApp 🤖🔄 skipped 🚫
🍎🔄 iOS HybridApp 🍎🔄 skipped 🚫

Copy link
Contributor

🚀 Deployed to production by https://github.com/Beamanator in version: 9.0.54-11 🚀

platform result
🤖 android 🤖 success ✅
🖥 desktop 🖥 success ✅
🍎 iOS 🍎 failure ❌
🕸 web 🕸 success ✅
🤖🔄 android HybridApp 🤖🔄 skipped 🚫
🍎🔄 iOS HybridApp 🍎🔄 skipped 🚫

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

Successfully merging this pull request may close these issues.

8 participants