{"version":"2.1.271","anchor":"ios-app-project-detection-gains-a-fresh-cache-bypass-optio","canonical_anchor":"ios-app-project-detection-gains-a-fresh-cache-bypass-optio","heading":"iOS app project detection gains a 'fresh' cache-bypass option and reports unknown separately","tier":"internal","area":"Dev Intent","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/ios-app-project-detection-gains-a-fresh-cache-bypass-optio","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### iOS app project detection gains a 'fresh' cache-bypass option and reports unknown separately\n\niOS app project detection gains a way to bypass its cache and treats 'unknown' like a cache miss\n\n**What**\n\nThe internal helper that checks whether a project is an iOS app project was renamed and now accepts an options object with a `fresh` flag. Setting `fresh` clears the previously cached result before re-checking. It also now treats a `has_ios_app_project` result of `null` (unknown) the same as a null result, meaning both cases invalidate the cache rather than being treated as a settled answer.\n\n**Why**\n\nThis lets Claude Code force a re-check of whether a project is an iOS app instead of always trusting a stale or inconclusive cached answer.\n\n- Area: Dev Intent\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}