“Account Locked”

10.10.1 beta keeps locking up then logs me out? anyone else?

Hello, Scenario: My app is running in the foreground, logged into my backend server and I have registered for push notifications and received a push token. I have pin code activated on the phone. I make some code changes and re-flash it in Xcode, the app is running in debug mode wired to Xcode. I put the app in the background and lock the screen and wait 30 sec until data protection is activated and the keychain cannot be accessed. I send a push notification. In this case didRegisterForRemoteNotificationsWithDeviceToken if often called with the same push token as I had before. Data is protected in this state, hence I cannot access the auth token and send the token to the server. In this case it is not needed since the token is the same, but it got me a bit worried. In didRegisterForRemoteNotificationsWithDeviceToken I send the push token to the server, as the Apple docs recommend. My concern now is: could didRegisterForRemoteNotificationsWithDeviceToken be called in a real scenario when the phone is

How can I get the watch to lock onto the heart rate before starting a workout, in the same way that precision start works on the Ultra? In the past it required a special permission and I requested this several times without hearing back. I assume this was because the permission was intended for other app types (meditation etc). However now that precision start is available in the native app it would be great to provide it in my workout app. I looked around for the permission form again but couldn't find it so I was wondering if anyone knows how to do this? Thanks.

Every so often the question about what these NewTimePitch parameters control comes up. Unfortunately these two are really not documented anywhere else, so this information should help developers wondering what these two parameters do.kNewTimePitchParam_Overlap - This value controls the number of overlapped spectral windows that are used to produce the output. More overlaps can make smooth passages sound smoother. For percussive sound, a lower overlap may be better. The value of overlap is directly proportional to CPU cost.kNewTimePitchParam_EnablePeakLocking - Peak locking enforces phase coherence of spectral peaks. While it does add some expense, peak locking results in a less phasey or reverberant sound (sometimes also called loss of presence).// Parameters for AUNewTimePitch CF_ENUM(AudioUnitParameterID) { // Global, rate, 1/32 -> 32.0, 1.0 kNewTimePitchParam_Rate = 0, // Global, Cents, -2400 -> 2400, 1.0 kNewTimePitchParam_Pitch = 1, // Global, generic, 3.0 -> 32.0, 8.0 kNewTime

I'd like an Image subview of a lock screen widget to render as itself, and not with the multiply-like effect it gets today. I've tried .widgetAccentable(true) and .widgetAccentable(false), but none have the appearance I'm looking for. Is there maybe a new modifier that lets me force the rendering mode? Hoping there is and it's just not jumping out at me. Thanks for your help.

I am using AVFoundation framework and more specifically AVPlayer along with AVPlayerItem to play an audio content. I am also setting AVAudioSession.sharedInstance().setCategory(AVAudioSessionCategoryPlayback), AVAudioSession.sharedInstance().setActive(true), MPNowPlayingInfoCenter.default().nowPlayingInfo = // some value and using MPRemoteCommandCenter commands. As usual it is showing a default player on iPhone lock screen as shown in figure.My question is once the playback of audio is finished the default iPhone lock screen player does not goes away. I am resetting all the above info e.g AVAudioSession.sharedInstance().setActive(false) and MPNowPlayingInfoCenter.default().nowPlayingInfo = nil and audioPlayer.replaceCurrentItem(with: nil) etc. How can I make this lock screen player hide after the playback is finished.

In 10.1 beta (14B72), my game center connection logs me out and fails to reconnect until I reboot of the device (iPhone 6S+). When the lockout occurs, I go into settings and select the Game Center setting, it locks up the settings app entirely - the Game Center selection remains grey to indicate my selection, but the view never changes and I cannot select or scroll the settings view. I can return to the home screen, but then going back to settings brings up a blank view (apparently its still locked up in GameCenter). Eventually it appears to timeout or crash the settings, after which the settings can be reopened successfully, but game center remains unable to connect.

Hello! I am trying to make my complication update info every second, so I could create a timer in it. I already found a solution that helps me to create a timer let components = DateComponents(second: 10) let futureDate = Calendar.current.date(byAdding: components, to: Date())! Text(futureDate, style: .timer) but I want to make a breath timer, so I need to change it to 5 sec timer and then again to 10 sec. Is there any solution that would allow me to update the info that shows in the new iOS 16 Lock Screen Widget in this way?

Hello, I have a ready-made developer account, there are published applications, now I go in to publish a new application and it says that I need to accept the agreementI click on this and go to the developro account and there it says Sorry, you are already a member of the development team, what should I do?

Is there a way to figure out from code if a user account is actually a mobile account or active directory account or local user account (non-mobile) on Mojave?Through following code i can distinguish between local user and AD user via attribute // 'dsAttrTypeStandard:AppleMetaNodeLocation': '/Local/Default' for Local user // 'dsAttrTypeStandard:AppleMetaNodeLocation': '/Active Directory/ABCD/abcd.in' for Domain userfunc checkForLocalUser(name: String) -> Bool { var records = [ODRecord]() let odsession = ODSession.default() do { let node = try ODNode.init(session: odsession, type: ODNodeType(kODNodeTypeAuthentication)) let query = try ODQuery.init(node: node, forRecordTypes: kODRecordTypeUsers, attribute: kODAttributeTypeRecordName, matchType: ODMatchType(kODMatchEqualTo), queryValues: name, returnAttributes: kODAttributeTypeAllAttributes, maximumResults: 0) records = try query.resultsAllowingPartial(false) as! [ODRecord] } catch { let errorText = error.localizedDescripti

It's fairly well know and stated that the Apple Health / HealthKit data store is unavailable when iPhone is locked. Since Lock Screen Widgets were introduced there's been a feature parity mismatch with Apple's own Fitness app which is able to display updating Activity Rings on the Lock Screen. Third party apps cannot do this and have to rely unlocking their device to then trigger an update. This means they often display stale and wrong Health data. With the release of iOS 18 beta, I see no changes to this... Is there anything I've missed? Currently for requesting the Timeline Updates on my Widget I have to just keep requesting updates as often as possible and hope that each time the iPhone might be unlocked.... This is inefficient and a waste of device resources. Even a Widget timeline reload API that let the developer say Only call update if iPhone unlocked would be useful.

Hi,I'm trying to differentiate when a user is using their phone (e.g., on Google or another app) vs when a user is on the lock screen. We're trying to prevent cheating for our bar trivia app and in order to do this we need to know when the players are searching for Google for answers or they're just on the lock screen. Would love your thoughts and feedback on this!Thanks,Evan

The new account deletion requirements stated in the app review guidelines (5.1.1(v)) state that: If your app supports account creation, you must also offer account deletion within the app. But what about if the account is owned by a different entity than the user itself, such as for someone using a work account that is owned by their employer? Are we still obligated to offer the employee a way to delete their account within the app?

Hello friends, For our application development on macOS (& also IOS), we need advisory locks which are 'File Descriptor' specific locks and not process specific. It is also important that they should support byte-range locking & shared/exclusive locking. Additionally, the same process can take multiple byte-range locks at the same time to support various combinations. Basically, we want to coordinate between multiple processes reading/writing to the same file simultaneously using advisory locks (byte-range & shared/exclusive). And we want to give flexibility to users to give file paths with all combinations like using ‘soft/hard links’, network shared file paths, etc. We see that 'fcntl ()' system call comes closest to our requirement. However, locks taken using standard commands FSETLK/ FGETLK, are process-specific locks & not file descriptor specific lock. That means, assuming one file descriptor has taken a byt