What
AuthAppForTesla/Info.plist still carries several keys from the app's 2021 origins that are now either meaningless or actively wrong.
UIRequiredDeviceCapabilities demands armv7
<key>UIRequiredDeviceCapabilities</key>
<array><string>armv7</string></array>
armv7 is 32-bit ARM. The app's deployment target is 26.0, which is 64-bit only — no device that can install this app is an armv7 device. The key is a fossil from the Xcode iOS template and should be removed rather than corrected.
NSUserActivityTypes names three intents that no longer exist
<key>NSUserActivityTypes</key>
<array>
<string>GetAccessTokenIntent</string>
<string>GetRefreshTokenIntent</string>
<string>RefreshTokensIntent</string>
</array>
None of these types exist in the codebase. The app now ships four App Intents with entirely different names, in AuthAppForTesla/AppIntents/:
GetOwnersAPIToken
RefreshOwnersAPIToken
GetFleetAPIToken
RefreshFleetAPIToken
Modern App Intents do not need NSUserActivityTypes registration, so the key should go rather than be updated to the new names. This is the same legacy generation as the intent reported broken in #24.
LSRequiresIPhoneOS
Set to true. Harmless on Catalyst (the key is dropped from the built Mac bundle), but it is inconsistent with a target that explicitly supports Mac, and worth clearing while in here.
Minor
UIStatusBarHidden and UIStatusBarStyle are inert under SwiftUI lifecycle.
UISupportedInterfaceOrientations is portrait-only for iPhone while iPad gets all four. That is a deliberate-looking choice, so leaving it alone — flagging only in case it is not.
Why bother
None of this is user-visible on its own. It is worth a single small pass because these keys are actively misleading to anyone reading the plist to work out what the app supports, and because UIRequiredDeviceCapabilities is the sort of thing that can affect App Store device eligibility if it is ever taken at face value.
Small, self-contained, no behaviour change expected — verify with a build for both iOS and Catalyst afterwards.
Posted by agent — anything without this footnote was written by Kim.
What
AuthAppForTesla/Info.pliststill carries several keys from the app's 2021 origins that are now either meaningless or actively wrong.UIRequiredDeviceCapabilitiesdemandsarmv7armv7is 32-bit ARM. The app's deployment target is 26.0, which is 64-bit only — no device that can install this app is anarmv7device. The key is a fossil from the Xcode iOS template and should be removed rather than corrected.NSUserActivityTypesnames three intents that no longer existNone of these types exist in the codebase. The app now ships four App Intents with entirely different names, in
AuthAppForTesla/AppIntents/:GetOwnersAPITokenRefreshOwnersAPITokenGetFleetAPITokenRefreshFleetAPITokenModern App Intents do not need
NSUserActivityTypesregistration, so the key should go rather than be updated to the new names. This is the same legacy generation as the intent reported broken in #24.LSRequiresIPhoneOSSet to
true. Harmless on Catalyst (the key is dropped from the built Mac bundle), but it is inconsistent with a target that explicitly supports Mac, and worth clearing while in here.Minor
UIStatusBarHiddenandUIStatusBarStyleare inert under SwiftUI lifecycle.UISupportedInterfaceOrientationsis portrait-only for iPhone while iPad gets all four. That is a deliberate-looking choice, so leaving it alone — flagging only in case it is not.Why bother
None of this is user-visible on its own. It is worth a single small pass because these keys are actively misleading to anyone reading the plist to work out what the app supports, and because
UIRequiredDeviceCapabilitiesis the sort of thing that can affect App Store device eligibility if it is ever taken at face value.Small, self-contained, no behaviour change expected — verify with a build for both iOS and Catalyst afterwards.
Posted by agent — anything without this footnote was written by Kim.