Post not yet marked as solved
This is probably the closest forum to post this... wanted to ask if others are getting any feedback on bugs filed with the Feedback Assistant application.Over the years, when using bugreport (radar), I got decent updates regarding whether bugs were duplicates, when they got fixed or if more detailed info was needed. So far in Feedback Assistant, all my issues are still just open with no feedback whatsoever. Some open now for several months.Every major release of the OS or Xcode, I update the bugs with a short "still exists in version" note. I feel as if these will never get fixed. I'd at least like a "works as designed" or "too low a priority" note so I don't keep wasting my time.Are others getting feedback on bugs they filed through this app?
Post not yet marked as solved
Prior to WWDC 2020, the excellent 2015 video on Protocol Oriented Design was still available.
The initial version of the developer app also had that video, so I favorited that along with some others. App update though deleted those favorites. But the videos still available via the web (WWDC 2015, etc sections)
Recently even the web no longer has that video and a few others. What gives?
I have a custom control (a directional button with four parts; up, down, left, right) that uses beginTracking, continueTracking, etc.When this control is in a modal view controller on iOS 13, any initial taps on the control work well, but after moving the touch even a small amount, cancelTracking is called.While I can set the view controller to go full-screen, I'd like to keep the iOS 13 behavior of being able to dismiss it with the gesture. But it seems that that gesture is overriding any tracking of a control. The control is set to have isExclusiveTouch to 'true'.NOTE: This also happens with standard iOS controls. e.g. a standard button. Touch the button and all is well. But once you track outside the button, it starts moving the view controller.
Post not yet marked as solved
For an existing iOS app with a baseline of iOS 12, I already had an assets file the the full range of app icons. To include the 1024x1024 app store flavor, special 76pt (1x and 2x) and the 83.5pt (2x) images for iPad.In the assets file, I clicked on the Mac checkbox and dragged in the custom artwork for all of those.Now though, even after existing Xcode and doing clean builds, I always get three warnings:A 76x76@2x app icon is required...A 83.5x83.5@2x app icon is required...A 1024x1024 app store icon is required...But all those image are there and of the correct resolution. Individually selecting those images in the asset catalog shows the correct info in the properties panel. For example, for AppIcon_76pt_@2x.png, the idiom is iPad, Size is 76x76pt and Scale is 2x.If I then uncheck the Mac checkbox in the assets catalog (and thus losing the Mac-specific artwork), the warnings go away.I then turned on the Mac checkbox again and did a clean build. No warnings.After then dragging in just the App Store icon (the 512pt @2x flavor) for Mac... hitting rebuild then produces the warnings. I will file a bug shortly.
Post not yet marked as solved
We're using ASWebAuthenticationSession and whenever no errors occur, all is well. However, if there's an error generated by our OAUTH web endpoint, the authentication session's UI is automatically dismissed. And, right at the beginning of its dismissal, our callback is called. But if we attempt to show say an error alert, or even present the prior view controller, we get errors like: Attempt to present <UINavigationController: ...> on <MainViewController: ...> while a presentation is in progress!In looking at the documentation, I see no way to tap into the authentication session's UI dismissal. Is there any way to defer work until after the session's UI is dismissed?For now, we're using a hack where we 'perform with selector' after a one-second delay. But I don't want to rely on that whatsoever.Here's the gist of our code:// In our main view controller...
private var webSession : ASWebAuthenticationSession?
func presentAuthorization(withURL aURL: URL) {
webSession = ASWebAuthenticationSession(url: aURL, callbackURLScheme: "ourcustomscheme://callback",
completionHandler: { (aURL, anError) in
if let theCallbackURL = aURL {
// We get here whenever there are particular errors. If we get a 'cancel' OAUTH
// error, that is working. The UI isn't automatically dismissed. So in our
// cancel handler we call webSession.cancel() and go to the prior view controller a-ok.
// But for some reason, any other callbacks seems to auto-dismiss the session's UI.
// Here, the app is left in a bad state since we cannot present alerts or view
// controllers.
} else {
// this block of code works a-ok.
}
}
}
For all my apps that use table view cells, I set up the textLabel and detailTextLabel in the storyboard editor to have a font of 'Body'. And, as my minimum OS is iOS 11, I also check the 'Automatically Ajusts Font' checkbox.When building these apps with Xcode 10.3 against the iOS 12 SDK, the apps react to dynamic type changes automatically as expected.But, when building the same apps with Xcode 11 (release version) against the iOS 13 SDK, the apps no longer work. All labels in table view cells have a fixed size. Even when the app is launched with various settings of the system's text size already set up.Standalone labels though work a-ok (same font and automatically... settings used).If I inspect the label's attributes at runtime, they do indeed have the 'adjustsFontForContentSizeCategory' set to 'true'. The font property appears "OK":- some : <UICTFont: 0x7f96d5c20440> font-family: "UICTFontTextStyleBody";
font-weight: normal; font-style: normal; font-size: 17.00ptTo remedy this, I created a sublass of UITableViewCell and in its awakeFromNib, I programatically set the font:let theFont = UIFont.preferredFont(forTextStyle: .body)
textLabel?.font = theFont
detailTextLabel?.font = theFontIf I inspect the attributes with this workaround, the adjustsFontForContentSizeCategory is still set to 'true' (so matches what I set in IB). The font property with dynamic text set to the default value is:- some : <UICTFont: 0x7fb78dd198a0> font-family: "UICTFontTextStyleBody";
font-weight: normal; font-style: normal; font-size: 17.00ptOther than the memory address difference, they are identical. Yet the behavior isn't the same. So there must be something behind the scenes that isn't being set up correctly when just relying on the settings in IB.NOTE: While I didn't try all fonts, the same issue doesn't happen with 'Callout'. I'll file a bug after I test all the other fonts to see if this is perhaps just isolated to 'Body'.
Post not yet marked as solved
Ages ago, I had an Objective-C application crash on a new version of OS X. The issue was that my subclass of an Apple class had a property, but Apple added a property with the same name. So to avoid this issue in the future, I started to prefix/suffix all my code to guarantee uniqueness.Fast-forward to Swift. When starting out, I kept the suffix scheme going. A contrived example:class IIMainViewController : UITableViewController { // custom type prefix
var refreshControl_II : UIControl! // custom property suffixIf I drop the _II suffix, I'll get an appropriate error: "Property 'refreshControl' with type 'UIControl?' cannot override a property with type 'UIRefreshControl?'But let's pretend that refreshControl wouldn't have been added to UITableViewController until iOS 13. What would happen with a Swift app with a 'refreshControl' property in the table view subclass when running on iOS 13?In all the namespacing articles I've read, I haven't come accross this specific example.
