Walkme.Sdk.Editor.Maui.Android 1.2.2

WalkMe.Maui.Editor

A .NET MAUI bridge/plugin for the WalkMe Android Editor SDK (WalkmeSdkPowerMode).

NuGet package (targets net9.0-android):

• Walkme.Sdk.Editor.Maui.Android — plugin surface (IWalkMe, managed models wrapping WalkmeSdkPowerMode; C# namespace WalkMe.Maui.Editor) plus the Android bindings and Editor .aar embedded in the same package. Jetpack Compose is not required: since Editor SDK 1.2.1 it is compileOnly on the Android side, so the package neither embeds Compose AARs nor declares Compose dependencies.

Install (consumers)

dotnet add package Walkme.Sdk.Editor.Maui.Android

Requires a .NET 9+ Android MAUI app (net9.0-android or newer). Or add a PackageReference to Walkme.Sdk.Editor.Maui.Android. You do not need a separate Bindings package or to build the Editor AAR yourself.

Do not reference both Walkme.Sdk.Maui.Android (core) and Walkme.Sdk.Editor.Maui.Android in the same app — use one or the other.

Prerequisites (building this repo)

• .NET 9+ SDK
• MAUI and Android workloads: dotnet workload install maui android
• A JDK compatible with the Android workload

Building and packing

dotnet restore
dotnet build
dotnet pack

OkHttp 5.1.0 is a NuGet dependency: Square.OkHttp3.LoggingInterceptor 5.1.0.2 brings Square.OkHttp3.JVM and Square.OkIO.JVM 3.15.0 (or a newer Square.OkIO.JVM already in the app). Do not also reference Square.OkHttp3 or Square.OkHttp3.Android; those ship okhttp-android, which duplicates okhttp-jvm. Koin 3.5.6 and Lottie 6.4.0 are embedded. No maintained .NET binding matches those artifacts.

Compose is neither referenced nor shipped. Editor SDK 1.2.1 replaced its Compose usage in the editor UI with plain Android views and declares Compose compileOnly, so apps that use Compose keep their own version and apps that don't stay free of it.

Transforms/Metadata.xml limits binding to the SDK's public surface (com.walkme.api* and com.walkme.pm). The release AAR is R8-minified, so binding internal packages fails the generator on obfuscated names and on Kotlin views that widen override visibility.

What's wrapped

IWalkMe mirrors the native WalkmeSdkPowerMode singleton (same public API as core WalkMeSDK):

Start, Stop, Restart, SetUserId, SetLanguage, SetVariable, SetEventUserVars, SetTenantId, StartItemById, DismissItem, SendEvent, plus ItemPresented / ItemDismissed / ItemAction / AnalyticsEventSent C# events.

using WalkMe.Maui.Editor;

var options = new WalkMeStartOptions
{
    SystemGuid = "<YOUR_SYSTEM_GUID>",
    Environment = "Production",
    DataCenter = WalkMeDataCenter.Prod,
};

CrossWalkMe.Default.Start(options); // after the host Activity exists

Or via DI: builder.UseWalkMe() in MauiProgram.cs and inject IWalkMe.

Known risk areas

1. WalkmeSdkPowerMode.Instance — Kotlin object bound as Com.Walkme.PM.WalkmeSdkPowerMode; this plugin always uses Instance!.Xxx(...).
2. WalkmeDataCenter mapping — sealed class cases mapped in ToNative at the bottom of WalkMeImplementation.cs. If generated names differ after an SDK bump, adjust that method only.
3. Binding surface — Transforms/Metadata.xml removes non-com.walkme.* packages so R8-obfuscated types in the monolith AAR are not bound (they break the generator).