Xcode 27 build fails because AppAuthCore_Privacy resource bundle targets iOS 12.0
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- ios, objective-c
- Domain
- authentication, build-system, mobile
Research direction
Start at the AppAuth podspec and inspect how its deployment target is applied to the native target and privacy resource bundle. Run pod install with AppAuth 2.1.0, then verify that both generated targets use iOS 15.0 or later and that the project builds with Xcode 27.
Written by the indexing model from the issue text.
Description
Summary
Xcode 27 fails the build because AppAuth 2.1.0 generates its privacy resource
bundle with an iOS 12.0 deployment target.
Xcode 27 supports deployment targets starting at iOS 15.0.
Environment
- AppAuth-iOS: 2.1.0
- react-native-app-auth: 8.4.1
- React Native: 0.83.2
- Xcode: 27
- Application deployment target: iOS 17.2
- CocoaPods: 1.16.2
Generated targets
After running pod install, the generated Pods project contains:
AppAuth: 12.0
AppAuth-AppAuthCore_Privacy: 12.0
Error
The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to
12.0, but the range of supported deployment target versions is
15.0 to 27.0.x.
The build failure is reported for:
AppAuth-AppAuthCore_Privacy
Steps to reproduce
- Create an iOS project using CocoaPods.
- Add
AppAuthversion 2.1.0. - Set the application deployment target to iOS 15 or later.
- Run
pod install. - Build with Xcode 27.
- Observe that
AppAuthCore_Privacyretains iOS 12.0.
Expected behavior
AppAuth and its privacy resource bundle should use an iOS deployment target
supported by Xcode 27, preferably iOS 15.0 or later.
Suggested change
Raise the minimum iOS deployment target in the AppAuth podspec to iOS 15.0 so
both the native target and generated privacy resource bundle receive a valid
deployment target.
Temporary workaround
Applications can raise generated pod deployment targets in their Podfile
post_install hook. However, correcting the package podspec prevents CocoaPods
from generating unsupported targets.
Related issue
React Native has a related issue where deployment-target normalization skips
resource-bundle targets:
- Dominant language
- Objective-C
- Stars
- 2k
- Forks
- 867
- Avg merge
- 9d 20h
- Merged PRs (30d)
- 1
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openid/AppAuth-iOS
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 60/100
openid/AppAuth-iOS#908 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
openid/AppAuth-iOS#962 ·
-
enhancement triage
Difficulty 4/5 3-5 days Newbie friendliness 38/100
openid/AppAuth-iOS#953 ·
-
enhancement triage
Difficulty 4/5 3-5 days Newbie friendliness 45/100
openid/AppAuth-iOS#948 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
openid/AppAuth-iOS#932 · 1 comment ·
All issues in openid/AppAuth-iOS
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
firebase/firebase-ios-sdk#16718 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
julienXX/terminal-notifier#333 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
serhii-londar/open-source-mac-os-apps#1419 ·
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
prime-radiant-inc/evener#2440 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
AvaloniaUI/Avalonia#22312 ·
Maintainers usually reply within 1 day