Internal server errors

[GuillermoCiqueHolvi]

We're using Sentry to track errors in our app and since one of the latest versions we started getting thousands of HTTPClientError with status code: 500.

They all seem to be coming from requests made by Adjust, all of them have a https://analytics.adjust.com/* URL.

Can you offer any insight as to why this is?

[uerceg]

Hi @GuillermoCiqueHolvi,

Is this all you can see from this tool when it comes to error message being reported? Is there any additional information available?

I assume your app which is reporting this is using Adjust SDK v4.38.0? How are you adding Adjust SDK to your app (CocoaPods / Carthage / SPM / framework from the release page / something else)? Does your app contain Privacy Manifest? If yes, are you maybe defining any of the Adjust domains under tracking domains part of the Privacy Manifest?

[GuillermoCiqueHolvi]

Hey @uerceg! Thanks for the response, we're using SPM and yes I believe this started with 4.38.0, we have an update in review with 4.38.1 but from the changeling I would not expect any change on this.

This is a sample request/response giving the error:

And here is a sample stacktrace:

I think that's probably the only relevant information I can gather from Sentry. I can see that the Sentry SDK seems to be adding a Sentry-Trace header, I don't think that should cause a 500 but I don't know 🤷‍♂️ Also I believe it was starting on 4.38.0 Adjust started using a different URL for consented and non-consented users, maybe that has something to do with this.

[uerceg]

Hi @GuillermoCiqueHolvi,

Thank you for the detailed information. And how about these: Does your app contain Privacy Manifest? If yes, are you maybe defining any of the Adjust domains under tracking domains part of the Privacy Manifest?

[GuillermoCiqueHolvi]

@uerceg we do have the PrivacyManifest but we're not adding any Adjust domains under tracking domains, I checked your get started guide and there was nothing new there. Could this be causing 500 errors on your side?

[uerceg]

It shouldn't. 🤔 You have my email in my GitHub profile. If you can write to me, reference this issue and lemme know your app token, I'll ask the team to check how does the incoming traffic looks like. Also, if you have the date when is that the app version which has the SDK 4.38.0 went live, that would also be good to know.

[GuillermoCiqueHolvi]

@uerceg do you have any update on this?

[uerceg]

Hey, it has been escalated to our support teams which are checking the traffic to see what's up. I think there is also an internal support team ticket where some of the account managers is looking at it, so most probably they are going to ping you. Are you in touch with them or maybe someone else from your team?

[GuillermoCiqueHolvi]

We're not in touch with anyone else, as far as I can tell the last communication we had was the email I sent with further info.

[ghadeermohameedelmahdy]

Any updates regarding this error as I have the same issue , thanks in advance,