Ramanpreet Nara 169180100c Temp: Always report debug info on module not found error ...

Summary:
The TurboModule interop layer causes a surge in "module not found" exceptions: T154044825.

After D45102812, this exception **should** have included debug info. But, it didn't.

## Problems
So, there are two problems:
1. No debug logs are getting printed.
2. In the TurboModule interop test group, global.RN$TurboInterop is false **for some reason.** This is **very** strange.

## Changes
1. **Always** print the debug logs.
2. Add more flag-related debug information to the "module not found" debug logs. This will help us validate whether global.RN$TurboInterop is truely false.

## Concerns
> **Always** print the debug logs on Android.

**Question:** Won't this be really expensive?

This shouldn't be too expensive: There are about ~50 native module requires in Fb4a. So: (1) the exception message shouldn't grow to an unreasonable size, (2) we'll only use enough memory to store ~50 strings in the JS VM.

Changelog: [Internal]

Reviewed By: fkgozali

Differential Revision: D46195117

fbshipit-source-id: 8215c7339d16a1adc063b674805063865d1f7ab6

2023-05-25 14:58:11 -07:00

..

samples

Add error reporting examples to rn-tester turbo modules (#36729)

2023-04-03 08:34:59 -07:00

RCTExport.d.ts

…

RCTExport.js

…

TurboModuleRegistry.d.ts

…

TurboModuleRegistry.js

Temp: Always report debug info on module not found error

2023-05-25 14:58:11 -07:00