“Account Locked”

Every time I'm on FaceTime and I lock my phone or hit the power button the FaceTime ends.

HiWill there be some ways to activate the live photo when we use the raise to wake up feature or simply press the home button on lock screen ?An option to auto play the live photo on the lock screen could be a nice and fancy feature to add to the options and could definitly have a harry potter feeling when raising the phone just to look up at the kids picture 🙂

Does anyone else have a problem responding to a message from the lock screen? My screen disappears while typing the reply. Thank youMatt

Does Apple now allow us to have our apps show on the lock screen and have access to them?Stright forward..ThanksJZ

We have an iOS app in Development with in-app purchases that works fine on iOS devices. When running the app on Apple Silicon Macs, the app locks the mouse pointer and renders its own (via GCMouse listener events). When the user selects an in-app item to purchase, the operating system displays the purchase confirmation dialog as expected, however because the pointer is still locked, users are unable to click elements on the dialog or see a pointer. I've tried running setNeedsUpdateOfPrefersPointerLocked and returning false prior to the purchase but the pointer remains locked. Is there a better way to immediately release the lock or ensure the in-app purchase dialog gets the mouse pointer? Thanks.

I have implemented the following code to create a keychain item:let keychainQuery = NSMutableDictionary(dictionary: [ NSString(format: kSecClass) : kSecClassGenericPasswordValue, NSString(format: kSecAttrService) : my_service, NSString(format: kSecAttrAccount) : my.app.domain, NSString(format: kSecAttrAccessible) : NSString(format: kSecAttrAccessibleAfterFirstUnlock), NSString(format: kSecReturnData) : my_password) let status = SecItemAdd(keychainQuery as CFDictionary, nil) if status != errSecSuccess ( print(status not success: (status)) }Unfortunately, when the iPhone is locked (press the lock button), even though the accessible element has been set to after first unlock, I get an error (-25300) when my code tries to retrieve the information stored in the keychain. The app can access information in the keychain while the app is in the background, just not when the iPhone is locked.The code to retrieve:let keychainQuery: NSMutableDictionary = NSMutableDictionary(dictionary: [ kSecClassValue:

Hi, I have a paid-up Apple dev program membership. I'm trying to debug an app on my iPad Pro. Xcode locks up when trying to generate the certificates, asked me to visit the membership site to sign the dev aagreement, I have done so and it still locks up. The dev center also locks up when I try to generate the certificates manually. What's my way out of this mess? Edmund

Our product includes a background sync process that synchronizes credentials between devices. We need to update ASCredentialIdentityStore when credentials are changed, we have noticed that the ASCredentialIdentityStore.shared.saveCredentialIdentities() fails to run when the device is locked. Is it possible to update ASCredentialIdentityStore when the device is locked?

I am not able to remove the Activation Lock through MDM. I enabled the activation lock via https://mdmenrollment.apple.com/device/activationlock My device is listed in the ABM portal and i used the provided snippet here to generate the bypass code. I am getting the SUCCESS response of the above API and the activation lock also got enabled. But while removing the above activation lock via https://deviceservices-external.apple.com/deviceservicesworkers/escrowKeyUnlock and using the same escrow key that I used in the above api while activating the lock. I got the following error everytime Though this API of clearing the activation lock works perfectly fine when I enable the user-initiated activation lock, by enabling the Find My in the device. And use the bypass code as escrow_key that we receive from the device via device querry command.

Hi,currently I'm experimenting with VoIP. I've developed a simple VoIP app using the old keep alive timeout approach (not PushKit) includinga inputstream and outputstream. The VoIP communication between my iPad and the VoIP server seems to work properly, except on a locked device.My test case is as follows:1. I start the VoIP app (which connects to the VoIP server) and then lock the device (with or without a code).2. I simulate a VoIP-Call for the device, which will be noticed (local notification on lock screen).3. I ignore the VoIP call on the deviceThis all works fine. But if I do this again and again, something like stress testing, then it seems that iOS terminates the app after a while.I cannot figure out why exactly this will be done. My considerations go from a too high CPU usage or an exceeded number of received bytes.This kind of stress testing is a little bit weird, but actually, this should work.What I've found out:- the VoIP app works fine on an unlocked device- the VoIP

Hi,I'm trying to get my SceneKit scene to lock to the floor, but if I move the phone to the table, the screen should be able to lock to the table too.I've been trying with the following code with no success, any tips?func renderer(_ renderer: SCNSceneRenderer, didAdd node: SCNNode, for anchor: ARAnchor) { guard let plane = anchor as? ARPlaneAnchor else { return } debugPrint(self.sceneView.scene.rootNode.position: (self.sceneView.scene.rootNode.position)) debugPrint(node.position: (node.position)) self.sceneView.scene.rootNode.transform = SCNMatrix4(plane.transform) }

In my App I'm using the NSFileCoordinator to read and write files to the iCloud, so they sync between devices. This works fine in general. But under iOS 11 I've noticed on my iPad (but not on my iPhone), that some times the iCloud syncing stops competely. If this happens this issue won't go away until the device is rebooted. Then evertyhing works again for some time. Some time later (days, weeks) the problem is back, iCloud sync fails completely.So I used the debugger to find out what's going on. And I noticed, when the problem occurs, all attepmts to use the NSFiIeCoordinator will lock up. For example whan calling the method coordinateReadingItemAtURL:options:error:byAccessor: the block which is called when it is safe to do the read operation is never called. The same happens for coordinated write operations. Every call to the coordinated file operations will block forever. Even if there's only one single call, so there can not be a dead-lock within the App. Is this a known issue (the fact

I'm observing all sorts of race conditions occurring in various VNOPs my custom filesystem implements. I'm inclined to attribute this to my implementation not following the locking rules expected by the system of a 3rd party filesystem as well as it should. I've looked at how locking is done in Apple's own implementation of Samba and NFS clients. The Samba client uses read/write locks to protect its node from data races. While the NFS client uses mutex locks for the same purpose. I realised that I don't have a clear model in my head of how locking should be done properly. Thus my question, what are the locking rules for VFS and VNOP operations? Thanks.