You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current app target inference is intentionally conservative but still leans on simple filesystem signals such as */Resources/Info.plist. Real projects may use generated Info.plist files, target-specific build settings, extensions, or nonstandard folder layouts.
Scope
Parse enough .pbxproj structure to distinguish app targets from extensions, frameworks, test bundles, and resource bundles.
Prefer product type and target metadata over folder naming when available.
Keep behavior conservative when target ownership is ambiguous.
Acceptance
Repos with generated Info.plist do not become unsupported solely because the file is absent.
Extension-only signals do not cause the analyzer to treat an extension as the main app.
can_apply remains false when the main app target cannot be proven.
@Zach677 Fixed on main in d627e58. The analyzer now uses PBXNativeTarget product metadata, keeps extension-only projects non-applicable, and preserves AppKit repositories as read-only; CI passed for tooling, app builds, and tests.
Activity
linear-code commentedon May 20, 2026
SPA-57
Zach677 commentedon Jul 18, 2026
@Zach677 Fixed on main in d627e58. The analyzer now uses PBXNativeTarget product metadata, keeps extension-only projects non-applicable, and preserves AppKit repositories as read-only; CI passed for tooling, app builds, and tests.