Expand my Community achievements bar.

Help shape the future of AI assistance by participating in this quick card sorting activity. Your input will help create a more effective system that better serves your needs and those of your colleagues.
SOLVED

Adobe throw TimeOut always

Avatar

Level 2

Hello, good afternoon.

Adobe is continually launching general.callback.timeout with error code 1. On some devices this does not happen and on others it does.

 

I am using Kotlin and adobe analitycs version 1.2.10

 

Can somebody help me?

 

Thanks.

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Employee

Hi @franciscojaviera ,

 

Thank you for reaching out. Could you please open a request through Adobe Client Care and provide additional details about the Adobe SDK versions used, your configuration setup and code snippet for the usage of the API that is returning callback timeout so we can investigate further?

 

Thank you,

Emilia Dobrin

Adobe Experience Cloud

View solution in original post

5 Replies

Avatar

Correct answer by
Employee

Hi @franciscojaviera ,

 

Thank you for reaching out. Could you please open a request through Adobe Client Care and provide additional details about the Adobe SDK versions used, your configuration setup and code snippet for the usage of the API that is returning callback timeout so we can investigate further?

 

Thank you,

Emilia Dobrin

Adobe Experience Cloud

Avatar

Level 2

I have opened a ticket as you have told me and I have specified about my error. The method that constantly throws me CALLBACK_TIMEOUT" with errorName: general.callback.timeout and errorCode: 1 is "Identity.appendVisitorInfoForURL()"

Avatar

Level 6

Hi @franciscojaviera 

 

Would you please share how your issue is resolved?

 

I'm using AEP Mobile SDK ReactNative, and having the same issue with timeout error in iOS.

 

Thanks,

John

 

Avatar

Level 2

Hello @Hey_John, I finally didn't have a solution. It only happens to me on some devices but when it reached production most of them worked.