Going from Flutter PnP -> Flutter SFA produces different keys

[maseh]

We are currently using flutter pnp but need to switch to sfa.

For a single user, with the same verifier and verifierId, we get a different key on the sfa sdk than we do from the pnp sdk. I noticed on other sdks there is a property “enableOneKey” which allows the key to be the same across both sdks for the same user, I dont see this option on the flutter sdk.

Also, the sdk has futures that might not complete on ios, is this intentional?

  @override
  void initState() {
    super.initState();
    initSdk();
  }

  Future<void> initSdk() async {
    if (Platform.isAndroid) {
      init().then((value) => initialize());
    } else if (Platform.isIOS) {
      init();
      initialize();
    } else {}
  }

To reproduce, just use the flutter pnp example code, create a user, and then use the flutter sfa example code with the same user. It should produce two separate keys.

Using Core Kit SFA Flutter SDK | Documentation | Web3Auth

[vjgee]

@maseh Thanks for reaching out.

Your request has been forwarded to our Dev team and we will get back with further updates.

[pepper]

@maseh

enableOneKey

Hi @maseh thanks for asking the question.
This issue is expected to be updated within 1-2 business days and
we’ll let you know as soon as it is completed.

[maseh]

Thanks guys, I appreciate the heads up

[maseh]

Hey guys, any update on this?

[pepper]

We’ve checked the code internally for this issue,
and found out that there is a difference in the package dependency associated with mobile native. Which means SFA mobile SDKS are using the different implementation with SFA web SDK.
So we are sorry to say that it’s not feasible to implement this in time.
We’ll add this to our future roadmap and update it in the future.

[maseh]

That’s unfortunate. This should be made more clear on your docs.