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

UnifiedDeepLinkData type definition is different from real data #575

Open
changwoolab opened this issue Sep 4, 2024 · 0 comments
Open

Comments

@changwoolab
Copy link

changwoolab commented Sep 4, 2024

Report

Current type UnifiedDeepLinkData is different from real data

Current type definition

export type UnifiedDeepLinkData = {
    status: "success" | "failure",
    type: "onDeepLinking",
    deepLinkStatus: 'FOUND' | 'NOT_FOUND' | 'Error',
    isDeferred: boolean,
    data: {
        campaign: string;
        deep_link_value: string;
        deep_link_sub1?: string;
        media_source: string;
        pid?: string;
        link: string,
        af_sub1?: string;
        af_sub2?: string;
        af_sub3?: string;
        af_sub4?: string;
        af_sub5?: string;
        [key: string]: any;
    }
}

Real data

data is not an object but string, and deepLinkStatus is not "Error" but "ERROR"

Screenshot 2024-09-04 at 3 32 44 PM

Plugin Version

6.12.2

On what Platform are you having the issue?

Android

What did you do?

Added validation of type "string"

What did you expect to happen?

Type should be changed

What happened instead?

data is not an object but string, and deepLinkStatus is not "Error" But "ERROR"

Please provide any other relevant information.

@changwoolab changwoolab changed the title UnifiedDeepLinkData type definition is different from real data UnifiedDeepLinkData type definition is different from real data Sep 4, 2024
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