Start with the Input Type Downtify Expects
A community reply stated that the tested Downtify build was not behaving as a keyword search tool and did not use the YouTube or YouTube Music choices even though those options appeared in its interface. The suggested workflow was a direct Spotify track, album, or playlist URL.
That makes input type the first reversible discriminator. Copy one direct track or album URL from Spotify, paste the complete URL, and submit it without changing metadata or audio-source options at the same time.
If a job appears, the earlier endless spinner was an input mismatch. If the link is accepted but the queue stays empty, the test has ruled out keyword search as the complete explanation.
Use Job Creation, Not Link Acceptance, as the Success Signal
The author tried a direct Spotify album URL and saw the same behavior. A later participant reproduced the result: the link was accepted, but no download job was created and no error appeared.
This is stronger than a generic “search does not work” report because it tests the workflow the reply described as supported. The recovery signal is a visible queued job that progresses, not the absence of a validation error.
Repeat the same URL after an app restart. If a job appears only once and fails again after restart, the app is not yet reliably recovered.
Keep the Suggested Upstream Cause Qualified
A reply attributed the behavior to an upstream Downtify or spotDL problem and suggested API rate limiting involving the App Store image. The topic does not show logs, an upstream issue, a different image control, or a before-and-after update that proves that mechanism.
Record the app image version, ZimaOS version, exact input category, queue state, and container logs. A rate-limit response or upstream error in the logs would support the hypothesis; an empty interface alone does not.
Do not change unrelated container privileges, expose credentials, or add guessed environment variables based on this topic. Those branches belong to the earlier 2025 configuration discussion and were not tested here.
The January 2026 Topic Ends Without a Reliable UI Workaround
The final reply says there was no reliable workaround from the UI at that moment. The author did not later confirm a fix, and the thread does not name a working package version.
Escalate with the direct-link control and evidence that the queue remains empty. This clearly distinguishes the case from unsupported keyword or artist-page searches.
After a documented Downtify or App Store update, repeat the identical Spotify link and confirm that a job is created, downloads content, and still works after restarting the app. Until that validation exists, the result remains unresolved.
FAQ
Can Downtify search by artist name or keywords?
The community reply described direct Spotify track, album, or playlist URLs as the usable input path for this build.
Does a valid Spotify link prove Downtify is working?
No. In the source case the link was accepted, but the queue stayed empty. A created and progressing job is the useful success signal.
Was API rate limiting confirmed?
No. It was suggested as a likely upstream explanation but was not demonstrated with logs or a successful control.
