Skip to content

Proof of Concept Insights - lockdown() options #3

@bentobox19

Description

@bentobox19

PoC

https://github.com/LavaMoat/docs/blob/main/react-native-and-ses-lockdown.md

Discussion

The SES function lockdown()is called with the following option:

lockdown({consoleTaming: 'unsafe'});

This option was added after the following report:

This line is (silently, without logs, nor anything) breaking my mobile app:
globalThis.console = /** @type {Console} */consoleRecord.console;

From Agoric the following advice

You might try the lockdown option consoleTaming: "unsafe"
It will be interesting if that gets you past the issue, though it is unsafe as described on the tin.
The purpose of the line is to replace the initial realm’s console with one that can reveal stack traces for any error that gets logged to it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions