If IOS 13 is released today (Sep 19) but IpadOS 13 isn't released until Sep 30, will there not be huge numbers of people who have both devices, and do the upgrade of their Reminders, causing them to fail on their iPad?And if iPadOS isn't released until the 30th, it will presumable be 13.1, so why is there still a 13.0 beta 8 available?Just a bit confused.
Search results for
iPadOS 17.7.7
3,647 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Hi,We have an agent which uses packet-tunnel framework which worked great in the previous iOS realeases.We are testing with iPadOS beta 13.1 (17A5844a) and experiencing issues where our app is being blocked with the following messages.CFSM dynamic blacklist: app com.bundleidentifiercom.bundleidentifier = AppBlacklisted.Has anyone encountered such issues with packet-tunnel based agent on the iPadOS 13 Beta environment?This is more what the log looks like:ep 19 10:20:25 iPad symptomsd(SymptomEvaluator)[110] <Notice>: CFSM dynamic blacklist: app com.bundleIdentifier denied (background/audio/plan): 1/0/1Sep 19 10:20:25 iPad symptomsd(SymptomEvaluator)[110] <Notice>: CFSM dynamic blacklist unrecognized com.apple.CryptoTokenKit.setoken (app: <null>, state: 1)Sep 19 10:20:25 iPad symptomsd(SymptomEvaluator)[110] <Notice>: CFSM dynamic blacklist for app: com.apple.Preferences, state: 2, (wifi/cell/rnf/jumbo/allflows/headroom/overdraft) 240198/0/0/0/4/0/0, allow, code: WithinA
I don't think there is going to be a 13.0 Final for iPad. iPadOS will be released on September 24th, the same day 13.1 is released.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
I did this just morning. On my iMac running the latest Catalina beta I installed iPadOS beta 8, the latest iPad 13.0 beta version you can download and installed it through Catalina with my ipad physically plugged into the iMac. Took a few minutes and when it finished, my ipad shows as running iOS 13. The ipad iOS 13.1 versions were a little too gruesome for me right now so I bailed on the beta version.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
I know that the `UISceneDelegate scene(_:openURLContexts:)` delegate method is meant as the `UIScene` equivalent of the `UIApplicationDelegate application(_:open:options:)` delegate method. But an app can have multiple active scenes while only one will have this delegate called at a time and it always seems to be the first scene.Is there any condition or action that will result in a specific scene (and not just the first one) having its `openURLContexts` delegate called or did this turn out to be a flawed design? What am I missing?Let me clarify the situation with an example.You have an app that supports multiple scenes in iPadOS. The user is actively using two side-by-side scenes for your app. There may even be some disconnected scenes in the background. Either way, assume there are multiple scenes.Let's also say that your app can open files of certain types. The user switches from your app to the Files app or just about any app that lets you share a file. In the other app you select a file and choo
Agreed. Still not present. I'm beginning to think we are being forced to wait for iPadOS to drop. Infuriating. They want us to submit updates, but we actually can't because we have no way to test.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
How can I do a conditional check for iPadOS ? I would have expected something like:#if targetEnvironment(iPadOS) ... #endifor#if os(iPadOS) ... #endifto work, but none of them do. I know how to do it by checking UIUserInterfaceIdiom, but I really thoguht one of the above would work.
Since Catalina beta 9 and iPadOS 3.1 release, SIdecar id broken again for me, with a timeout error.Is it just me?
Same here, Catalena beta 9 and iPadOS 13.1
Topic:
App & System Services
SubTopic:
Core OS
Tags:
Lately updated iPadOS 13.1 (release version, 17A844 ) on my iPad (5th generation)when call (in Swift):let voices = AVSpeechSynthesisVoice.speechVoices()The voices.count returns 0 (zero)It get no voices.And the OS log on console:== START LOG ==2019-09-25 14:47:00.949625+0800 AVSpeechSynthesisVoiceSynth[343:15026] Creating client/daemon connection: CE08F91D-B4FF-4997-A1C0-51B4F820D1F12019-09-25 14:47:00.952167+0800 SpeechSynth[343:15026] Got the query meta data reply for: com.apple.MobileAsset.MacinTalkVoiceAssets, response: 02019-09-25 14:47:00.953109+0800 SpeechSynth[343:15026] Consumed extension2019-09-25 14:47:00.973031+0800 SpeechSynth[343:15026] Got the query meta data reply for: com.apple.MobileAsset.MacinTalkVoiceAssets, response: 02019-09-25 14:47:01.018410+0800 SpeechSynth[343:15021] Got the query meta data reply for: com.apple.MobileAsset.VoiceServicesVocalizerVoice, response: 02019-09-25 14:47:01.030168+0800 SpeechSynth[343:15021] Consumed extension2019-09-25 14:47:01.064721+0800 SpeechSynt
WKScriptMessageHandler's didReceiveScriptMessage not called in iPadOS 13
Up until recently it seemed reasonable to assume that all StoreKit observer and delegate methods were called on the main thread. I'm not sure if this was documented, but I had ASSERTs in the relevant methods to check this was the case and they never fired.Since updating to iPadOS 13.1 I have discovered that the productsRequest:didReceiveResponse: and requestDidFinish: methods of SKProductsRequestDelegate are no longer called from the main thread. It's best to assume that request:didFailWithError: is also affected, although I haven't tested it.Given that these methods are typically used to update application state, it's now necessary to ensure this is performed in a thread-safe manner. I think the least intrusive solution would be to schedule the work to be performed on the main thead using dispatch_async(dispatch_get_main_queue(), ...).I'd be interested to know if anyone else can confirm this.
I've downloaded Xcode11 and it was missing simulators for 12.3, 12.4 & 13.1. Following various tips has not helped and I finally wiped it off my system and redownloaded. No help.Yesterday iPadOS and iOS 13.1 were released to the public. Still no simulators?
During the iPadOS beta, Sidecar was functional on my iPad mini 4, but that may have changed ahead of release.now with iPadOS installed sidecar don't wotk any more...Apple has not provided an official list of iPads that support the Sidecar feature.
Still having this same problem with iPadOS 13.1 beta 4, very frustrating because I can't use the mouse alongside the smartfolio keyboard; I'm amazed it still hasn't been fixed
Topic:
App & System Services
SubTopic:
Core OS
Tags: