Internal user identifier setting is not effective in latest versions.

[Ysix]

MAX SDK Version

12.4.0

Device/Platform Info

iOS

Current Behavior

Attaching an internal user identifier with either the newest API

builder.settings.userIdentifier = "«USER-ID»" 

or the deprecated API

ALSdk.shared()!.userIdentifier = "user-id"

doesn't seems to be effective:

• User Id is not found in the User revenue API's data
• User Id is not found when using the Creative debugger

Expected Behavior

I expect to retrieve the provided user id in the creative debugger and in the data provided by AppLovin Max.

How to Reproduce

• Instanciate the AppLovinMax SDK with a userIdentifier
• Display some ad
• Open the creative debugger.

Additional Info

This bug is also impacting at least versions 12.3.0 and 12.3.1. It was not present in version 11.9.0

[thomasmso]

@Ysix - Could you provide your integration code for when you set the user id, relative to your other calls to our SDK?

[Ysix]

Sure !

        // Create the app lovin max initialization configuration
        let appLovinInitConfig = ALSdkInitializationConfiguration(sdkKey: Constants.AppLovinSDKKey) { builder in
            builder.mediationProvider = ALMediationProviderMAX
            builder.settings.userIdentifier = installationId
        }

        guard let appLovin = ALSdk.shared() else {
            throw AdvertisingError.appLovinNotFound
        }

        appLovin.initialize(with: appLovinInitConfig) { (configuration: ALSdkConfiguration) in
           // start ad loading
        }

When running this code I can see in the console:

[AppLovinSdk] DEBUG [ALSdkSettings] ALSdkSettings setUserIdentifier: xxxxxx

[zdrake314]

@Ysix, Can you reproduce this in our demo app: https://github.com/AppLovin/AppLovin-MAX-SDK-iOS

I checked the creative debugger as well, and the User ID shows up there when I do this in my personal test app and our internal diagnostic test app.

[Ysix]

Allow me to clarify my previous message:

Upon running this code, I observed the following output in the console: [AppLovinSdk] DEBUG [ALSdkSettings] ALSdkSettings setUserIdentifier: xxxxxx

Here, xxxxx served as a placeholder for the current user ID.

I intended to convey that despite not locating it in the creative debugger, the log indicated successful provision of the user ID.

--

I'll try to reproduce my issue in the demo app, thanks.

[Ysix]

I confirm I have the same issue in the demo app project:

The user id is correctly shown in the console:

But not in the creative debugger:

[zdrake314]

Okay, I've got a clean repro case:

• Old method works
• New method doesn't

This is in our internal test app (Swift, iOS SDK 12.3.1). I've written up an internal ticket for this and will notify this thread when action is taken.

[Ysix]

This is great news, thank you!

By any chance, do you have an estimated time of arrival (ETA)?

Also what is the old method you mention ? Maybe we could use it as a workaround ?

[zdrake314]

No ETA, but I see there's a pull request for the fix, so it will probably be soon.

The old way I mentioned is documented here: https://dash.applovin.com/documentation/mediation/ios/getting-started/integration#initialize-the-sdk

Yes, it would work as a work-around. It is deprecated, but hasn't been removed yet.

[zdrake314]

This has been fixed in iOS SDK 12.4.2, released May 6 2024. Chagelog: https://developers.applovin.com/en/ios/changelog