Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Delayed onAttributionChanged callback after upgrading to Adjust 4.38.3 #620

Open
zxq126 opened this issue Oct 9, 2024 · 0 comments
Open

Comments

@zxq126
Copy link

zxq126 commented Oct 9, 2024

After upgrading the Adjust SDK from 4.33.0 to 4.38.3, I noticed a significant increase in the time between calling Adjust.onResume and receiving the first onAttributionChanged callback. Based on tracking data, the percentage of users receiving the callback within 20 seconds dropped by approximately 9%.

Steps to Reproduce
Using Adjust version 4.33.0, track the time between calling Adjust.onResume and receiving the first onAttributionChanged callback for new users.
Upgrade to Adjust 4.38.3 and repeat the tracking.
Compare the results, noting that the callback time has increased after the upgrade.

Expected Behavior
The callback time should remain consistent with the previous version or not exhibit a significant delay.

Actual Behavior
After upgrading to Adjust 4.38.3, the percentage of users receiving the callback within 20 seconds decreased by approximately 9%.

Environment Information
Adjust SDK version: 4.38.3
Android project: no changes to Adjust API calls other than updating the SDK version
Dependency: com.android.installreferrer:installreferrer:2.2

Code Snippet

config.setOnAttributionChangedListener(new OnAttributionChangedListener() {
    @Override
    public void onAttributionChanged(AdjustAttribution attribution) {
        // Attribution callback logic
    }
});

Additional Notes
I understand that Adjust.onPause could potentially influence this timing. However, we have not modified the activity interaction flow during this Adjust version update, so we believe this API can be ruled out as the cause.

Analysis
Please help verify whether this behavior is expected and assist in identifying potential causes for the delay. Could this issue impact attribution timing or other functionality?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant