[Waiting on Checklist] [$125] [Dev] Console Warning: No native ExponentConstants module found

[m-natarajan]

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:
Reproducible in staging?: DEV
Reproducible in production?: DEV
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?:
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: @eVoloshchak
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1729174865370699

Action Performed:

1. Launch the iOS app
2. Observe the warning

Expected Result:

No warning is displayed

Actual Result:

Warning is displayed

Workaround:

unknown

Platforms:

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

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence


Screen.Recording.2024-10-17.at.16.20.46.mov

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021849240595196131510
• Upwork Job ID: 1849240595196131510
• Last Price Increase: 2024-10-24

Issue Owner

Current Issue Owner: @twisterdotcom

[melvin-bot]

Triggered auto assignment to @twisterdotcom (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.

[MelvinBot]

This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

[bernhardoj]

Proposal

Please re-state the problem that we are trying to solve in this issue.

A "No native ExponentConstants module found" warning is shown.

What is the root cause of that problem?

We don't link the expo-const module, so it's not found.

App/package.json

Lines 354 to 357 in c3d33fc

	"expo": {
	"autolinking": {
	"exclude": [
	"expo-constants",

expo-const is being used in expo-asset module and it's found in PlatformUtils file. However, all the properties that is being used inside the file doesn't exist even if we installed the expo-const.
https://github.com/expo/expo/blob/d576550145ede25dec3f6636bf260f7b05bec7a6/packages/expo-asset/src/PlatformUtils.ts#L32-L39

So, it's no different whether we include expo-const module or not. Here is the available properites from expo-const.

{"addListener": [Function addListener], "debugMode": true, "deviceName": "iPhone 15 Plus", "emit": [Function emit], "executionEnvironment": "bare", "getWebViewUserAgentAsync": [Function getWebViewUserAgentAsync], "isHeadless": false, "listenerCount": [Function listenerCount], "manifest": {"description": "New Expensify is the next generation of Expensify: a reimagination of payments based atop a foundation of chat.", "name": "new.expensify", "platforms": ["ios", "android", "web"], "sdkVersion": "51.0.0", "slug": "new.expensify", "version": "9.0.50-7"}, "platform": {"ios": {"buildNumber": "9.0.50.7"}}, "removeAllListeners": [Function removeAllListeners], "removeListener": [Function removeListener], "removeSubscription": [Function removeSubscription], "sessionId": "715902EE-F726-43EA-B204-6797A7E27318", "statusBarHeight": 54, "systemFonts": [listOfFontsTooLong]}

What changes do you think we should make in order to solve the problem?

We can suppress the warning. One way to do it is by suppressing it here.

App/src/App.tsx

Lines 48 to 53 in c3d33fc

	LogBox.ignoreLogs([
	// Basically it means that if the app goes in the background and back to foreground on Android,
	// the timer is lost. Currently Expensify is using a 30 minutes interval to refresh personal details.
	// More details here: https://git.io/JJYeb
	'Setting a timer for a long period of time',
	]);

'No native ExponentConstants module found',

OR

We can link the expo-const by remove it from the auto-link exclude list.

App/package.json

Lines 354 to 357 in c3d33fc

	"expo": {
	"autolinking": {
	"exclude": [
	"expo-constants",

[melvin-bot]

@twisterdotcom Whoops! This issue is 2 days overdue. Let's get this updated quick!

[melvin-bot]

@twisterdotcom Huh... This is 4 days overdue. Who can take care of this?

[twisterdotcom]

Seems straightforward right? I haven't recreated this, so will lean on C+ too for this dev specific issue.

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @mollfpr (External)

[melvin-bot]

Upwork job price has been updated to $125

[twisterdotcom]

Downgrading as this isn't customer facing.

[mollfpr]

I'm assuming we exclude the expo-constants to reduce the binary size. I think we can suppress the warning like it proposed from @bernhardoj.

🎀 👀 🎀 C+ reviewed!

[melvin-bot]

Triggered auto assignment to @blimpich, see https://stackoverflow.com/c/expensify/questions/7972 for more details.

[blimpich]

Proposal seems good, but question: why is this only getting reported and fixed now? The PR that added that code was merged 10 months ago. Did we just live with warning until @eVoloshchak decided to report it?

[bernhardoj]

PR is ready
cc: @mollfpr

Did we just live with warning until @eVoloshchak decided to report it?

I think yes. There has been so much warning on the app that I think people keep ignoring them 😅

[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 9.0.57-10 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [NO QA] Ignore expo const warning #51628

If no regressions arise, payment will be issued on 2024-11-13. 🎊

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

• @mollfpr requires payment through NewDot Manual Requests
• @bernhardoj requires payment through NewDot Manual Requests
• @eVoloshchak requires payment through NewDot Manual Requests

[melvin-bot]

@mollfpr @twisterdotcom The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

[melvin-bot]

Payment Summary

Upwork Job

• Reviewer: @mollfpr owed $125 via NewDot
• Reviewer: @bernhardoj owed $125 via NewDot

BugZero Checklist (@twisterdotcom)

• I have verified the correct assignees and roles are listed above and updated the neccesary manual offers
• I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants/1849240595196131510/hired)
• I have paid out the Upwork contracts or cancelled the ones that are incorrect
• I have verified the payment summary above is correct

[bernhardoj]

Requested in ND.

[melvin-bot]

@twisterdotcom @blimpich @mollfpr @bernhardoj this issue is now 4 weeks old, please consider:

• Finding a contributor to fix the bug
• Closing the issue if BZ has been unable to add the issue to a VIP or Wave project
• If you have any questions, don't hesitate to start a discussion in #expensify-open-source

Thanks!

[twisterdotcom]

It is done Melv. Just waiting on @mollfpr to do the checklist, although... looking again, I don't think we need one just for this console error. Going to close.

[JmillsExpensify]

$125 approved for @bernhardoj

[JmillsExpensify]

Actually wait, going to confirm the amounts with @twisterdotcom via DM.

[JmillsExpensify]

Payment summary is updated and so is my approval amount.

[mollfpr]

Sorry for the delay! Yes, we don't need the checklist here.

[garrettmknight]

$125 approved for @mollfpr