[Bug] Rust SDK check_crawl_status errors if there are arrays in the metadata

[justindgm]

Describe the Bug
I suspect that when calling check_crawl_status, the Rust SDK expects all of the metadata fields to be strings, even though sometimes they can be Vec.

For example

"viewport": ["width=device-width, initial-scale=1", "width=device-width,initial-scale=1.0,maximum-scale=1.0,user-scalable=no,viewport-fit=cover"]

or

"twitter:image": ["http://localhost:3000/#{FALLBACK_IMAGE}", "https://images.contentstack.io/v3/assets/bltdc2476c7b6b194dd/blt46acaa0d3fe3fd06/66db08a7b89507bdf18d1c3d/Sports_Impact_Report.jpg"]

If you have a crawl with vector metadata like this, then the Rust SDK will throw the error

Error: Failed to parse response: invalid type: sequence, expected a string

However, if your crawl has only string fields in the metadata, it works as expected.

To Reproduce

1. Get a crawl with vectors in the metadata
2. Call check_crawl_status with that crawl id using the rust sdk

Expected Behavior
The sdk should throw an error

Environment (please complete the following information):

• OS: macOS Sequoia 15.3
• Firecrawl Rust SDK Version: 1.0.0
• Node.js Version: N/A

[blackmad]

I think I'm probably getting this error too - "https://www.cnn.com/: Failed to parse response: invalid type: sequence, expected a string"