Marios Dimitriadis

@eloev thank you for bringing this to our attention (and your help @shashanksu). As this is related to the Signature SDK, could you please contact Adjust's support so that we...

> @dimim @shashansku Sorry for the long reply, update signature library not solved this. I will return to the problem in Q3, because it's non-critical task, but it looks very...

Hi @kibotu, Thanks for reaching out. > I don't understand the solution for closing the issue. There was no solution provided. The topic was explored, but with no immediate solutions...

Hey @kibotu, Thank you for coming back to me & the recommendation. I raised it internally, as Signature relies solely on what the SDK provides on this front. Given the...

Hi @G00fY2. Thanks for getting in touch & sharing your thoughts. I can confirm that the size is an outcome of the product's nature: The Signature is a highly obfuscated...

@imliujun: > the SDK initialization fails and the Adjust.getAdid method does not receive a callback For the callbacks, please run your test on a real device. There's an internal task...

Closing as per the above msg & the thumbs up. Ping away if concerns. Thanks!

Hi @MoElkilany. Thank you for reaching out. > The archive did not include a dSYM for the AdjustSigSdk.framework [...] Please see https://github.com/adjust/ios_sdk/issues/760#issuecomment-2908926819. Happy to elaborate. > The Adjust SDK should...

> We have no signals or reports of the two being related. I'll sync internally to get you the help needed. @MoElkilany: To debug this further we need SDK's verbose...

@egorafanasenko, thanks for reaching out. If it's just the warning, **[1]** please see ~~https://github.com/adjust/ios_sdk/issues/760#issuecomment-2908926819~~ https://dev.adjust.com/en/sdk/ios/integrations/signature-library#troubleshooting, i.e. it is safe to ignore -- happy to expand. If you also see the...