What are the steps in order to safely partition a drive to run MacOS26 for testing on my main machine without corrupting the main machine, please advise? My machine is a Mac Pro M3 Max Apple Intelligence/Foundation Models DO NOT WORK on Parallels VM. I cannot afford to buy new machines. My current one is maxed out on GPU/CPU and memory. TIME SENSITIVE

I would like to inquire about an error that has started occurring while debugging AppStore billing. (In sandbox environment) This error occurs after entering a password and completing the purchase process, and in this case, no completion alert appears. The error doesn't seem to depend on the purchase item, sandbox account, or device, and shows unstable behavior - sometimes succeeding and sometimes failing. Additionally, this error started occurring after special debugging where the network was disconnected during the purchase process. Moreover, the same error occurs in the TestFlight version of our already released normal (supposedly) version. I think this might be a sandbox-specific error where the system has temporarily become unstable, but what do you think? If so, how can I resolve this issue? I would appreciate your insights on the cause and appropriate response. Error details below: <SKPaymentQueue: 0x283b3d070>: Payment completed with error: Error Domain=ASDErrorDomain Code=500 "(null)" UserInfo={NSUnderlyingError=0x28364d770 {Error Domain=AMSErrorDomain Code=305 "Purchase Failed" UserInfo={NSLocalizedDescription=Purchase Failed, AMSStatusCode=200, AMSServerPayload={ "cancel-purchase-batch" = 1; customerMessage = "Unauthorized_message"; failureType = ""; "m-allowed" = 0; pings = ( ); }, NSLocalizedFailureReason=Server canceled the purchase}}, storefront-country-code=JPN, client-environment-type=Sandbox}

Installation has completed login is successful but after 30 secs it returns to login screen safe mode does the same. tried recovery mode and reinstalled. Still in the login loop. what are my choices now?

I noticed the water lock feature isn’t in the control center after updating to WatchOS 26

Under multiple display screens (left and right screens), when a commonly used app application clicks "Window" -> "Move to..." When it comes to this, the app cannot be completely moved to the other window but instead moves to the middle of the two Windows for display. Is this a bug of the system?

Hi, I’m experiencing a serious keyboard lag issue on my iPhone 15 Pro Max running iOS 18.4. When playing games in Roblox, if I try to type in the in-game chat using the default iOS keyboard, the typing becomes extremely laggy and drops a lot of frames. However, if I turn on Low Power Mode, the issue disappears completely, and typing becomes smooth again. This suggests that the problem may be related to background optimization or system performance handling in iOS 18.4. Open Roblox and start any game with chat input and Try typing in the chat box using the iOS keyboard than Observe serious lag and frame drops and Enable Low Power Mode.The lag disappears instantly. • iPhone 15 Pro Max • iOS version: 18.4 • Keyboard: Default iOS keyboard • Issue only occurs when Low Power Mode is OFF Please investigate this behavior. It’s very disruptive during gameplay and seems linked to performance scaling or system optimization. Thanks! My English is not very good and these are the ones I edited using Google Translate.

After doing a software update I can only view iMessages older than 12hrs (from a single contact) if the other person replies to and older message. Every time I leave the Massages app and go back in the issue occurs again.

I was searching for demo code from WWDC 2015 (Maze: Getting Started with GamePlayKit). Turns out, Apple remove the project from their website. But I finally found the project on my Mac because I must have downloaded it in the past. Does anyone know if I'm allowed to put that project to a public GitHub page without any modifications? Has anyone of you experience with this? I think it's really bad that Apple is removing those old projects. And as this particular project is in ObjC it compiles with only minor adjustments.

Hi Guys! I’ve been encountering some issues while testing the latest iOS beta. Is anyone else experiencing similar bugs? Test environment: Device enrolled in iOS 26 Beta since June 9th, 5:00 PM (BRT) Hardware-related issues: • The device is overheating during routine tasks, especially when screen brightness is set to maximum. • Battery life has dropped significantly — approximately 20% to 30% shorter compared to iOS 18.5 UX/UI issues: • Scrollbars occasionally behave erratically in some apps — scrolling leads to empty areas or becomes unresponsive. • When opening a new tab in Safari, the app sometimes freezes and requires a force restart. • The Control Center is difficult to interact with due to excessive transparency, which gives the impression that the icons are scattered without visual hierarchy.

Hi everyone, We're facing an issue with Universal Links on iOS 18 and above. The problem seems related to how iOS handles redirects before reaching a Universal Link. ✅ Working Link (direct): When we open this direct Universal Link, the app opens as expected: 👉 https://dl.punchh.com/deeplinks/logansroadhouse/ ❌ Not Working (redirected link): This marketing/tracking link eventually redirects to the above Universal Link, but on iOS 18+, it opens the App Store or a browser instead of the app: 👉 https://ip2.loyalty.logansroadhouse.com/ls/click?upn=... The same redirect link works fine on iOS 17 and below — it opens the app.

Two days ago, I tested IOS 26 on my device, but it was still overheating severely. Today, the device is very sluggish. What should I do? Or do I just need to wait...

Yo i installed IOS 26 Beta to see how it is, and I want it to downgrade but Checking for Updates are unavailable and my iPhone 14 Pro is lagging i have 20-30 fps or something like that. And these Icons don’t wanna talk about it 🙏

On recent versions of macOS (including current betas), when enabling Internet Sharing from Ethernet to Wi-Fi, the configured WPA2/WPA3 password is ignored and the shared network is broadcast as an open (unsecured) network. Steps to Reproduce: Connect Mac to Ethernet via USB/LAN adapter Go to System Settings > General > Sharing > Internet Sharing Set up Wi-Fi options with a valid WPA2/WPA3 password Enable Internet Sharing Expected Behavior: Devices should see a password-protected Wi-Fi network with a lock icon and require authentication. Actual Behavior: The network appears unsecured (no lock icon) Devices like iPhone connect without entering a password This can be verified immediately from iOS Wi-Fi settings Additional Notes: Reproducible across macOS 15.5 RC and 16.0,26.0 Developer Beta Feedback has been submitted via Feedback Assistant multiple times This is a serious security risk if used in public or shared environments Has anyone else experienced this? Any known workarounds besides terminal-level defaults or Plist edits? Thanks in advance!

When minimize an app on extended display, then plug out the extended display, the app crashes. These simple steps, make every iOS app running on Mac crash. Pls fix it.

Please expedite to Solve this bug , my Singpass is unable to launch in iOS 26. I believe this is more urgent than a new pride theme wallpaper 🏳️‍🌈

Hi all, I’m running into a persistent build issue with my Swift project ORSOFINAL after migrating from Xcode stable to Xcode-beta.app (June 2025 version). ⸻ 💥 Errors displayed: 1. C99 was enabled in PCH file but is currently disabled 2. module file .../ModuleCache.noindex/SwiftShims-AXUM98L131W4...pcm cannot be loaded due to a configuration mismatch with the current compilation 3. missing required module 'SwiftShims' ⸻ 🛠 What I’ve already tried: • xcode-select -s /Applications/Xcode-beta.app/Contents/Developer • Deleted ~/Library/Developer/Xcode/DerivedData, ModuleCache.noindex, Archives, and Products • Ran sudo xcodebuild -runFirstLaunch • Clean Build Folder in Xcode-beta • Verified Command Line Tools setting points to Xcode-beta ⸻ ❓Looking for guidance on: • Whether this is a known bug in Xcode-beta • If SwiftShims/PCM conflicts are expected between versions • Best practices to safely migrate from Xcode stable to beta for Swift-based projects Any advice is much appreciated. Thanks, Mathéo

Hey everyone, I've got a feature suggestion for iOS that I believe would significantly benefit users by optimizing battery life and data usage through more intelligent Wi-Fi prioritization. While iOS already favors Wi-Fi over cellular when available (due to its lower power consumption), there's room to enhance this behavior with more granular user control. My proposal is to introduce an explicit option: "Prioritize Wi-Fi for Energy Saving." How It Could Work Global Toggle (Settings > Wi-Fi or Settings > Battery): A simple switch that makes the iPhone more "aggressive" in maintaining a Wi-Fi connection. When active, it would reduce the likelihood of switching to cellular data during minor Wi-Fi signal fluctuations. This ensures the device stays on the more energy-efficient Wi-Fi network for longer periods, even if cellular signal is strong. This could also subtly influence Wi-Fi Assist, making it less eager to use cellular when Wi-Fi is slightly weak but still usable, prioritizing energy savings. Per-Network Option (Settings > Wi-Fi > [Network Name] > "i" icon): Adding an option like "Prioritize This Network for Energy Saving" within individual Wi-Fi network settings. This would be perfect for trusted networks like home or work, where users want to ensure maximum battery life. The iPhone would then make an extra effort to remain connected to that specific Wi-Fi network. Integration with Low Power Mode: For seamless optimization, this feature could automatically be enabled or its behavior enhanced when Low Power Mode is active, aligning perfectly with the goal of battery conservation. Key Benefits Extended Battery Life: By consistently favoring the more energy-efficient Wi-Fi radio, we minimize cellular power draw. Reduced Cellular Data Use: Helps prevent accidental or unnecessary shifts to cellular data, saving precious megabytes. Greater User Control: Gives users who prioritize battery longevity and data limits a direct tool to fine-tune their device's network behavior. This feature would be a valuable enhancement to iOS, offering users more control and a genuinely optimized experience.

Dear Apple: If a BLE advertisement carries both a 16-bit service UUIDs and a 128-bit service UUIDs along with a local name, the local name will be placed in the scan response, then when the advertisement is turned off, both the 16-bit and 128-bit service UUIDs disappear while the local name persists. Subsequently, when transmitting a new advertisement that includes the 16-bit service UUIDs and local name, the resulting advertisement contains two local names. What methods can be used to avoid having two local names appearing simultaneously?Thanks

Hey, I cant can update or downgrade to a newer Version like IOS18.5 Can someone help me? And will Apple fix that?

I am writing to report a significant battery drain issue after updating my Apple Watch SE (2nd generation) to watchOS 26.0 beta. Since the update, my watch’s battery life has drastically decreased: it goes from 100% to 0% in just 6 hours, whereas previously, under my typical usage, a single charge would last about 1.5 days. I have already tried the following troubleshooting steps without success: 1. Performed a fresh reset of the watch. 2. Reset my iPhone. 3. Disabled background app activity. 4. Enabled airplane mode and power saving mode. 5. Disabled Live Activities and Photo Memories Despite these measures, the issue persists. The battery health of my watch is at 90%, so I believe this is likely related to the software update. I am quite concerned about this situation. I have researched and noticed that similar battery drain problems were reported by beta testers of watchOS 11, and unfortunately, there appeared to be no clear resolution at that time. I rely on my Apple Watch daily, and I sincerely hope this can be addressed soon. I would appreciate your assistance in resolving this issue, as it is significantly affecting the usability of my Apple Watch. Thank you for your attention to this matter.