I turned on the opt to install the developer beta on my 15 Pro Max. It downloaded 18.1 but none of the newer features are available such as the apple intelligence and RCS support. I am assuming that I don’t have the newest version of the developer beta, but it isn’t being offered to me to download. Any help with this would be most appreciated.

it’s a cool concept, i see the vision, but it’s really ugly. all my app colours have changed, none of my transparent widgets work anymore because it changed the size of my wallpaper. i do like how the brightness and volume are now colours, i just wish we could’ve gotten to choose the colours. i also like how the things are circles instead of squares. i’m mostly just upset that my transparent widgets don’t work anymore, and how all the colours of all my apps are darker than i would like.

I've noticed the tab bar in tvOS 18 (beta) is positioned lower on the TV screen than in previous versions. Bug? I see no documentation on this important UI change... If this is not a bug, is there any way to adjust the y coordinate of the tab bar location in tvOS 18? I would really like to restore this to the previous location for my app and avoid having to do OS-conditional constraints for all my views/pages.

In visionOS2, there exists a function that enables users to raise their hand to display the home button. However, this functionality conflicts with the interaction required for the mixed display space utilized within my application. Therefore, I seek a method to disable this functionality.

I am writing to report an issue I encountered with iOS 18 beta that affects my application, which has been available on the App Store for over two years and currently has over 60,000 active users. My application utilizes a UITabBarController to manage multiple tabs, where each tab hosts a UIViewController embedded within a UINavigationController. The application operates in two different states, where users may have either 5, 4, or 3 tabBarItems depending on their configuration. The issue arises when fewer than 5 tabs are present. In these cases, I add child view controllers to the UITabBarController to ensure they are displayed above the tab bar, rather than below it. The relevant code snippet is as follows: tabBarController.addChild(childController) tabBarController.view.addSubview(childController.view) Prior to iOS 18, this implementation functioned as expected. However, with the release of iOS 18, adding a child view controller to the UITabBarController results in the child being incorrectly added as a UITabBarItem. This misbehavior leads to an application crash when the unintended tab is selected. The crash trace is as follows: "Inconsistency in UITabBar items and view controllers detected. No view controller matches the UITabBarItem '<UITabBarItem: 0x142d9c480> selected'." I have attached screenshots from iOS 18 and previous versions to illustrate the issue, which compares the expected behavior in earlier iOS versions with the problematic behavior in iOS 18. I appreciate your attention to this matter and look forward to any guidance or resolution you can provide.

Hi, guys. I installed iOS Beta 18.0 on my iPhone SE and iPad 9th, but the system does not upgrade to 18.1. These devices can't run Apple Intelligence. Is it that the reason? And if so, does anyone know how Apple is going to manage this situation? Thanks

Ever since updating to the latest ios18 I have had virtually no cellular connection. Even with four full bars I can’t actually connect to service. Sometimes I’ll get notifications, but sending anything, Waze, websites…not a chance. I sure hope they fix this fast. What’s the point of a smart phone and iOS that makes a phone unusable??

In Ios 18 beta the NFC not showing and also not working please can fix that

The storage optimization option in system settings-&gt; general-&gt; storage is missing in MacOS 15.0 (beta). It was present up to Sonoma.

Environment info Local machine: macos xcode 16 beta macOS Sequoia beta xcode cloud: Xcode latest release version (15.4). MacOS latest version I checked my project bundle identifier several times, it absolutly match to Apple Store connect. IIs failed occurred when workflow archive - distribution select testfight. If I select None in distribution, it Build success in Xcode cloud. Ps: I cannot archive from local machine, it shows Xcode version should be released version. Anyone meet the same problem? --- failed notification email attached below --- We noticed one or more issues with a recent delivery for the following app: WGesture Watch App Version 1.0 Build 8 Please correct the following issues and upload a new binary to App Store Connect. ITMS-90055: This bundle is invalid - The bundle identifier cannot be changed from the current value, 'com.war.WGesture.watchkitapp'. If you want to change your bundle identifier, you will need to create a new application in App Store Connect.

On testing my app with tvOS 18, I have noticed the Siri Remote back button no longer provides system-provided behavior when interacting with tab bar controller pages. Instead of moving focus back to the tab bar when pressed, the back button will close the app, as if the Home button was pressed. This occurs both on device and in the Simulator. Create tvOS project with a tab bar controller. Create pages/tabs which contain focusable items (ie. buttons) Scroll down to any focusable item (ie. a button or UICollectionView cell) Hit the Siri Remote back button. See expect behavior below: Expected behavior: System-provided behavior should move focus back to the tab bar at the top of the screen. Actual results: App is closed and user is taken back to the Home Screen. Has anyone else noticed this behavior?

I've got a problem with compatibility with Swift6 in iOS app that I have no idea how to sort it out. That is an extract from my main app file @MainActor @main struct LangpadApp: App { ... @State private var notificationDataProvider = NotificationDataProvider() @UIApplicationDelegateAdaptor(NotificationServiceDelegate.self) var notificationServiceDelegate var body: some Scene { WindowGroup { TabView(selection: $tabSelection) { ... } .onChange(of: notificationDataProvider.dateId) { oldValue, newValue in if !notificationDataProvider.dateId.isEmpty { tabSelection = 4 } } } } init() { notificationServiceDelegate.notificationDataProvider = notificationDataProvider } } and the following code shows other classes @MainActor final class NotificationServiceDelegate: UIResponder, UIApplicationDelegate, UNUserNotificationCenterDelegate { var notificationDataProvider: NotificationDataProvider? func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey : Any]? = nil) -&gt; Bool { UNUserNotificationCenter.current().delegate = self return true } func setDateId(dateId: String) { if let notificationDataProvider = notificationDataProvider { notificationDataProvider.dateId = dateId } } nonisolated func userNotificationCenter(_ center: UNUserNotificationCenter, didReceive response: UNNotificationResponse) async { // After user pressed notification let content = response.notification.request.content if let dateId = content.userInfo["dateId"] as? String { await MainActor.run { setDateId(dateId: dateId) } } } nonisolated func userNotificationCenter(_ center: UNUserNotificationCenter, willPresent notification: UNNotification) async -&gt; UNNotificationPresentationOptions { // Before notification is to be shown return [.sound, .badge, .banner, .list] } } @Observable final public class NotificationDataProvider : Sendable { public var dateId = "" } I have set Strict Concurrency Checking to 'Complete.' The issue I'm facing is related to the delegate class method, which is invoked after the user presses the notification. Current state causes crash after pressing notification. If I remove "nonisolated" keyword it works fine but I get the following warning Non-sendable type 'UNNotificationResponse' in parameter of the protocol requirement satisfied by main actor-isolated instance method 'userNotificationCenter(_:didReceive:)' cannot cross actor boundary; this is an error in the Swift 6 language mode I have no idea how to make it Swift6 compatible. Does anyone have any clues?

Let me start by apologizing for the long read.. I am not an Apple Developer or Power Mac user per se but I am also not a beginner. I am desperate for a solution because I’ve hit a wall. Im sorry I cant attach a Etrecheck report because it doesn’t support my Mac OS 15 Beta 6 on a M1 Macbook Air. … So once I changed my password ant root’s using the command, but many restarts later I would still use my old password to get in so I ignored. But a week later and after finishing up a Time Machine backup, neither my old or new password would get accepted on screen-lock. I’m not sure if the things I just mentioned are related but its definitely worth mentioning. The reason for my doubt is because I was able to log in to the Web GUI of Webmin remotely using my iPhone and my username and the password I changed the wee earlier; the same one that got me locked out of Mac user accout (I tried both old and new). Activating root from the Webmin panel allowed me to log in to my Macbook as root for the first time and went through the ame process as if it was a fresh install. I coulnt understand what was going on at this point Why did TouchID and passwordA fail only a few days later when I decided to do this ***** move? Why only after I finished backing up? I waited for the account locked timer to finish a few times but it would be in vain because it would just restart the the temporary lock each time the timer hits 0 or when I restart.cEven when I tried to change my account password from the root account GUI or terminal, it would accept the root password I enter but nothing happens…What’s even weirder is that MacOS would not accept that password I always use on the occasion of adding a new user. Any admin task is ok except for when I try to add a new user!!! WHAT THE HELL?!?! Regardless of what the causes for this are, the symptoms and how each one contradicts the other are very weird and illogical, at least for me. Finally, and I regret to say, that booting into recovery isn’t an option because every time I try holding the power button maybe a second or two after the chime sounds and the ztApple logo appears. I started experiencing this symptom around 2 years and I scoured the internet for a solution or any other way I could get into recovery but it seemed like I was the only one on earth to experience this problem. The local Apple repair wanted $100 just for opening up the laptop and typing up a report, so I couldn’t justify paying that amount for something I didn’t exactly need at that time and was able to live my life without needing to get into recover mode which I still hope would be the case now… and that is why I am being this details because every time I try to search for my problem I find that booting into recovery mode is always the recommended step to diagnose my password/account lock password. Some more notes in case it would help anyone identify the problem I am facing which I hope I didn’t make worse by being in the root account all this time which at the time of sending this post is almost 16 hours. When I logged into root, I went through all the prompts you would get when starting an account for the first time but skipped everything including setting up TouchID and my Apple ID. However, I did later log in to my Apple ID in haste and got the message on my iPhone that a new device was being set up, but after looking into it, it seemed like nothing changed from my device list. It hasn't been 24 hours logged in as root and besides all the weird stuff I', experiencing, Seqouia ihas become generally sluggish-- it hangs when I'm using everyday stuff like TextEdit, or when I try to go to the Advanced tab in Finder. The most unusual thing which I've already mentioned earlier is the password I have set for roo (System Administrator at the prompt) not getting accepted by the system when I try to add a new user when in all other scenarios that require System Administrator privileges. I hope someone from the community can help me out, and once again I do apologize for the long read, but my intention was only to minimize the need for back and forth like most otherone-linee reports spanning several pages. I am quite embarrassed by this because I don’t know what I was thinking when I tried changing my account password like that from the terminal, but then again I am only 90% sure that was the cause, as for the other 10% … it's a total mystery!! Thank you.

Hey, so just got my iPhone 14 Pro Max on iOS Beta repaired , but now almost every app that requires me to log in doesn’t work. hoe do I trouble shoot this. I’ve also tried resetting passwords and even those do not work

I’m developing a mobile app using Bubble.io, and we’ve wrapped our web app for iOS. One of the key features is importing and uploading audio files from Google Drive and Dropbox. However, I’m facing an issue with OAuth authentication during TestFlight testing. After users log into Google Drive or Dropbox and confirm access, they’re directed to a white page that says “Verification complete,” but nothing happens afterward. When they close and reopen the page, they’re prompted to log in and go through verification again, suggesting the redirect isn’t being handled correctly. This feature is critical for our app, and I need to ensure it functions properly before submitting it to the App Store. I’ve read that redirects might behave differently in TestFlight compared to a fully released app, but my development team and I haven't been able to resolve the issue. Does anyone have insights into whether this problem might be resolved upon official release, or are there specific steps we should take to fix the redirect handling in TestFlight?

I’ve let the System Settings‘ Sofware Updates run overnight twice - and all I get is the cylon blue shifting left to right… I’ve restarted my M1 MBAir several times. I’ve attempted to download it directly from developer.apple.com - but it just stops (Zero KB of 15.87 GB) - with no further clarification. Any ideas?

Apple Developer Support stated that they don’t have any technical support for this and suggested posting in the Forums or Feedback Assistant app. Hoping someone here may have encountered this before and maybe has a fix. On any of my devices (macOS, visionos, watchOS, iPadOS, tvOS, and iOS) Beta Update will not show Developer Beta as an option for my Apple Account/ID. The only option would be Public Beta. As visionOS is only available for Developer Beta, this wouldn’t help with my workflow unfortunately. My question is whether anyone here has seen that Developer Beta did not show up under Beta Update and what they had to do to get that fixed.

Platform and Version iOS Development environment: Xcode 16.0 beta 5 (16A5221g), macOS 14.6.1 (23G93) Run-time configuration: iOS 18.0 beta 5 (22A5326g) Description of Problem Starting with iOS 18 SDK, test bundles containing a +load method that accesses UIScreen.mainScreen result in deadlock during test bundle injection. Also filed as FB14703057 I'm looking for clarity on whether this behavior is considered a bug in iOS or whether we will need to change the implementation of our app. Steps to Reproduce Create a new iOS app project using Objective-C and including unit tests Add the following code snippet to any .m file in the test target: @interface Foo: NSObject @end @implementation Foo + (void)load { UIScreen * const mainScreen = UIScreen.mainScreen; NSLog(@"%@", mainScreen); } @end Run the tests Expected Behavior As with iOS 17 & Xcode 15, the tests run to completion. Actual Behavior With iOS 18 & Xcode 16, deadlock during test bundle injection. stack_trace.txt

Hey everyone, I’m inquiring on how to possibly resolve this issue I’m having. My Apple Account/ID is not showing any device Developer Beta (iOS, iPadOS, macOS, tvOS, visionOS, and watchOS). I’m only seeing Public Beta and AppleSeed Beta. I know some will say just use AppleSeed or Public Beta but the reason this is important for me is due to visionOS as it is only available for Developer Beta This is an image of what I see on my iPhone for example. Apple Vision Pro won’t show any at all as AppleSeed and Public Betas are not available for visionOS.

Xcode rejects the build as it is "not accepting apps developed with this OS yet". Based on the experiences of prior summer beta cycles — when should one expect this blocker to come down. Will I be waiting all the way until the public release of Sequoia (or longer)?