Update Cocoapods to at least 1.10
sudo gem install cocoapods -n/usr/local/bin -v 1.10.0.rc.1
Hogdotmac
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
thought this was an issue with iOS 12 that was fixed, but now it's re-surfacing in iOS 13.7 - 14.1.
other apps (using the same code) on the same device are receiving locations just fine. app is even running and logging activity, but sometimes stops receiving locations.
p.s: permissions are also granted and set to precise, according to the location manager, significant location fires.
I'm on MacOS 12.1
i've tried:
ProcessInfo.processInfo.performActivity(options: [.idleDisplaySleepDisabled, .userInitiated], reason: "...")
IOPMAssertionCreateWithName(kIOPMAssertionTypeNoDisplaySleep as CFString, UInt32(kIOPMAssertionLevelOn), "..." as CFString, &assertionID)
IOPMAssertionDeclareUserActivity("..." as CFString, kIOPMUserActiveLocal, &self.assertionID)
they all prevent display sleep fine however, neither of these prevent the screen saver ("Preferences>Desktop & Screen Saver") from starting
at a loss, have no idea other than to tell users to turn off the screen saver. if they have display sleep turned on they shouldn't be needing it ever anyways.
ok, so this API is gone, but what is the reasoning for CTTelephonyNetworkInfo.serviceSubscriberCellularProviders to also always return an object and never update regardless of whether a SIM is actually inserted?
Why aren't developers allowed to know whether a SIM is present at all?