Hey All! When transitioning my app to use the nav bar appearance (introduce in ios13, but required to make navigation bar colors / backgrounds in io15) i believe i had everything all changed over and working ! in iOS 15 b2 it seems when changing navbar backgrounds from view controller to view controller BEFORE the view is displayed in (viewwillload) there seems to be a delay in the change, aka until the animation finishes THEN the navbar background will change, which if you have 2 difference navbarbackgrounds expected for a different view looks less than ideal, as it seems like it "pops in" vs it being there as the animation happens in ios 15 b1 and ios 14 etc. Any thoughts ? Thought maybe i was doing something wrong ! i submitted a feedback, but figured ide ask here too. Thanks !

Has anyone noticed the 14.3 Simulators have like a yellow tint dock and really weird colors on the app library etc. Something seems off. Im on latest Catalina

I recently got my iPhone 12 pro today and of course the first thing I do is try to debug onto my device. For All projects, even sample ones i created, it will literally sit on the launch storyboard for about 1 min before even hitting applicationdidfinishlaunchingwithoptions: and even after loaded sometimes hang for like 10 seconds. has anyone else seen this, the simulator is instant, and all other phones are instant, just weird the new phone just sits there.

Hey All, I noticed when trying to edit availability of and app for Apple Silicon macs, below the check box it says "Version xxxx cannot be made available for mac " Which is odd since it used to be checked. Im curious what makes its "Not available" since it really doesnt say why, possibly a bug within appstore connect? Or maybe all or "not available" until the macs are released. I check make available and hit save but it just reverts back to unchecked.

Hey All, im receiving the following new warning in xcode b3 : Showing All Messages Building for watchOS Simulator, but linking in object file (/Applications/Xcode-beta.app/Contents/Developer/Platforms/WatchSimulator.platform/Developer/SDKs/WatchSimulator7.0.sdk/usr/lib/libWKExtensionMainLegacy.a(WKExtensionMainLegacy.o)) built for watchOS is anyone else receiving this? its just a warning, but its new none the less. Thanks !

Hey All I have a question about the widget url to deep link or goto a specific view in my main app once the widget is tapped. Is this URL passed in the App Delegate ? Then i control which viewcontroller to goto ? Im a little confused , I currently have a ObjC App, and the widget itself is working great , im just curious how the "hand off" between the widget and the main app works. Im new to the URL portion. And ideas or sample (even pseudo) code would be great !

Im interested in adding a Widget into my Mix Obj C / Swift project and i believe i can, i understand WidgetKit is SwiftUI but as its an extension i can add it to my ObjC project. My question is (similar to WCSession), is WidgetCenter the framework used in the Main App, to Reload the widget etc. And if so how would you go about doing that in an ObjC project, or how do you reload widget for your main ObjC/Swfit App? Thanks!

Hey All,i noticed something in my app using iOS 13.4 B2, this was not occuring on iOS 13.4 b1 or any previous iOS versions . The delegate methodtextFieldShouldBeginEditing is being called twice now when i return NO after giving focus to the textfield (i dont want the keyboard to appear over my action sheet). Normally this is only called once so showActionSheet is only called once, but now its called twice and calls showactionsheet twice, which is obviously not what we want. as 2 action sheets will show up one after the other. Anyone else seeing anything similiar with double delegate calls? Thanks !- (BOOL)textFieldShouldBeginEditing:(UITextField *)textField{ if(textField==myTextField2){ [myTextField1 resignFirstResponder]; [self showActionSheet]; return NO; } return YES; }