Update: I updated my M1 iPadPro 12.9 to iPadOS 14.6 - hoping that make a difference - but no. "Your Mac is updating the software on this iPad" for over 8 hours now... I've using the restore image: "11-in iPad Pro (3rd gen), 12.9-in. iPad Pro (5th gen) 19A5281h" restore image Also, I'm developing in a remote part of Mexico, and getting a USB-A to USB-C connector is doubtful, so trying to update from my iMac isn't an option... ☹️ Any ideas for how to get my M1 Air to update my M1 iPad???

Urgently seeking some help here... I've also tried sending my iPad into Recovery Mode and then updating using the 15 beta 2 restore image, but alas, no difference. Finder on my M1 MBAir continues to say "Your Mac is updating this iPad" and it goes on and on and on (even overnight) and never completes

Just tried the latest iPadOS beta 2 package (19A5281j) - same problem continues.

Yet another update and a word of warning to anyone else trying to update their M1 iPad... After 2 1/2 days I finally had to give up trying to install iPadOS 15 beta 2 - and instead tried to re-install 14.6. Some more major bad news: my brand new M1 iPad Pro is now completely bricked. I cannot get it out of Recovery Mode. Neither AppleCare reps nor Apple Developer reps are allowed to support anything having to do with beta software - so their only advice was for me to send the iPad in for hardware service. Yuk. I have no idea which of my not-so-bright ideas was the one that turned this into such a fiasco - but I'm guessing it was trying to update the iPad to a beta OS from a MacBook that was also running a beta OS. Seemed like such a great idea at the time...

So, it turns out that perseverance is key to this problem, too... Despite having given up earlier today, I just couldn't stand by and watch my iPad become a paper-sized paper-weight - so I tried it a couple more times. Same exact procedure, each time expecting different results. Notwithstanding - finally success!!! A big shout-out to the consumer-facing AppleCare support folks @ Apple, as it was they who suggested I try putting the iPad into Recovery Mode.  The rep said he couldn’t guarantee it would work with beta software - but maybe it’d be worth a try… So, here’s what I did to get iPadOS 15 beta 2 on my iPad: 1 - I shut down both my MBAir and my iPad Pro 2 - I connected both via USB-C cables 3 - I powered up both devices, and waited for them to fully boot 4 - I pressed the following buttons on the iPad to enter Recovery Mode: 1.  Volume up (quick press) 2.  Volume down (quick press) 3.  Top / power button (press and hold - until laptop <- cable image appears) 4.  Note: this may take several attempts (it sometimes took me over 12 tries - on each Recovery Mode attempt!) to get the “laptop <- cable” image - otherwise, it just reboots 5 - Launch Finder on MBAir 6 - Select iPad 7 - A dialog box appeared, select Restore 8 - Hold down the option key and select “Restore and Update” (so that I could select the .ipsw image - instead of contacting the Apple software update servers. 9 - Select the image “iPad_Pro_Spring_2021_15.0_19A5281j_Resore.ipsw” 10 - Cross fingers and repeat as necessary Honestly, it took me 3 full days and tons of attempts. In the end, I have no idea what was actually causing my iPad to hang-up - and at this point I don't care. It works, I'm happy, and I've got a deadline to slay...

I had a very similar experience when trying to get iPadOS 15 beta 2 installed from my Mac which was running Monterey beta 2. I just kept trying, expecting to get different results. And lo & behold - after 3 days - I did: it finally just worked. My only suggestion is to just keep on trying… The rather comical account of my trials: https://developer.apple.com/forums/thread/683943

I had a very similar experience when trying to get iPadOS 15 beta 2 installed from my Mac which was running Monterey beta 2. I just kept trying, expecting to get different results. And lo & behold - after 3 days - I did: it finally just worked. My only suggestion is to just keep on trying… The rather comical account of my trials:  https://developer.apple.com/forums/thread/683943 (Note that the answer to this thread includes the exact steps I repeated until I finally got success.)

Am I missing something in the above program listing? This is such a fundamental basic requirement - to wrap @FocusState with @available(iOS 15) and then later in the code check #available(iOS 15) - that it's hard to believe that it is a bug. The more likely answer is that I'm not using these compiler directives correctly... Any thoughts? Any help?

Similar problems here too - M1 MBAir (21A5522h). Never saw the issue prior to latest OS upgrade

I have a very similar issue.  I've got an app currently in the store that is:   a) showing App Clip Domain Status = "Bad JSON Content", and    b) won't allow Advanced App Clip Experiences due to the App Clip Experience URL = "This URL is not contained in your app's associated domains."   c) unable to recognize an App Clip Code Here's my debugging steps: This is the contents of my .well-known dir: root:~/dvn8/ROOT/.well-known$ more apple-app-site-association  { "appclips": { "apps": { ["myappbundle.myreversedomain.Dvn8.Clip"] } }, } With each attempt to View Status of the "Bad JSON Content", I see 2 calls to apple-app-site-association - both of which return HTTP Status 200: 44.232.70.210 - - [17/Jun/2022:12:03:38 -0700] "GET /.well-known/apple-app-site-association HTTP/1.1" 200 80 "-" "AASA-Bot/1.0.0" 44.232.70.210 - - [17/Jun/2022:12:03:38 -0700] "GET /apple-app-site-association HTTP/1.1" 200 80 "-" "AASA-Bot/1.0.0" With respect to creating an Advanced App Clip Experience in App Store Connect (“Edit Advanced Experiences”), and the error "This URL is not contained in your app's associated domains", my entitlements are as follows: myMainApp.entitlements *   com.apple.developer.associated-domains: ( "appclips:dvn8.app" ) *   com.apple.developer.associated-appclip-app-identifiers: ( "myappbundle.myreversedomain.Dvn8.Clip" ) myAppClip.entitlements *   com.apple.developer.associated-domains: ( "appclips:dvn8.app" ) *   com.apple.developer.parent-application-identifiers: ( "myappbundle.myreversedomain.Dvn8" ) When I create an App Clip Code using the command line generator, and then I point any of my test devices at the code, I consistently get “No useable data found”.  Of course, when running the App Clip from Xcode - it works beautifully.  I just can’t figure out what I’m missing to get the Experience defined in App Store Connect, and why the App Clip Code doesn’t have useable data. Many thanks for any thoughts on what I’m might be missing!!!

Same problem here. I tried turning on/off everything as suggested in this thread, even un-paired my Watch from iPhone. Nothing worked. Spent 5 hours trying to rectify. And then I finally found a solution: I cleared the /Users/me/Library/Xcode/DerivedData directories for my app. (ie, any directory which begins with your app name.) That did it. Could have saved myself a 1/2 day of programming if I had tried that 1st. YMMV

FYI: I submitted FB10908604 regarding this

iOS 16 beta 5 continues to exhibit this bug

Work-around found! I found this in the release notes: Added View.scrollContentBackground, which permits customization of background colors for scrollable views like List. (45928055) And so here’s the new version… struct ContentView: View { @State var text = "Type something here." var body: some View { ZStack { Color.blue.ignoresSafeArea() if #available(iOS 16.0, *) { TextEditor(text:$text) .multilineTextAlignment(.center) .scrollContentBackground(Visibility.hidden) // new technique for iOS 16 .frame(height: 100) .padding([.leading, .trailing], 40) } else { // Fallback on earlier versions TextEditor(text:$text) .multilineTextAlignment(.center) .frame(height: 100) .padding([.leading, .trailing], 40) } } .onAppear { // Fallback on earlier versions UITextView.appearance().backgroundColor = .clear } } }

Just got bricked in iPadOS 16.1. It's been working until today, but I removed the iPad from the Magic Keyboard and kaboom! I've got a brick.