Skip to content

Release testing clean-up: example deployment target + bundle identifier#959

Open
w-goog wants to merge 1 commit into
masterfrom
chore/release-testing-cleanup
Open

Release testing clean-up: example deployment target + bundle identifier#959
w-goog wants to merge 1 commit into
masterfrom
chore/release-testing-cleanup

Conversation

@w-goog

@w-goog w-goog commented Jun 4, 2026

Copy link
Copy Markdown
Collaborator

Cleans up two example-app configuration issues surfaced while testing the 2.1.0 release packaging.

Changes

  • Examples/Example-iOS_ObjC/Podfile — bump platform :ios from 11.0 to 12.0. AppAuth's podspec has required iOS 12 since 2.0.0 (Update minimum iOS version from 10 to 12. #918), so pod install on this sample currently fails with "Specs satisfying the AppAuth dependency were found, but they required a higher minimum deployment target."

  • Examples/Example-iOS_Swift-SPM — remove the hardcoded PRODUCT_BUNDLE_IDENTIFIER from the Xcode project so the bundle identifier is driven by Config/Example.local.xcconfig (the gitignored local override), consistent with how the OAuth client values are already configured. Note: building the SPM sample now requires setting your own PRODUCT_BUNDLE_IDENTIFIER in Example.local.xcconfig.

Testing

  • pod install + iOS Simulator build & launch of Example-iOS_ObjC succeed with the bumped Podfile.

- Example-iOS_ObjC/Podfile: bump platform :ios from 11.0 to 12.0 to match the
  podspec minimum deployment target (iOS 12 since 2.0.0); pod install otherwise
  fails to resolve the AppAuth dependency.
- Example-iOS_Swift-SPM: remove the hardcoded PRODUCT_BUNDLE_IDENTIFIER from the
  Xcode project so the bundle identifier is supplied via
  Config/Example.local.xcconfig, matching how the OAuth client values are set.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant