Support Expo Config Plugins for managed workflow compatibility

[budet-b]

Hello 👋,

I’m currently using this package in an Expo project, and I noticed that it does not yet provide an Expo config plugin.
Without a config plugin, the library requires manual changes in the native iOS/Android projects, which makes it incompatible with the Expo managed workflow.

Would you consider adding support for an Expo config plugin?

This would:

✅ Make the library compatible with Expo managed workflow (no need to eject).
✅ Simplify setup for developers.
✅ Ensure smoother upgrades with Expo SDKs.

Here are some references that might help:

Expo config plugin documentation: https://docs.expo.dev/guides/config-plugins/

Example implementation: https://github.com/expo/expo/tree/main/packages/expo-build-properties

Thanks again for your work on this library! 🚀

[adelbeke]

I have the same issue 🙏🏻 It would be a great asset to have it, as React Native recommends Expo, and the Expo config plugin is quite the go-to nowadays.

[felipe-saez]

Hello,

Thank you for your request. We are currently reviewing it and will keep you updated. As soon as we have any news, we’ll be in touch.

Best regards,
Felipe

[pmerlet-at-didomi]

Hello @budet-b , we just opened a PR for this feature: #158

We were able to pack and use the plugin locally in a new Expo project, but as we are not familiar with the Expo framework, feel free to have a look and add comments if needed.

Regards,

Philémon

[LivioGama]

Not sure it's related: the plugin seem to work in my Expo project but iOS does not compile.
Maybe it's because of Expo 54... It was working on our Expo 53 project, even without the plugin

ld: warning: search path '/var/run/com.apple.security.cryptexd/mnt/com.apple.MobileAsset.MetalToolchain-v17.1.324.0.WVFXbQ/Metal.xctoolchain/usr/lib/swift/iphonesimulator' not found
ld: warning: Could not find or use auto-linked framework 'UIUtilities': framework 'UIUtilities' not found
ld: warning: Could not parse or use implicit file '/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator.sdk/System/Library/Frameworks/SwiftUICore.framework/SwiftUICore.tbd': cannot link directly with 'SwiftUICore' because product being built is not an allowed client of it
Undefined symbols for architecture arm64:
  "_OBJC_CLASS_$_RCTEventEmitter", referenced from:
      full type metadata for react_native_didomi.RNDidomi in RNDidomi.o
  "_OBJC_METACLASS_$_RCTEventEmitter", referenced from:
      _OBJC_METACLASS_$_Didomi in RNDidomi.o
  "_RCTPresentedViewController", referenced from:
      closure #1 @Swift.MainActor () -> () in react_native_didomi.RNDidomi.setupUI(resolve: (Any?) -> (), reject: (Swift.String?, Swift.String?, Swift.Error?) -> ()) -> () in RNDidomi.o
      closure #1 @Swift.MainActor () -> () in react_native_didomi.RNDidomi.showPreferences(view: Swift.String?, resolve: (Any?) -> (), reject: (Swift.String?, Swift.String?, Swift.Error?) -> ()) -> () in RNDidomi.o
      closure #1 @Swift.MainActor () -> () in react_native_didomi.RNDidomi.setUserAndSetupUI(id: Swift.String, resolve: (Any?) -> (), reject: (Swift.String?, Swift.String?, Swift.Error?) -> ()) -> () in RNDidomi.o
      closure #1 @Swift.MainActor () -> () in react_native_didomi.RNDidomi.setUserWithHashAuthAndSetupUI(id: Swift.String, algorithm: Swift.String, secretId: Swift.String, digest: Swift.String, salt: Swift.String?, resolve: (Any?) -> (), reject: (Swift.String?, Swift.String?, Swift.Error?) -> ()) -> () in RNDidomi.o
      closure #1 @Swift.MainActor () -> () in react_native_didomi.RNDidomi.setUserWithHashAuthWithExpirationAndSetupUI(id: Swift.String, algorithm: Swift.String, secretId: Swift.String, digest: Swift.String, salt: Swift.String?, expiration: Swift.Double, resolve: (Any?) -> (), reject: (Swift.String?, Swift.String?, Swift.Error?) -> ()) -> () in RNDidomi.o
      closure #1 @Swift.MainActor () -> () in react_native_didomi.RNDidomi.setUserWithEncryptionAuthAndSetupUI(id: Swift.String, algorithm: Swift.String, secretId: Swift.String, initializationVector: Swift.String, resolve: (Any?) -> (), reject: (Swift.String?, Swift.String?, Swift.Error?) -> ()) -> () in RNDidomi.o
      closure #1 @Swift.MainActor () -> () in react_native_didomi.RNDidomi.setUserWithEncryptionAuthWithExpirationAndSetupUI(id: Swift.String, algorithm: Swift.String, secretId: Swift.String, initializationVector: Swift.String, expiration: Swift.Double, resolve: (Any?) -> (), reject: (Swift.String?, Swift.String?, Swift.Error?) -> ()) -> () in RNDidomi.o
      ...
  "_RCTRegisterModule", referenced from:
      _initialize_Didomi in Didomi.o
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

[pmerlet-at-didomi]

I tested with a new project using expo 54.0.10, iOS was building correctly on my side. I didn't use Expo before, so i cannot compare with previous versions. Are your XCode tools up-to-date?

[felipe-saez]

Hello @budet-b @adelbeke,

Could you please let us know if you were able to compile your projects on Expo after the updates provided by @pmerlet-at-didomi?

The Expo plugin has been available since version 2.16.0.

Thanks,

Felipe

[vbriand]

I think there is some misunderstanding here.

The purpose of an Expo config plugin is to automatically make changes to the native Android and / or iOS code.
However, unless I am missing something, Didomi only requires the aforementioned changes for the local file configuration.
In all other cases, an Expo config plugin doesn't appear to be needed.

As it stands, the config plugin is basically useless since it is not doing anything.
To become useful for the local file configuration, it would require an option to pass it the path to didomi_config.json, which would then be copied in the appropriate place in the android and ios directories.

[pmerlet-at-didomi]

Hello @vbriand , thanks for your feedback.

Providing a local didomi_config.json file is a deprecated feature and should be avoided, so it is unlikely that we will provide additional support for it.

Even if the plugin doesn't do anything atm, we can keep it in case we need native code changes in the future.