Hello, we've encountered issues on Android using Custom Catalogs.
-
On Android the only possible way to create a custom catalog is using
.addFromCatalog()
from a .shazamcatalog file, there is no method like iOS SDK provides.addReferenceSignature()
to add a signature. -
Generating from iOS a .shazamcatalog file and loading in Android returns wrong values for query signature duration:
Android
catalog.minimumQuerySignatureDurationInMs: 3000
catalog.maximumQuerySignatureDurationInMs: 2147483647
iOS
minQuerySignDuration: 1.0 seconds
maxQuerySignDuration: 12.0 seconds
No match resulting for Android but iOS works as expected.
Is it possible to match against a custom catalog on Android?
Any help will be much appreciated.
Hi @andzk, thank you for opening the Feedback.
So what's happening is the Android SDK disregards a signature (or clusters of signatures) that have no associated metadata. I suggest when you populate a custom catalog to also provide metadata for any signature ( see https://developer.apple.com/documentation/shazamkit/shcustomcatalog/3747140-addreferencesignature).
I have tried with a custom catalog following such recommendation and I was able to get matches. We will be working with the team to consolidate a common behaviour with the iOS counterpart in the future.
Best Regards