But only until the update to iOS 18.0.1 came along just a few weeks later. EVERY TIME there's an update it breaks family share and screen time. EVERY TIME single time! And to fix, you must have the kid's phone in hand (easier for parents with little kids, not so easy with teens, also not easy for kids whose parents are split up and kid spends one week with you and one week with other parent). Then you have to make sure they are both on the same iOS version, then you have to log into iCloud and set up family sharing all over again. THIS SUCKS. Apple you can do better.

My games on my ipad 9th generation are constantly crashing they weren’t doing this before on the iOS 17 update but I haven’t seen change on my phone either, the games will sometimes say I don’t have enough storage but I’ll check my storage and I have 30gbs free of storage and the games I am playing are small games that aren’t even more than a 1 gb or 5 gb’s I just want to know if it’s because of the update because I seen ios 18.1 came out and it was suppose to allegedly fix that and I started playing it hasn’t work I even tried hard resetting my iPad that didn’t work either I’ve honestly given up and I’m thinking about going back to target and getting one that hasn’t been updated yet because this is outrageous

RCS not active on Airtel or Jio sim on iPhone even on ios 18.1 developer Beta

In my React Native mobile application, we are experiencing app termination issues on a few devices (iPhone 13 & 14). We have implemented Firebase Crashlytics, we are getting crashes logs but we are not receiving any logs for app terminations when app terminates due to memory leak or terminates by OS. Could you please suggest a way to log app terminations or recommend any other platform where we can log such events? Alternatively, do you have any suggestions on how to resolve app termination issues?

test to check view inflation, POC.

Locked phone -> Face ID unlocking (without swapping up to home page) -> The phone stays unlocked and wait for swapping up endlessly (don’t locking after the setted aut. locking period). Sorry for the bad english - I hope you will understand what is the bug.

after I updated to iOS 18, I can toggle the cellular data on and off for specific apps in settings, and it doesn’t have an effect. For some apps it’s turned on and if I turn it off, it doesn’t have any effect it stays on and other apps it’s turned off and I even if I turned cellular data for that app doesn’t work It keeps turning it off itself. Is there just a setting I missed, or?

I used to be able to dictate via Siri and it was fine. Now that I’ve switched to iPhone 16 pro max, it’s full of errors. I can dictate and it adds capital letters where there should not be. It adds periods and commas the middle of sentences where they shouldn’t be. If I pause normally as I’ve always done, it deletes All that I’ve dictated and starts over (Notice the capital A in the sentence where it should not be). Even when I’m typing, it adds capital letters For no reason. I was trying to dictate a common word earlier and Siri would not recognize that word. I reset Siri and reset dictation and it’s still buggy. The phone is updated. I had the iPhone 13 Pro Max prior to this phone and didn’t have these issues.

Yesterday all of a sudden the timezone on my iPhone has changed (being on "Automatic") for an unknown reason. I put it on manual, selected my current timezone and the switched back to Automatic and put me back to this irrelevenat to me timezone. My "medications" have been affected by that, and even though I keep it now on manual, they are not fixed.

Hello all, I recently shared a post to Reddit r/iCloud "Apple Alias Converted to Primary Apple Account" about an experience I had with changing my primary iCloud address to my alias after a name change. All the outlets have picked up on this story which may be misleading. I was under the impression this may be a bug, and now everyone's replicating this process without precaution. My question to the amazing Apple Developers and potentially Apple as well: Is the ability to change your Primary Apple Account to an Apple Alias (permanently) a known, previously discussed, upcoming feature? All Apple docs & support state otherwise. Really just seeking confirmation and I greatly appreciate expert input. Also happy to change Tags based on feedback (if possible). Thanks all! Caol

i have had iPhone 16 pro since 09252024, and the following issues pop up in turns everyday: Camera crashes and the device doesn’t response. I have to restart to restore the function. Outgoing and incoming voice messages have no sounds. Initially, I thought it was because of the message app; however, I tried to record my voice with voice Memos, Still no sounds, so I figured it’s the microphone. I sometimes have to restart iphone 2-3 times to fix the issue. The device gets hot and slow without background apps running. I can not figure out the cause. For example, after I woke up this morning and picked up my phone to look at some websites. The phone became hot and slow in just a few minutes. Again, after I restarted it, the issue resolved. Do I pay over $1,100 to constantly restart my iPhone to have it work? i have contacted Apple service teams for hundreds of times since last week; however, I have found it’s extremely hard to get proper help. Initially, I chose chat service and was transferred from tech support to Apple care then to sales department. Sometimes the connection lost, so I had to repeatedly tell the new person what has happened. Then I was told to call their senior advisor, who again asked me“how can I help you”, so I told him what’s going on and I chatted with other agents, who advised me to call instead because their limited access, and if he needed more info, he could look at the chat history or notes. Surprisingly, this person mocked:” I went over the previous chat and noticed that you have contact us for 20 times!” I told him that before I talked to him, I only contacted Apple once and was transferred to different department and still can not get help. Then he again asked me:” how can I help you”? I said I told you already and you said you reviewed the chat history, why are you asking me again? he said he wanted to hear from me, so I repeated again, then he asked the same thing again, so we were doing this back and fort for a few times. Finally, I was really ****** off, so I shouted to him and hung up because I had to go back to work. Later, I chatted with Apple service again, and this tech support said they needed to run a diagnostic test for my phone, but they could only give me verbal advice regarding the result and recommendation instead of proving a detailed written report. I felt this does not make any sense! For example, if we go to our car dealer to fix our car, the advisor will give us a written report and advices., so we can see what’s the issue and make suitable decision. Why can not Apple do this? How do I know if what they tell me is true without anything in writing? Apple’s explanation to this is this is what Apple does! Of course, I did not accept this and ask if this defective phone can be replaced. Then I was transferred to another person, who told me a replacement for my phone was initiated and I would receive an email within 24-48 hours. I was so happy and waited and waited for 3 days! No email came! I contacted Apple again and was told my phone was still in warranty, but I had to send my phone first to Apple and to have it inspected. If it’s eligible, a replacement would be sent to me. I refused because i simply can not function without my cellphone:) Then I did research online and found out Apple care offers a service called express replacement, which can send a new phone to me first, then have me return the defective one, so I bought Apple care and called Apple again, but I was told one more time that they had to run a diagnostic before further action! The above is just simplified story because I don’t want to waste more time to write down all the details. It’s also worth to mention that during my numerous contacts with Apple: my chat repeatedly got disconnected, so I had to repeat my request to new agents; when I called, 2-3 times, my call was hung up by their agent; or one of the agents told me she could not see any devices associated with my account; and every time I was transferred to a new department, I had to identity myself and repeat my request despite the fact that I had verified with Apple’s automatic voice assistant and previous agents. another issue is different agent even from the same department told me different solutions and policies. Nothing in writing can express my frustration and disappointment. I do not understand how a good company has become like this, both product quality and cus service quality.

I'm developing an iOS application using Xcode 15.3 and Firebase SDK 11.3.0. My app utilizes Firebase Realtime Database to monitor changes in foodEntries through Firebase observers. Here's a simplified overview of my implementation: Setting Up Observers: I set up Firebase observers to listen for changes in the foodEntries node. This allows my app to react in real-time to any additions or modifications. Monitoring Connection Status: I check the Firebase connection status whenever the app becomes active. Additionally, I track the network connection using NWPathMonitor to handle connectivity changes. Issue: When I send the app to the background and then bring it back to the foreground, I occasionally encounter the following error in the console. This happens approximately once in ten attempts: 2024-10-10 17:49:08.588502+0200 MyApp[22614:2112636] [[FirebaseDatabase]] 11.3.0 - [FirebaseDatabase][I-RDB083016] Error sending web socket data: Error Domain=NSPOSIXErrorDomain Code=89 "Operation canceled" UserInfo={NSDescription=Operation canceled}. Consequences: Once this error occurs, my app stops receiving updates from the Firebase observers. The observers' closure callbacks are no longer triggered, effectively halting real-time data synchronization. Additionally, the Firebase connection status change is not triggered when this happens. Temporary Workaround: Interestingly, the issue resolves itself when I send the app to the background and then bring it back to the foreground. This action seems to reset the Firebase connection, allowing observers to function correctly again until the error reoccurs. What I've Tried: Reinitializing Observers: Attempted to remove and re-add observers upon detecting connection issues. Connection Monitoring: Implemented NWPathMonitor to track network changes and attempt reconnections. Error Handling: Tried catching errors during data operations to trigger retries or reconnections. Despite these efforts, the Operation canceled error persists and disrupts the observer functionality. Sample Code: Here's how I set up the Firebase observers and monitor the network connection: `import FirebaseDatabase import Network import Combine class UserData: ObservableObject { private let monitor = NWPathMonitor() private let networkQueue = DispatchQueue(label: "NetworkMonitor") private var cancellables = Set() @Published var isAppFirebaseConnected: Bool = false @Published var isAppNetworkConnected: Bool = false init() { setupFirebaseMonitoring() startNetworkMonitoring() } private func setupFirebaseMonitoring() { let db = Database.database().reference() let connectedRef = db.child(".info/connected") connectedRef.observe(.value) { [weak self] snapshot in if let connected = snapshot.value as? Bool { DispatchQueue.main.async { self?.isAppFirebaseConnected = connected if connected { print("Firebase is connected.") // Initialize observers here self?.initObservers() } else { print("Firebase is disconnected.") self?.removeObservers() } } } } } private func startNetworkMonitoring() { monitor.pathUpdateHandler = { [weak self] path in let isConnected = path.status == .satisfied DispatchQueue.main.async { self?.isAppNetworkConnected = isConnected print("Network connection status: \(isConnected ? "Connected" : "Disconnected")") if isConnected && self?.isAppFirebaseConnected == false { // Attempt to reconnect Firebase if needed self?.reconnectFirebase() } } } monitor.start(queue: networkQueue) } private func initObservers() { let db = Database.database().reference() db.child("foodEntries").observe(.childAdded) { snapshot in // Handle new food entry print("New food entry added: \(snapshot.key)") } db.child("foodEntries").observe(.childChanged) { snapshot in // Handle updated food entry print("Food entry updated: \(snapshot.key)") } } private func removeObservers() { let db = Database.database().reference() db.child("foodEntries").removeAllObservers() print("Removed all Firebase observers.") } private func reconnectFirebase() { print("Attempting to reconnect Firebase...") Database.database().goOffline() DispatchQueue.main.asyncAfter(deadline: .now() + 1.0) { Database.database().goOnline() } } }` Problem Description: Observers Stop Working: After some time, the Operation canceled error appears, and the Firebase observers stop receiving updates. No Triggered Closures: The closure callbacks for .childAdded and .childChanged are no longer invoked. Manual Reset Required: Backgrounding and foregrounding the app temporarily fixes the issue by resetting the Firebase connection. Question: How can I prevent the NSPOSIXErrorDomain Code=89 "Operation canceled" error from disrupting Firebase Realtime Database observers in my SwiftUI app using Xcode 15.3 and Firebase SDK 11.3.0? Additionally, how can I effectively track and handle network connectivity changes to ensure that Firebase observers remain functional without requiring manual app state resets? What I Need Help With: Understanding the Cause: Insights into why the Operation canceled error occurs and how it affects Firebase's WebSocket connections. Robust Error Handling: Best practices for handling such network-related errors to maintain continuous observer functionality. Network Monitoring Integration: Examples or suggestions on effectively integrating network monitoring to trigger Firebase reconnections when necessary. Alternative Solutions: Any alternative approaches or configurations that can mitigate this issue. Additional Information: Firebase Configuration: I'm using default Firebase configurations and have enabled offline persistence. Device Environment: The issue occurs on both simulators and physical devices with stable internet connections. App Lifecycle Management: Observers are set up when the app becomes active and removed when it resigns active, as shown in the sample code. Any guidance or examples on handling this Firebase connection error and maintaining observer reliability would be greatly appreciated!

Hi, My project was compiling and running absolutely fine on Xcode 15.4. I upgraded to Xcode 16.0 from appstore and when I run, I'm getting following compilation error. Cleared derived data etc I have tried everything now. Can someone pls help in getting rid of this issues. Showing Recent Issues SwiftCompile normal arm64 Compiling\ DefaultValue.swift,\ Factory.swift,\ ClassHeader.swift,\ ClassMetadataLayout.swift Apple Swift version 6.0 (swiftlang-6.0.0.9.10 clang-1600.0.26.2) Compiling with effective version 5.10 Stack dump without symbol names (ensure you have llvm-symbolizer in your PATH or set the environment var LLVM_SYMBOLIZER_PATH to point to it): 0 swift-frontend 0x00000001064630fc llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) + 56 1 swift-frontend 0x0000000106461350 llvm::sys::RunSignalHandlers() + 112 2 swift-frontend 0x00000001064636c8 SignalHandler(int) + 292 3 libsystem_platform.dylib 0x0000000195478184 _sigtramp + 56 4 libsystem_pthread.dylib 0x0000000195442f70 pthread_kill + 288 5 libsystem_c.dylib 0x000000019534f908 abort + 128 6 swift-frontend 0x00000001011c6bc8 createDispatchingDiagnosticConsumerIfNeeded(swift::FrontendInputsAndOutputs const&, llvm::function_ref<std::__1::unique_ptr<swift::DiagnosticConsumer, std::__1::default_deleteswift::DiagnosticConsumer> (swift::InputFile const&)>) + 0 7 swift-frontend 0x00000001063d2e80 llvm::report_fatal_error(llvm::Twine const&, bool) + 280 8 swift-frontend 0x00000001063d2d68 llvm::report_fatal_error(llvm::Twine const&, bool) + 0 9 swift-frontend 0x000000010140731c llvm::detail::PassModel<llvm::Module, llvm::VerifierPass, llvm::PreservedAnalyses, llvm::AnalysisManagerllvm::Module>::printPipeline(llvm::raw_ostream&, llvm::function_ref<llvm::StringRef (llvm::StringRef)>) + 0 10 swift-frontend 0x000000010619aa80 llvm::PassManager<llvm::Module, llvm::AnalysisManagerllvm::Module>::run(llvm::Module&, llvm::AnalysisManagerllvm::Module&) + 224 11 swift-frontend 0x00000001013fbd58 swift::performLLVMOptimizations(swift::IRGenOptions const&, llvm::Module*, llvm::TargetMachine*, llvm::raw_pwrite_stream*) + 3764 12 swift-frontend 0x00000001013fd994 swift::performLLVM(swift::IRGenOptions const&, swift::DiagnosticEngine&, llvm::sys::SmartMutex, llvm::GlobalVariable, llvm::Module*, llvm::TargetMachine*, llvm::StringRef, llvm::vfs::OutputBackend&, swift::UnifiedStatsReporter*) + 2352 13 swift-frontend 0x0000000100e12c7c generateCode(swift::CompilerInstance&, llvm::StringRef, llvm::Module*, llvm::GlobalVariable*) + 368 14 swift-frontend 0x0000000100e0e114 performCompileStepsPostSILGen(swift::CompilerInstance&, std::__1::unique_ptr<swift::SILModule, std::__1::default_deleteswift::SILModule>, llvm::PointerUnion<swift::ModuleDecl*, swift::SourceFile*>, swift::PrimarySpecificPaths const&, int&, swift::FrontendObserver*) + 2316 15 swift-frontend 0x0000000100e0cf74 swift::performCompileStepsPostSema(swift::CompilerInstance&, int&, swift::FrontendObserver*) + 984 16 swift-frontend 0x0000000100e10228 performCompile(swift::CompilerInstance&, int&, swift::FrontendObserver*) + 1680 17 swift-frontend 0x0000000100e0ef58 swift::performFrontend(llvm::ArrayRef<char const*>, char const*, void*, swift::FrontendObserver*) + 3572 18 swift-frontend 0x0000000100d9601c swift::mainEntry(int, char const**) + 3680 19 dyld 0x00000001950c0274 start + 2840 Command SwiftCompile failed with a nonzero exit code Command SwiftCompile failed with a nonzero exit code

The Tapback emojis are blue the only one with color is the heart i can see responses in color and the recipient sees mine in color it’s just on my end

Link to Download apps: https://apps.apple.com/us/app/pingid/id891247102 the circle rotates and again gives me the “Get” button.

Issues with connectivity to a secured wifi.

I bought my M2 MacBook Air in December 2022, and now, in October 2024, it's showing that I have no storage left. I have the 256GB, 8GB RAM model. My daily activities are fairly simple—primarily using Safari and Chrome for reading papers and light graphic design in Affinity Designer. However, in just a few months, my Mac has accumulated 170GB of data under "Other Users and Shared," "macOS," and "System." 170GB out of 245GB is absurd—can anyone help me clear this up?

`// PCM -> AAC AudioBufferList* convertPCMToAAC (XDXRecorder *recoder) { UInt32 maxPacketSize = 0; UInt32 size = sizeof(maxPacketSize); OSStatus status; status = AudioConverterGetProperty(_encodeConvertRef, kAudioConverterPropertyMaximumOutputPacketSize, &size, &maxPacketSize); // log4cplus_info("AudioConverter","kAudioConverterPropertyMaximumOutputPacketSize status:%d \n",(int)status); AudioBufferList *bufferList = (AudioBufferList *)malloc(sizeof(AudioBufferList)); bufferList->mNumberBuffers = 1; bufferList->mBuffers[0].mNumberChannels = _targetDes.mChannelsPerFrame; bufferList->mBuffers[0].mData = malloc(maxPacketSize); bufferList->mBuffers[0].mDataByteSize = kTVURecoderPCMMaxBuffSize; AudioStreamPacketDescription outputPacketDescriptions; UInt32 inNumPackets = 1; pthread_mutex_lock(&pcmBufferMutex); status = AudioConverterFillComplexBuffer(_encodeConvertRef, encodeConverterComplexInputDataProc, pcm_buffer, &inNumPackets, bufferList, &outputPacketDescriptions); pthread_mutex_unlock(&pcmBufferMutex); if(status != noErr){ // log4cplus_debug("Audio Recoder","set AudioConverterFillComplexBuffer status:%d inNumPackets:%d \n",(int)status, inNumPackets); free(bufferList->mBuffers[0].mData); free(bufferList); return NULL; } if (recoder.needsVoiceDemo) { OSStatus status = AudioFileWritePackets(recoder.mRecordFile, FALSE, bufferList->mBuffers[0].mDataByteSize, &outputPacketDescriptions, recoder.mRecordPacket, &inNumPackets, bufferList->mBuffers[0].mData); // log4cplus_info("write file","write file status = %d",(int)status); if (status == noErr) { recoder.mRecordPacket += inNumPackets; } } return bufferList; } ` The above code for converting PCM to AAC works normally in iOS versions below 18, but in iOS 18, crashes occur during the conversion process. The console does not provide much useful information, and the application crashes at malloc(maxPacketSize) or AudioConverterFillComplexBuffer(), displaying the message AURemoteIO::IOThread (14): EXC_BAD_ACCESS (code=1, address=0x0). Please help identify the cause of the crash.

If user has made any app hidden and set Face ID to open it; if user removes the requirement of Face ID to open the app, user will not able to see the app again on home screen. However, app is still on the device and can be found by searching the app name.

I am encountering a problem with HealthKit authorization in my app. In a previous version of the app, write permission for HKWorkoutType was already granted. In the new version of the app, I added a request for read permissions for both HKWorkoutType and HKWorkoutRoute. After updating the app, the following occurs: I can successfully fetch workout data using HKSampleQuery, and authorizationStatus(for: HKObjectType.workoutType()) returns .sharingAuthorized, indicating that the app has access to the data. However, when I check the Health app (Settings -> Health -> Data Access & Devices -> [App Name]), the read permission does not appear in the list. The write permission is still visible, but the newly requested read permission is missing. This behavior is unexpected because, despite being able to access the data programmatically, the read permission is not listed in the Health app settings. I have already verified that I am requesting the read permissions correctly in the code using requestAuthorization for both HKObjectType.workoutType() and HKObjectType.seriesType(forIdentifier: .workoutRoute). I would appreciate guidance on why this issue is occurring and how to ensure that read permissions are displayed correctly in the Health app settings.