infobip-api-php-client getWhatsAppMediaMetadata returns null

TL;DR

Upgrade infobip-api-php-client to 6.2.1 or later and use the returned array (see the updated usage test ReceiveWhatsAppApiTest). The maintainers fixed it in version 6.2.1: getWhatsAppMediaMetadata now returns an array keyed by the documented media-metadata headers.

Steps

1. Calling getWhatsAppMediaMetadata in infobip-api-php-client always returned null in the getWhatsAppMediaMetadataResponse. The method wraps a HEAD request (media metadata is returned in response headers, not a body), and the library's response handler discarded the headers and returned null instead of the metadata.
2. The library did not model HEAD-request responses properly and dropped the metadata headers. The maintainers fixed it in version 6.2.1: getWhatsAppMediaMetadata now returns an array keyed by the documented media-metadata headers. Upgrade infobip-api-php-client to 6.2.1 or later and use the returned array (see the updated usage test ReceiveWhatsAppApiTest). The reporter confirmed the fix works.
3. Take the question above and check if it matches what you're seeing. If it does, work through the verified fix step by step. Start with the cause described first, because that's what tells you the fix applies to your setup, then apply the changes in the order given. Verify by re-running whatever failed before, and expect the same behavior the thread author reported.

When to use

You are seeing this: Calling getWhatsAppMediaMetadata in infobip-api-php-client always returned null in the getWhatsAppMediaMetadataResponse. Use this skill when you run into "infobip-api-php-client getWhatsAppMediaMetadata returns null".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: 6.2.1. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Someone asked: Calling getWhatsAppMediaMetadata in infobip-api-php-client always returned null in the getWhatsAppMediaMetadataResponse. The method wraps a HEAD request (media metadata is returned in response headers, not a body), and the library's response handler discarded the headers and returned null instead of the metadata. The verified answer: The library did not model HEAD-request responses properly and dropped the metadata headers. The maintainers fixed it in version 6.2.1: getWhatsAppMediaMetadata now returns an array keyed by the documented media-metadata headers. Upgrade infobip-api-php-client to 6.2.1 or later and use the returned array (see the updated usage test ReceiveWhatsAppApiTest). The reporter confirmed the fix works.

Source: https://github.com/infobip/infobip-api-php-client/issues/67 Discussion and confirmation live at https://vectle.com/threads/thr_aZurF2Z9C8pCG7yFw5_Q