Not sure if this is the proper place to post this. In quotes below is what I posted on the regular forum but it was removed when I used the word 'beta' - didn't know that was an issue. The email then sent me here. Updated both my MacBook Pro (M1, Late 2020) and my iPhone 13 Pro with the new Tahoe 26 Public Beta and now my phone number is unavailable for iMessage and FaceTime It's listed on the website for sign in to the account, but now messages on my different devices don't sync and I can't send from my number or receive messages in new threads to my number. After an hour or so of digging online I called their support - who didn't know about Tahoe. The best he could tell me is wait 24 hours for the system to catch up. Sigh. It's the same number I've had since (well before) iPhone 2 when I first set up the account. I've been doing the betas since they've been available, and I expect quirks and issues. I've just never had an issue this invasive. Follow up - existing threads still seem to work
Search results for
Account Locked
31,782 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Hello forum, Hope you all are doing great! We’ve implemented Live Activities in our iOS app to display live soccer scores on the lock screen. The feature generally works as expected when the app is in backgroun or app is invoked when the push is sent. However, we’re observing an issue affecting approximately 20–30% of users where the Live Activity starts successfully but no subsequent score or commentary updates are received. Upon investigation, it appears the OS is not waking the app when the Live Activity starts. This wake-up is critical for syncing the activity token with backend service we use, which is required for delivering updates. Key Points: Starting a Live Activity does not require the app to be invoked since we start with Push token However, for updates to be delivered, the app must be woken at the start to send the latest pushh token to Backend. In affected cases, even manually sending a background push does not wake the app—it remains terminated until manually opened by the user. We’d l
@DTS Engineer I created the post on the correct account. On which the Xcode cloud was working at the beginning of July, but has now stopped working.
Topic:
Developer Tools & Services
SubTopic:
Xcode Cloud
Tags:
@DTS Engineer I created a post from the wrong account. The account I have access to has a signed PLA, and everything is fine with it. But there is still a problem.
Topic:
Developer Tools & Services
SubTopic:
Xcode Cloud
Tags:
Hi Ziqiao, Thanks for your detailed reply – and you’re absolutely right. You’re correct that the .shared option in ModelConfiguration(cloudKitDatabase:) isn’t supported and doesn’t compile. I had initially hoped it might be possible based on how .automatic behaved for syncing within the same Apple ID, but now I understand the limitation more clearly. So to clarify: • The sharing that “worked” was actually just syncing across devices with the same Apple ID using the private CloudKit DB. • When testing across multiple Apple IDs, it failed with the well-known “Bad Container” and CKShare-related errors. • After discussing with DTS, I’ve started converting the app to Core Data + CloudKit + Sharing, using UICloudSharingController and manual CKShare handling. The full transition is still in progress, but I’m hopeful that this approach will finally allow working sharing between different iCloud accounts. Thanks again for your support — it really helps to get direct feedback on what’s supported and what’s not
Topic:
App & System Services
SubTopic:
iCloud & Data
Tags:
Hi everyone, I’m currently unable to view crash logs in Xcode Organizer for any of the apps in my account. When I try to access crash reports, I receive the following error: An error occurred preventing Xcode from downloading version information from App Store Connect. An unexpected error occurred: [<__NSDictionaryM> valueForUndefinedKey:]: this class is not key value coding-compliant for the key [App Name] [Version] (iOS App). The error message references an app name and version that were previously used. Notably, the original app name included an @ symbol (e.g., @ExampleApp). We suspected this might be contributing to the issue, so we updated the app name to remove the symbol. However, the error persists and still references the old name. Has anyone experienced something similar or found a workaround? Any guidance would be greatly appreciated! Thanks in advance.
We started seeing an access issue today when attempting to go to the Xcode Cloud tab in App Store Connect. When you navigate to https://appstoreconnect.apple.com/teams/:teamId/apps/:appId/ci we're seeing the following message: The page you’re looking for can’t be found. The page you’re looking for does not exist, or you do not have permission to view it. I am the account holder so it shouldn't be a permissions issue. Is there an ongoing outage or problem in Xcode Cloud? And, if so, where can I monitor this accurately?
Hello Apple Developer Program, Every year this banner shows up, I would follow the link and update my card. It's never expired! My Apple account is able to charge my monthly iClould+ just fine. How come, it can't charge my apple developer account?
My general advice is that you not try to manually manage Apple Development signing identities. Rather, lean in to Xcode’s automatic signing feature. Try this: Log in to Xcode > Settings > Account with your developer account. Create a new project from the iOS > App template. In Signing & Capabilities, make sure that automatic signing is enabled and you’ve selected your team from the popup. Build and run on the simulator, just to check that the basics are working. Now try to build and run on your attached device. Does that work? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Just a couple of factoids to expand on the previous answers… If your Apple Account is not a member of a paid developer team then Xcode lets you develop apps for your own device. This feature is known as a Personal Team. It has significant limitations. For the specifics, see Developer > Support > Choosing a Membership. If you’re using a Personal Team, it’s a good idea to bookmark the Developer Account Help > Reference > Supported capabilities (iOS) page. The last column, labelled Apple Developer, shows what entitlements are available to Personal Team developers. Sadly, Family Control is not in that list )-: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
Code Signing
SubTopic:
Entitlements
Tags:
I have the same problem! In support advised 1. Sign out of Xcode and sign in again. 2. Quit Xcode, restart, and then open it again. 3. Verify that the account credentials you are signing in with are correct. 4. Confirm that Xcode and macOS versions are up to date. This is ridiculous.
Topic:
Developer Tools & Services
SubTopic:
Xcode Cloud
Tags:
i'm trying to work on a simple screen recording app on macOS that always records the last 'x' seconds of your screen and saves it whenever you want, as a way to get comfortable with swift programming and apple APIs. i was able to get it running for the past '30 seconds' and record and store it. however i realised that there was a core issue with my solution: i was defining the SCStreamConfiguration.queueDepth = 900 (to account for 30fps for 30 seconds) which goes completely against apple's instructions: https://developer.apple.com/documentation/screencapturekit/scstreamconfiguration/queuedepth?language=objc now when i changed queueDepth back to 8, i am only able to record 8 frames and it saves only those first 8 frames. i am unsure what the flow of the apis should be while dealing with screenCaptureKit. for context, here's my recording manager code that handles this logic (queueDepth = 900) import Foundation import ScreenCaptureKit import AVFoundation class RecordingManager: NSObject, ObservableObjec
Hi, Currently, instead of using a real device and test account for in-app purchase testing, we are using Products.storekit with the Simulator. Our app offers a subscription plan with a 3-day free trial. We would like to simulate the following test scenarios: User cancels the subscription within the 3-day free trial period. User cancels the subscription after the 3-day free trial period. However, in Xcode, under Debug > StoreKit > Manage Transactions..., we couldn’t find an option to simulate a subscription cancellation. There is an option to refund the purchase, but we believe this is not the same as a cancellation. Do you have any idea how we can simulate these two cases using Products.storekit and the Simulator? Thanks in advance!
I am experiencing an issue where Xcode Cloud is not available in my Apple Developer Program account on App Store Connect. Despite having an active developer membership, I cannot access or enable Xcode Cloud for my apps. Could you please assist me in understanding why this feature is not available for my account and what steps I need to take to enable it?
I cannot explain how frustrating this is. Not that I want to compare to Android, but in 3 years of QA Testing my app, Android works like a dream, while iOS fights with me EVERY SINGLE STEP OF THE WAY. Hopefully someone here can tell me what I am missing/doing wrong/which god I must appease to get this to work. I have 3 REAL iPhones of varying iOS versions and ages. But they are all proper actual iPhones. We use google accounts at this company, so my primary email is a gmail one. I have created MANY sandbox accounts inside App Store Connect. Currently I have 2, and 2 of my devices (both 14's one of which is a Pro) have my Primary account as the main account for the device. But they both also have a Sandbox account which is simply my main email with a +sandbox in it to make it a new unique email. Here is the problem, nothing works as expected ever. I can install my Staging and Production apps from TestFlight, then I can make a subscription purchase as a customer woul