iPadOS 17.7.7

Everything was going ok until I decided to restore my apps from a 12.3.1 image. It got 95% done and then randomly went to a spinning wheel that never revcovered. Did hard reset, then DFU, and nothing. I had to start over. I assume it was a compatibility issue, but with a dozen apps I was testing, I can't narrow it down as it was nothing I developed. Par for the course, no biggie, but just want to put it out there so other people know it can happen. I put the 12.4 beta on and will give it a go in a week on another build.

if I use a cable to attach it, so I can set wifi, it shows up in the finder window < new install of OSX 10.15 as well >, but when I unlock it, it disappears.Can't get it to connect again until I disconnect the wire and reconnect it.Also, not showing up in the new Music app.any ideas??

Hello everyone,So has anyone of you managed to connect an external hard drive to your iPad?Both of my hard drives give me the simple error „Contents not available“.Do I have to format it to a special system?Thanks in advance.

Wondering whether the iOS Universal app code will need to be modified in order for the app to function properly in iPadOS. Thanks

On iPadOS and iOS13 on a call to visibleCells on a UITableView ( on code which works fine on iOS9 to iOS12 ) I get an exception with the messageAttempted to access the table view's visibleCells while they were in the process of being updated, which is not allowed.Searching on the web gives me no hits for this exact message, so I suspect the message itself is new or changed.Now the general gist of the message is fairly clear, but the specifics and but how one is expected to avoid this in a multithreaded application are far from clear.For example ...what sort of changes qualify,For example ... the user may rotate the device, a redisplay may be caused by incoming data. Are these now to be expected to crash your application?Maybe there is a new threading model / usage requirement that I don't know about, yet.Synchronising on the UITableView itself doesn't help.What am I missingAnd Yes, I can avoid the problem by catching the error and backing off until I succeed. But the hit on performance is eyewatering

On iOS13 snd iPadOS on a call to visibleCells on a UITableView ( on code which works fine on iOS9 to iOS12 ) I get an exception with the messageAttempted to access the table view's visibleCells while they were in the process of being updated, which is not allowed.Searching on the web gives me no hits for this exact message, so I suspect the message itself is new or changed.Now the general gist of the message is fairly clear, but the specifics and but how one is expected to avoid this in a multithreaded application are far from clear.For example ...what sort of changes qualify,For example ... the user may rotate the device, a redisplay may be caused by incoming data. Are these now to be expected to crash your application?Maybe there is a new threading model / usage requirement that I don't know about, yet.Synchronising on the UITableView itself doesn't help.What am I missingAnd Yes, I can avoid the problem by catching the error and backing off until I succeed. But the hit on performance is eyewatering

Tryig to test latest version of an app - need to use Xcode beta because devices are iOS 13.With iPad, build succeeds but instal generates a mesage saying 'An error was encountered while enabling development on this device'. (xE000076) . With iPhone X error message says cannot install when device is locked (xE0000E2) although devcie is unlocked; if devcie unlocked before Xcode launched then same error messabge as iPad is received.

Installed iOS 13 beta on my XS Max yesterday and mail worked fine ... installed on my 8 plus a few days before that. Today, mail isn't working on either device -- can't send or receive on any account. Verified all accounts are working fine on other devices.Edit: mail also stopped working on my 10.5 iPad Pro running iPadOS beta.Anyone else seeing this?

I tried to run the WWDC 2019 session 707 example project ColorFeed in iPad Pro 11 with iPadOS 13 beta (17A5492t). Was running on device, not launched via Xcode.https://developer.apple.com/videos/play/wwdc2019/707I added logging functions and also run Console App on Mac to monitor the app running on iPad. The background app refresh task does not seem to ever get launched.In the log file it's visible that dasd (DuetActivitySchedulerDaemon) processes the registered background task request every 5 to 50 seconds, but the task's CurrentScore never exceeds the ThresholdScore, which results in DecisionToRun:0.Console output:bgRefresh-com.example.apple-samplecode.ColorFeed.refresh:B60719:[ {name: ApplicationPolicy, policyWeight: 50.000, response: {Decision: Can Proceed, Score: 0.35}} {name: DeviceActivityPolicy, policyWeight: 5.000, response: {Decision: Can Proceed, Score: 0.33}}] sumScores:60.576667, denominator:96.410000, FinalDecision: Can Proceed FinalScore: 0.628323}'bgRefresh-com.example.apple-samplecod