Hello, I want to dynamically update the values of the LSApplicationQueriesSchemes key in the info.plist file within this project. Is this possible? What is Apple's stance on this matter in terms of security?
Core Services
RSS for tagAccess and manage key operating system services using Core Services.
Posts under Core Services tag
26 Posts
Sort by:
Post
Replies
Boosts
Views
Activity
I have tried below code to open [Settings(App) -> Bluetooth Settings] but it is navigating to App permission screen instead of Bluetooth Settings. I have tried to search but didn't get any latest documentation regarding it. Is there any way to do this?
guard let url = URL(string: UIApplication.openSettingsURLString) else {
return
}
if UIApplication.shared.canOpenURL(url) {
UIApplication.shared.open(url, options: [:], completionHandler: nil)
}
Hello Community,
Need your help/guidance please. Seeking LocationServices experts who can advise me whether my idea for a valuable add-on feature that I've been trying to add into my app for 2+ months is achievable or not given LocationServices limitations.
The Feature: to enable users who would like to be automatically notified whenever they're within X meters from a store that provides them an exclusive discount BUT only when they choose to be notified. Instruction to enjoy the feature is by keeping app open in 'background state' (means opened and kept in background) but not when app is terminated state (completely closed).
The state is important because I would like to give users the choice to only receive notifications when they choose to instead of all-time. That is to eliminate unnecessary power consumption fetching location updates constantly when user don't need them (example staying at home, at work, etc), but give them option when they go out.
Ideal scenario (after opting in to enable 'Always'): user launches the app, keeps in background, go out shopping/dining/etc and enjoy convenience of being automatically notified whenever about Xmeters from a place that they have an exclusive offer for.
Implemented conditions:
API is called at fixed time interval whenever user is within about 10 meters from their last location, that is to limit checking only when there is certainty user is within the same place for sometime instead of just walking by (this currently works perfectly, using AccuracyBest),
the challenge when user terminates app, LocationServices wakes up again and continues to fetch location updates constantly.
The Ask:
Is it technically possible that I configure app LocationServices to not wake-up with [AccuracyBest] when terminated but instead use only reduced accuracy (like 'significant location updates' or on 'AccuracyOne/ThreeKilometer')?
Ideas/suggestions/recommendations would be much much appreciated
Apple deprecated launch service calls like LSCopyAllRoleHandlersForContentType, referring to -[NSWorkspace URLsForApplicationsToOpenContentType:] instead.
However all those new NSWorkspace methods do not have the crucial LSRolesMask the launch service calls have.
For example, I have code that looks up all alternative shells, and with LSCopyAllRoleHandlersForContentType I could simply provide LSRoleMask.shell to restrict the returned bundle identifiers to shells only.
This is not the first time Apple deprecates stuff without a proper replacement and I don't really get it.
Every OS update is basically a downgrade.
Or is there another way to replicate the old launch service call behavior?
Colleagues, I need your help. I have an swift app-widget and I wish users to have the ability to go to a certain IOS Settings screen, for example to "Display & Brightness". or Night Shift.
So, when user taps on widget he will go to Display & Brightness settings screen.
Tell me please, is it possible to adjust the code to work this way or does Apple policies not allow redirecting users to a certain screen in ios settings?
I am trying to test an application in a SANDBOX environment.
iPhone XR, iOS 17.0.3, Xcode 15.0.1
Everything works, but with every transaction or update I get
a lot of CoreServise warnings, Error messages, etc.