I develop Podcast Addict for Garmin. On a physical fēnix 7X Pro, an audio content provider request returns `UNABLE_TO_PROCESS_MEDIA` (-1005) even though the progress callback reports that the watch received the full expected file size. I reproduced this twice in a single native sync with a small public MP3, and again with a podcast episode.
Environment
- Watch: Garmin fēnix 7X Pro
- Watch firmware: [fill in from System → About]
- Connect IQ SDK: 9.3.0 for macOS, command-line `monkeyc`
- Build target: `fenix7xpro`
- App type: Audio Content Provider
- Test: sideloaded diagnostic build on physical hardware, using native Wi-Fi audio sync
Steps to reproduce
1. Start a native audio provider sync on the watch.
2. In the native sync request chain, call `Communications.makeWebRequest` with the options below.
3. Log the bytes transferred and expected size from the progress callback, and the response code from the completion callback.
4. From the completion callback, request the same public MP3 again in the same sync session.
The control URL serves a 52,079-byte `audio/mpeg` file. I verified the file with ffprobe as MP3, 44.1 kHz, stereo.
```monkeyc
Communications.makeWebRequest(
"https://samplelib.com/mp3/sample-3s.mp3",
null,
{
:method => Communications.HTTP_REQUEST_METHOD_GET,
:responseType => Communications.HTTP_RESPONSE_CONTENT_TYPE_AUDIO,
:mediaEncoding => Media.ENCODING_MP3,
:fileDownloadProgressCallback => method(:onProbeProgress)
},
method(:onProbeComplete)
);
Expected result
The request completes successfully and returns a usable cached audio reference.
Actual result
Both control requests reached 52,079 of 52,079 bytes, then returned -1005. The podcast episode also reached its full expected size and returned -1005.
Garmin library code=200 requestMs=13984
Garmin control start mp3Pass=1 encoding=2
Garmin control result step=1 code=-1005 bytes=52079 expectedBytes=52079 requestMs=5295 firstProgressMs=5142 progressSpanMs=78
Garmin control start mp3Pass=2 encoding=2
Garmin control result step=2 code=-1005 bytes=52079 expectedBytes=52079 requestMs=220 firstProgressMs=131 progressSpanMs=36
Garmin control start episode=930054 encoding=2
Garmin control result step=3 code=-1005 bytes=1774856 expectedBytes=1774856 requestMs=5220 firstProgressMs=3036 progressSpanMs=2045
Garmin control finished probes=3
The first progress callback arrived at 5.14 seconds for the first control request and 0.13 seconds for the second. These are times to the SDK callback. I don’t have a measurement of when the first network byte arrived.
Could you reproduce this on a fēnix 7X Pro and check why the native downloader returns -1005 after reporting a complete transfer? If -1005 can arise from several stages of media processing or caching, is there a device log or diagnostic build that would show which stage failed?
API reference: https://developer.garmin.com/connect-iq/api-docs/Toybox/Communications.html
I’m also reporting slow downloads during native Wi‑Fi sync. In one 10-episode run, the audio requests took 3 minutes 30 seconds in total. Of that, 2 minutes 51 seconds elapsed before the first progress callback for each file. The files were roughly 1–4 MB each, and the wait recurred throughout the same sync session.
The delay varies substantially for the same file. A 1.77 MB episode took 7.18 seconds on one attempt and 54.06 seconds on another. On the slower attempt, the first progress callback arrived at 51.99 seconds. In a separate diagnostic run, the same 52 KB MP3 took 5.30 seconds on its first request and 0.22 seconds on its second. The library metadata request alone took 13.98 seconds.
Could you investigate where the native downloader spends this time and whether the delay is related to -1005? Is there a device trace that shows when the request actually starts, when bytes first arrive, and when media processing begins? The app can measure when the SDK reports progress, but it has no timestamp for the first network byte.