Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

xCode 12 compilation warning: iOS Simulator target and Deprecated code on iOS 12.0 #508

Open
jefflks opened this issue Oct 1, 2020 · 10 comments · May be fixed by #600
Open

xCode 12 compilation warning: iOS Simulator target and Deprecated code on iOS 12.0 #508

jefflks opened this issue Oct 1, 2020 · 10 comments · May be fixed by #600

Comments

@jefflks
Copy link

jefflks commented Oct 1, 2020

The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99.

'kSecAttrAccessibleAlways' was deprecated in iOS 12.0: Use an accessibility level that provides some user protection, such as kSecAttrAccessibleAfterFirstUnlock

'kSecAttrAccessibleAlwaysThisDeviceOnly' was deprecated in iOS 12.0: Use an accessibility level that provides some user protection, such as kSecAttrAccessibleAfterFirstUnlockThisDeviceOnly

'kSecAttrAccessibleAlways' was deprecated in iOS 12.0: Use an accessibility level that provides some user protection, such as kSecAttrAccessibleAfterFirstUnlock

'kSecAttrAccessibleAlwaysThisDeviceOnly' was deprecated in iOS 12.0: Use an accessibility level that provides some user protection, such as kSecAttrAccessibleAfterFirstUnlockThisDeviceOnly

@DocMacFain
Copy link

Same problem

1 similar comment
@erolando
Copy link

erolando commented Oct 7, 2020

Same problem

@Rickth64
Copy link

+1 for the deprecation warnings

@weakvar
Copy link

weakvar commented Oct 22, 2020

@jefflks, @sergeifabian, @erolando and @Rickth64 — add this to your Podfile:

post_install do |installer|
  installer.pods_project.targets.each do |target|
    target.build_configurations.each do |config|
      config.build_settings.delete 'IPHONEOS_DEPLOYMENT_TARGET'
    end
  end
end

Source: https://www.jessesquires.com/blog/2020/07/20/xcode-12-drops-support-for-ios-8-fix-for-cocoapods/

@Rickth64
Copy link

@jefflks, @sergeifabian, @erolando and @Rickth64 — add this to your Podfile:

post_install do |installer|
  installer.pods_project.targets.each do |target|
    target.build_configurations.each do |config|
      config.build_settings.delete 'IPHONEOS_DEPLOYMENT_TARGET'
    end
  end
end

Source: https://www.jessesquires.com/blog/2020/07/20/xcode-12-drops-support-for-ios-8-fix-for-cocoapods/

That helps to silence the iOS 8.0 warning. Not the deprecation warnings. In fact, they only arise when the deployment target becomes 12.0, which is exactly what happens when I delete this key from the Pods (because it then inherits it from my project which is set to 12.0).

@jrikhof
Copy link

jrikhof commented Nov 17, 2020

If you include this version into you own podspec it's not going to work, because pod lib lint will fail. The deployment target needs to be increased as well.

#515

@pouriaalmassi
Copy link

pouriaalmassi commented Nov 21, 2020

Ignore warnings for the KeychainAccess pod like so

pod 'KeychainAccess', :inhibit_warnings => true

Then pod install.

Source: https://stackoverflow.com/a/13209057/1004227

@mickspecial
Copy link

What if using SPM ??

@johnarn
Copy link

johnarn commented Jan 19, 2022

@kishikawakatsumi I think that the right way to resolve this issue is to remove the deprecated accessibility levels. These accessibility levels have been declared by apple as deprecated for security reasons so there is no reason to exist and be maintained in the code. May I open a Pull Request with the solution?

Documentation
kSecAttrAccessibleAlways -> link
kSecAttrAccessibleAlwaysThisDeviceOnly -> link

@dfalling
Copy link

Do we know when these deprecated levels are going to be removed by Apple? We're coming up on new releases of iOS and macOS soon, which I worry may completely break KeychainAccess.

@Ogijun2018 Ogijun2018 linked a pull request May 16, 2024 that will close this issue
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 a pull request may close this issue.

10 participants