== PREVIEW UPDATE ERROR: JITError ================================== | NoBuiltTargetDescriptionCouldBeFound | | translationUnit: PreviewTranslationUnit(moduleNamePrefix: Previews_EmptyFeedRow, sourceIdentifier: file:///Users/bryananderson/Developer/JournalApp/JournalApp/Interface/Feed/EmptyFeedRow.swift -> EmptyFeedRow.swift, parseTree: ParseTree(version: 727, statements: 3, providers: 1), update: nil, changesContextMemoizer: PreviewsPipeline.PreviewTranslationUnit.(unknown context at $34b4b9c4c).ChangesContextMemoizer(parseTree: ParseTree(version: 727, statements: 3, providers: 1), sourceIdentifier: file:///Users/bryananderson/Developer/JournalApp/JournalApp/Interface/Feed/EmptyFeedRow.swift -> EmptyFeedRow.swift, cachedValue: os.OSAllocatedUnfairLock>(__lock: Swift.ManagedBuffer, __C.os_unfair_lock_s>)), registryDeclarationMemoizer: PreviewsPipeline.PreviewTranslationUnit.(unknown context at $34b4b9bec).RegistryDeclarationMemoizer) | | builtTargetDescriptions: | == VERSION INFO: Tools: 16A5171c
Apple Maps Guides
135,579 results found
Post
Replies
Boosts
Views
Activity
Reviving an old thread here, but. When it was called bugreport.apple.com, I was getting reponses from Apple Devs somwhat frequnty, even if just closed as dupes. Now, with the Feedback Assistant, there's no luck if you are on a stable release at all. And I won't force myself onto beta releases without being a paid QA engineer for them. Indeed a sad state for honest people wanting to report bugs and for the once legendary quality of software.
It's clearly a bug on Apple side. For now, you will just have to revert to Xcode 16.1.
Apple has made Xcode 16.2 beta 3 the Latest Release on Xcode Cloud so a lot of builds are failing. @DTS Engineer this needs to be fixed If your builds are failing, just revert to Xcode 16.1 in your workflow ✅
Thanks, all helpful links and I will read them. When I was talking about PENDING and APPROVED, I was talking about developer membership when looking at my account info. I used my credit card to pay for the one-year membership on the apple store Tuesday, and got an email my card was charged (from my bank) However, upon checking today that charge was never sent for clearance by Apple to my bank, for unknown reasons, so it was not on my charges today as PENDING or POSTED. So I withdrew that membership and redid the payment today, so let's see tomorrow morning if Apple puts the charge through tonight!
Seems like this is back with iOS 18 & 18.1 (so far...). I had to reset everything for my app in the production environment so wiped the iCloud data, reset everything then reinstalled and imported my data into the primary device (iPhone) Sync completed after a day or so, then I installed the app on the iPad. Sync starts and appears to be doing something then nothing appears to happen for a while (maybe 20 minutes), then the app crashes again. No further data appears to have been downloaded. This happens every time I restart the app. Sigh... It's as though it's trying to do 'everything at once' for the initial sync instead of incremental syncs in small batches... and then it drops out. EDIT: Apple censored the word for 'drops out' that I used (ie. the thing they drop from planes) and substituted it with five asterisks - seriously? What puritanical nonsense is this??
Background I have an established app in the App Store which has been using NSPersistentCloudkitContainer since iOS 13 without any issues. I've been running my app normally on an iOS device running the iOS 15 betas, mainly to see problems arise before my users see them. Ever since iOS 15 (beta 4) my app has failed to sync changes - no matter how small the change. An upload 'starts' but never completes. After a minute or so the app quits to the Home Screen and no useful information can be gleaned from crash reports. Until now I've had no idea what's going on. Possible Bug in the API? I've managed to replicate this behaviour on the simulator and on another device when building my app with Xcode 13 (beta 5) on iOS 15 (beta 5). It appears that NSPersistentCloudkitContainer has a memory leak and keeps ramping up the RAM consumption (and CPU at 100%) until the operating system kills the app. No code of mine is running. I'm not really an expert on these things and I tried to use Instruments to see if that would show
Hi @novak-ji, Please see the the following post to learn about properly configuring Sign in with Apple for the Private Email Relay Service: Gathering required information for troubleshooting Private Email Relay with Sign in with Apple https://forums.developer.apple.com/forums/thread/762828 If the information above does not resolve your issues, please follow the steps outlined above and reply here with the Feedback ID so I may begin my investigation. Cheers, Paris X Pinkney | WWDR | DTS Engineer
Hello community, In our application, we've implemented Apple ID for user authentication. Unfortunately, we forgot to register the associated domains and communication email addresses. This oversight has led to complications in email delivery via the private relay service. We've taken steps to fix the issue by reconfiguring the domains and communication email addresses. Post-adjustment, new user registrations are functioning properly. However, for users who registered before this fix, the problem persists. We followed the instructions provided on https://developer.apple.com/documentation/sign_in_with_apple/sign_in_with_apple_js/communicating_using_the_private_email_relay_service, and we also have SPF configured, which has passed validation in our administration. Has anyone encountered a similar issue, and if so, how did you resolve it? Any insights or guidance would be greatly appreciated.
I have encountered a bug for Apple log in when user's iOS version is 15 or below. After completing the user email and password correctly, the it will trigger two factor authentication pop up with the code on screen. However, it will not display the screen to let user enter the two factor pass code and have a error saying the identity is wrong. I have tried to reboot the phone and log in Apple ID again. Both methods are not working. Looking for a solution here.
For help with two factor authentication, please post in the Apple Support Community. The Apple Developer Forums are for questions about APIs and features intended specifically for developers.
same here... I have tried 3 times to pay the membership, 2 times from the desktop and once from the app. Every time I receive an email with confirmation and that it takes 2 days for the payment to be made and then nothing... I contacted apple support and they told me that something is wrong with the payment, but they did not give me any information about what the issue is and the payment is not being made... also my bank told me that no payment request has ever arrived from Apple... If I don't know what the issue is, I really don't know what to do...
Hello We've tried to purchase our membership on the 6th of November, entered valid billing information, but still didn't receive back any feedback from apple. Previously with other accounts we didn't encounter any issue, but now for some reason apple support is not answering us back (left 3 tickets, they are all open, where the oldest is open for over a week without a reply back from apple) Did anybody encounter this before? is there another way to contact apple to get their help? Thanks in advance
Hi @mattywarr, Please see the following post for more information about troubleshooting these errors: Gathering required information for troubleshooting Sign in with Apple authorization and token requests https://forums.developer.apple.com/forums/thread/762831 If you're still unable to resolve these errors, please follow the steps outlined in the post above and reply here with the Feedback ID so I may begin my investigation into your issue. Cheers, Paris X Pinkney | WWDR | DTS Engineer
I'm trying to set up Sign In With Apple on my .NET 7 Web App (Not sure how many people here use this). I followed the guide by Scott Brady here: https://www.scottbrady91.com/openid-connect/implementing-sign-in-with-apple-in-aspnet-core It reaches Apple Sign In OK, authenticates, and passes back to my server, but the callback responds with this error. OpenIdConnectProtocolException: Message contains error: 'invalid_client', error_description: 'error_description is null', error_uri: 'error_uri is null'. Googling hasn't helped much, other than I saw a post saying to wait 48 hours, which I have now done (not that that makes sense anyway). Any idea whats been done wrong? Code below, replacing sensitive data. Startup.cs .AddOpenIdConnect(apple, async options => { options.Authority = https://appleid.apple.com; // disco doc: https://appleid.apple.com/.well-known/openid-configuration options.ClientId = com.rackemapp.applelogin; // Service ID options.CallbackPath = /signi