Third party custom adapter big bug！！

[v5huang]

MAX SDK Version

12.4.0+

Device/Platform Info

all android device

Current Behavior

Call "setMediationProvider(AppLovinMediationProvider.MAX)" when init sdk, third party custom adapter cannot get the custom parameters, parameters.getCustomParameters() is null

Expected Behavior

Call "setMediationProvider(AppLovinMediationProvider.MAX)" when init sdk, third party custom adapter cannot get the custom parameters, parameters.getCustomParameters() is null

How to Reproduce

Call "setMediationProvider(AppLovinMediationProvider.MAX)" when init sdk, third party custom adapter cannot get the custom parameters, parameters.getCustomParameters() is null

Reproducible in the demo app?

Yes

Additional Info

No response

[applovinAsh]

@v5huang - can you confirm that you have set the custom parameters in the ad unit? Can you provide the ad unit ID and/or the AppLovin account email?

[v5huang]

1: Initialize the max sdk
AppLovinSdkInitializationConfiguration initConfig = AppLovinSdkInitializationConfiguration.builder
(AdConfig.MAX_APP_KEY, this.getApplicationContext() )
.setMediationProvider(AppLovinMediationProvider.MAX)
.build();

// Initialize the AppLovin SDK
AppLovinSdk.getInstance( this ).initialize(initConfig, configuration -> {
Log.i(TAG, "AppLovinSdk-init:" );
} );
2: When configuring AD slots, json parameters are added to custom params

3: In the custom adapter, in the initialize method, the parameter value is not retrieved via getCustomParameters()
Bundle bundle = parameters.getCustomParameters();
String sid = bundle.getString("sid");
String token = bundle.getString("token");
String debug = bundle.getString("isdebug");

The sid,token, and debug values are all null

1: When configuring AD slots, json parameters are added to custom params
(https://github.com/user-attachments/assets/b648f045-c4f2-47ef-9f05-e04c8519d3ca)

2: max sdk init
private void initSdk() {
// Max 13版本及以上
AppLovinSdkInitializationConfiguration initConfig = AppLovinSdkInitializationConfiguration.builder
(AdConfig.MAX_APP_KEY, this.getApplicationContext() )
.setMediationProvider(AppLovinMediationProvider.MAX)
.build();

// Initialize the AppLovin SDK
AppLovinSdk.getInstance( this ).initialize(initConfig, configuration -> {
    Log.i(TAG, "AppLovinSdk-init:" );
} );

}
3: In the custom adapter
@OverRide
public void initialize(MaxAdapterInitializationParameters parameters, Activity activity, final OnCompletionListener onCompletionListener) {
Log.d(TAG, "initialize alx sdk……");
Log.d(TAG, "applovin-adapter-version:" + ADAPTER_VERSION);

Bundle bundle = parameters.getCustomParameters();
String sid = bundle.getString("sid");
String token = bundle.getString("token");
String debug = bundle.getString("isdebug");

}

[v5huang]

//Max
public static final String MAX_APP_KEY = "****";
public static final String MAX_BANNER_AD = "d784fd2128f4d859";
public static final String MAX_INTERSTITIAL_AD = "8309f13fe976b315";
public static final String MAX_REWARD_VIDEO_AD = "03cae3773972a7ee";
public static final String MAX_NATIVE_AD = "2ad8ef4685641135";

[v5huang]

[jplianghu]

@v5huang
It looks like you have a boolean parameter "isdebug": true configured in your custom parameters, but in your app, you use bundle.getString("isdebug"); to retrieve the boolean value, which might cause an exception.

Could you please fix this (for example, call bundle.getBoolean( "isdebug")) and try again? If you still encounter errors, please share the verbose log with us so I can help you investigate.