Internal constructor in BankIdLauncherCustomAppCallbackContext #428
Replies: 3 comments
-
Good catch. We usually try to expose as little as possible, but I think we should make this constructor public. Will fix. |
Beta Was this translation helpful? Give feedback.
-
Until a public constructor is available we're using the following workaround. ConstructorInfo info = typeof(BankIdLauncherCustomAppCallbackContext).GetTypeInfo().DeclaredConstructors.First();
if (info.Invoke(new object[] { device, request }) is BankIdLauncherCustomAppCallbackContext customAppCallbackContext)
{
var customAppCallback = await GetRelevantCustomAppCallbackAsync(customAppCallbackContext, customAppCallbacks);
if (customAppCallback != null)
{
return await customAppCallback.GetCustomAppReturnUrl(customAppCallbackContext);
}
} |
Beta Was this translation helpful? Give feedback.
-
@Max-Eriksson We have made this public now (https://github.com/ActiveLogin/ActiveLogin.Authentication/pull/434/files#diff-3e365192149746040d1f6b9e9641bb45031536d7505c194e8d8d47eb9f439e39). It's part of the 8.0.0-beta-1 release available on Nuget. |
Beta Was this translation helpful? Give feedback.
-
To support native apps we're using the features custom browser detection and launch info and custom app callback.
However, the constructor in BankIdLauncherCustomAppCallbackContext is internal and we can't use it when implementing the IBankIdLauncher interface, i.e I can't create a callback context as it's done in the source.
Is this by design? If yes; How do I create a BankIdLauncherCustomAppCallbackContext?
BR,
Max.
Beta Was this translation helpful? Give feedback.
All reactions