Posts

Post marked as solved
17 Replies
10k Views
Greetings,my app adds various items to its keychain and when doing an iTunes backup and restore, it successfully restores the keychain items provided the iTunes backup is encrypted. Works great!However I can't seem to be able to restore my app's keychain when doing an iCloud backup and then restoring to a different iPhone. Is there a way of specifying that the iCloud backup is encrypted in such a way that apps' keychains are backed up and restored properly when using iCloud backup/restore function?Is there a iCloud specific attribute that must be provided for keychain items to make this work?Thanks,Neal
Posted
by neal1.
Last updated
.
Post marked as solved
14 Replies
26k Views
Before loading an html resource into a WkWebView, it is always white regardless of whether in dark or light mode. I've tried setiing its background color after instantation, but it has no effect. When in dark mode, this produces a flashing effect as the white background is briefly displayed. Is there an API that I'm missing for this?Thanks in advance,Neal
Posted
by neal1.
Last updated
.
Post marked as solved
11 Replies
11k Views
I'm adding one UIBarButtonItem with a custom view. The custom view uses autolayout to layout its inner components. Is this supported in iOS 13? This issue does not happen when the same code is run against an iOS 12 device. Adding just one UIBarButtonItem which has a custom view causes this to happen. None of the UIViews listed in the conflict below are mine (e.g: _UIToolbarContentView) and they're clearly private UIView classes.I'm not even sure how to debug this issue. I've set the UIToolbar's translatesAutoresizingMaskIntoConstraints to NO, but this issue still happens.Setting a breakpoint on UIViewAlertForUnsatisfiableConstraints doesn't help because the stack trace doesn't give any valuable clues as it's all iOS private classesAny suggestions?Thanks,Neal[LayoutConstraints] Unable to simultaneously satisfy constraints. Probably at least one of the constraints in the following list is one you don't want. Try this: (1) look at each constraint and try to figure out which you don't expect; (2) find the code that added the unwanted constraint or constraints and fix it. (Note: If you're seeing NSAutoresizingMaskLayoutConstraints that you don't understand, refer to the documentation for the UIView property translatesAutoresizingMaskIntoConstraints) ( "<NSAutoresizingMaskLayoutConstraint:0x2815ebe30 h=--& v=--& _UIToolbarContentView:0x100d6f8e0.width == 0 (active)>", "<NSLayoutConstraint:0x2815ea120 H:|-(0)-[_UIButtonBarStackView:0x100d31080] (active, names: '|':_UIToolbarContentView:0x100d6f8e0 )>", "<NSLayoutConstraint:0x2815ea170 _UIButtonBarStackView:0x100d31080.trailing == _UIToolbarContentView:0x100d6f8e0.trailing - 16 (active)>")Will attempt to recover by breaking constraint <NSLayoutConstraint:0x2815ea170 _UIButtonBarStackView:0x100d31080.trailing == _UIToolbarContentView:0x100d6f8e0.trailing - 16 (active)>Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger.
Posted
by neal1.
Last updated
.
Post marked as solved
3 Replies
1.2k Views
I encountered many issues updating my 12.9" iPad Pro 2018 model to 13.2 latest beta. The issues were:The update hung overnight. In the morning the iPad was still at the Apple Logo with a full progress bar, but never finished. Had to put the iPad in DFU mode and restore it to 13.1.2Since I had 13.2 beta 1 on the iPad previously could not restore from backup so had to download the entire 13.2 beta 2 install (almost 4 GB)After downloading that huge update, it could not verify it. It complained about no Internet connectivity, even though Safari and other apps had no issue. Tried many solutions (including redownloading it) none workedTried to download the 13.2 beta 2 ipsw and do the update from iTunes but the ipsw is not there. Was it pulled back due to issues?
Posted
by neal1.
Last updated
.
Post not yet marked as solved
0 Replies
455 Views
Are there going to be any more iOS 13 betas, as opposed to iOS 13.1?I ask because all of my test devices are now running iOS 13.1 beta and if there will be more iOS 13 betas, how will I update to that now that I'm on iOS 13.1 beta?Thanks,Neal
Posted
by neal1.
Last updated
.
Post marked as solved
15 Replies
9.3k Views
Greetings,when I run my iOS 13 app in a iOS 11 simulator some of the colors in my asset catalog were incorrectly dsiplayed. Some colors came up as if the iOS 11 device was in dark mode and some colors were correct. Ideally it should have worked just as it does on iOS 12. I assumed that since named colors were available in iOS 11 that on on that platform the light colors would be used, since that is all that is known?We have a requirement that our app runs on the last 3 major versions of iOS, so it is imperative that this worksEdit: This is an issue with Xcode beta 6. I recall my app displaying colors correctly when it was run on Xcode beta 5 via the simulator.Edit2: I should point out that this also happens with image catalogs. Instead of picking the 'Any' image from the image set, it sometimes pick a dark mode one on iOS 11.Thanks in advance,Neal
Posted
by neal1.
Last updated
.
Post marked as solved
1 Replies
1.3k Views
I was running out of space so I deleted my 2 Xcode apps (10.3 and 11 beta 5). I also deleted everything in ~/library/developer in the hope that when I reinstall xcode, that the simulators would come back. Alas they did not. So while I have simulators for xcode 10 I see not a single simulator for iOS 13 (or any other iOS version for that matter) for xcode 11 beta.Clearly I did not delete the file that tells xcode which simulators are missing so xcode 11 'thinks' they are sill there.Edit: I should mention that I did not delete ~/library/developer/xcode/userData because I did not want to have to re-enter my provisioning profile data. Could that be the problem?Any suggestions would be highly appreciated.Thanks in advance,Neal
Posted
by neal1.
Last updated
.
Post marked as solved
2 Replies
696 Views
I had a Safari window in iOS 12 and early versions of iOS 13 which had hundreds of tabs, both in regular and private mode and when I select that window from the task list (it says that Safari window has > 400 tabs open) it comes up with only one tab in regular and private mode.I have Safari -> Close Tabs set to Manually.I have done many restores from earlier backups and afterwards, every time I go to that window from the task list it loses all its tabs. Is this a bug or a feature? Has anyone else had this happen?Thanks.
Posted
by neal1.
Last updated
.
Post not yet marked as solved
11 Replies
9.1k Views
This issue doesn't happen in iOS 11 or iOS 12. I don't believe it happened in earlier iOS 13 betas. Although it looks like a crash, the app keeps working and getting data. However every time it gets data from the backend the error occurs. Any ideas?019-07-18 15:45:43.161236-0400 MYAPP[56691:8522761] [] __nwlog_err_simulate_crash simulate crash already simulated "nw_endpoint_get_type called with null endpoint"2019-07-18 15:45:43.164858-0400 MYAPP[56691:8522761] [] nw_endpoint_get_type called with null endpoint, dumping backtrace: [x86_64] libnetcore-1872 0 libnetwork.dylib 0x00000001126be068 __nw_create_backtrace_string + 120 1 libnetwork.dylib 0x000000011262049f nw_endpoint_get_type + 175 2 libboringssl.dylib 0x0000000140ac4a6a nw_protocol_boringssl_get_subject_name + 178 3 libboringssl.dylib 0x0000000140ac7911 nw_protocol_boringssl_connected + 916 4 libnetwork.dylib 0x00000001124d655f nw_socket_connect + 239 5 libboringssl.dylib 0x0000000140ac74ee nw_protocol_boringssl_connect + 357 6 CFNetwork 0x0000000112a7e11a _CFURLStorageSessionCopyCache + 22727 7 libnetwork.dylib 0x00000001123954f8 nw_endpoint_flow_connect + 184 8 libnetwork.dylib 0x00000001123a23b9 nw_endpoint_handler_append_and_start_application_protocol + 3417 9 libnetwork.dylib 0x00000001125bc576 __nw_connection_append_and_start_application_protocol_block_invoke + 70 10 libnetwork.dylib 0x00000001126b942a nw_queue_context_async_if_needed + 74 11 libnetwork.dylib 0x00000001125bc240 nw_connection_append_and_start_application_protocol + 160 12 CFNetwork 0x000000011291e957 CFURLDownloadCancel + 113751 13 CFNetwork 0x000000011291e700 CFURLDownloadCancel + 113152 14 CFNetwork 0x000000011298083c _CFStreamErrorFromCFError + 279310 15 CFNetwork 0x00000001128a97b9 _CFHTTPMessageSetResponseProxyURL + 55146 16 CFNetwork 0x00000001128a946f _CFHTTPMessageSetResponseProxyURL + 54304 17 CFNetwork 0x00000001128a932e _CFHTTPMessageSetResponseProxyURL + 53983 18 CFNetwork 0x00000001128aa864 _CFHTTPMessageSetResponseProxyURL + 59413 19 CFNetwork 0x0000000112a6c370 __CFNetworkAgentMessageProcessorMain + 115008 20 CFNetwork 0x0000000112a6d1af __CFNetworkAgentMessageProcessorMain + 118655 21 CFNetwork 0x0000000112a6cd26 __CFNetworkAgentMessageProcessorMain + 117494 22 CFNetwork 0x0000000112a6c95e __CFNetworkAgentMessageProcessorMain + 116526 23 CFNetwork 0x0000000112a6c409 __CFNetworkAgentMessageProcessorMain + 115161 24 CFNetwork 0x0000000112a69fb5 __CFNetworkAgentMessageProcessorMain + 105861 25 CFNetwork 0x0000000112a69774 __CFNetworkAgentMessageProcessorMain + 103748 26 CFNetwork 0x0000000112a1c865 _CFNetworkHTTPConnectionCacheSetLimit + 183261 27 libdispatch.dylib 0x0000000112f21de4 _dispatch_call_block_and_release + 12 28 libdispatch.dylib 0x0000000112f22d58 _dispatch_client_callout + 8 29 libdispatch.dylib 0x0000000112f295ff _dispatch_lane_serial_drain + 788 30 libdispatch.dylib 0x0000000112f2a1c5 _dispatch_lane_invoke + 476 31 libdispatch.dylib 0x0000000112f2b815 _dispatch_workloop_invoke + 2631 32 libdispatch.dylib 0x0000000112f35a4d _dispatch_workloop_worker_thread + 722 33 libsystem_pthread.dylib 0x0000000113396611 _pthread_wqthread + 421 34 libsystem_pthread.dylib 0x00000001133963fd start_wqthread + 13
Posted
by neal1.
Last updated
.
Post marked as solved
1 Replies
718 Views
On an iPad with Touch ID, has anyone else noticed that intermittently when blocked on secItemCopyMatching(), the touch ID dialog doesn't come up but the Touch ID system is actually primed and waiting for a fingerprint?At first I thought that a different code path had been taken so that our app's default behavior was bypassed, but then I accidently touched the home button and realized that it was just not bringing up the Touch ID system dialog.What I would end up doing is then requesting the touch Id dialog to come up, but since an app's thread was already blocked on secItemCopyMatching() it would then return errSecAuthFailed.Thanks
Posted
by neal1.
Last updated
.