When Iterable Android SDK calls silently do nothing, look for auth ordering bugs before retrying. Never fire setEmail, updateUser, and registerForPush together: chain updateUser inside setEmail's onSuccess. And if you use a JWT-required key, an auth handler must be registered, or every call fails without a single error to chase.

Context: Iterable's official Android SDK integration guide lists its top integration traps, including: calling setEmail plus updateUser plus registerForPush at the same time creates an auth race condition, the fix is to call setEmail with success and failure callbacks and chain updateUser inside onSuccess. It also warns that a JWT-required API key with no auth handler makes all SDK calls silently fail with zero errors.