Support for new architecture and bridgeless

[brentvatne]

Checklist

• I have looked into the Readme, Examples, and FAQ and have not found a suitable solution or answer.
• I have looked into the API documentation and have not found a suitable solution or answer.
• I have searched the issues and have not found a suitable solution or answer.
• I have searched the Auth0 Community forums and have not found a suitable solution or answer.
• I agree to the terms within the Auth0 Code of Conduct.

Describe the problem you'd like to have solved

Hi there! I'm working on supporting the roll out of the new architecture + bridgeless with Expo and Meta, and as part of that we identified which are the most popular native libraries on EAS Build to help prioritize which libraries to investigate. react-native-auth0 came up on that list. See the list on Google Sheets (request edit access if you'd like to update the status of react-native-auth0 after testing, or if you prefer to report back here on this issue it's fine too).

We want to start recommending folks try out the new architecture in the next release, react-native 0.74 / Expo SDK 51. Ideally we can get the ecosystem ready to switch over to the new architecture within the next few releases. So, we'll have from now until 0.74 release (before May) to give meta feedback on anything that might not be working as expected with the new arch/bridgeless enabled.

Folks at Meta would really appreciate it if you could test your libraries against the latest release and report any issues that you find. This new version enables an interop layer by default, so hopefully many things will just work, but the more off of the beaten path of a simple module / view that a library goes the more likely it is to encounter possible issues ;) The following gist includes a step by step process for how to test your library and report issues: https://gist.github.com/cipolleschi/82b7a9561b8861330efabbd3eb08c6f5.

Describe the ideal solution

react-native-auth0 works correctly with the new architecture enabled or disabled, and with bridgeless enabled or disabled, using React Native 0.74. More info in: https://gist.github.com/cipolleschi/82b7a9561b8861330efabbd3eb08c6f5.

Alternatives and current workarounds

No response

Additional context

No response

[chriszs]

Still experiencing #804, which was won't-fixed because New Arch was in beta. Believe New Arch will be the default in the React Native release after this one.

[brentvatne]

@chriszs - that's the plan! for any maintainers here, please refer to reactwg/react-native-new-architecture#167 for more context

[kibiz0r]

@brentvatne If I grok that spreadsheet correctly, Auth0 is one of only 10 unique maintainers among the top 400 packages that hasn't started on new arch support?

@poovamraj Can we get this prioritized?

[chriszs]

As a test, I upgraded the example app to the latest 0.74 RC using the Test Your Library guide, enabled new arch (newArchEnabled=true) and then deleted the codegenConfig config key from package.json per the Interop Layer test instructions (since I didn't see TurboModule specs). That is, all I did was this:

  },
-  "codegenConfig": {
-    "name": "RNAuth0Spec",
-    "type": "modules",
-    "jsSrcsDir": "src"
-  },
  "husky": {

The example appears to work correctly on Android using 0.74 and new arch, though I haven't thoroughly tested it and it's possible I'm missing something.

This obviously isn't a full conversion to a TurboModule, it doesn't ensure compatibility with new arch on lower versions of React Native (unless the Interop Layer is explicitly enabled) and supposedly some day the Interop Layer will go away, but it does appear to work as a first step.

I wonder if a two-step approach would be to delete the codegen config, ensure the interop layer works, and then do a full conversion at a later date.

[brentvatne]

@chriszs - I think that is a good approach! we're recommending releasing interop layer compat first, then migrating when you have time