I had been using the following code prior to iOS 11 to customize the appearance of the `UISearchController` search bar:

    var searchController = UISearchController(searchResultsController: nil)
    searchController.searchBar.setDefaultSearchBar()
    searchController.searchResultsUpdater = self

    if #available(iOS 11.0, *) {
        navigationItem.searchController = searchController
    } else {
        tableView.tableHeaderView = searchController.searchBar
    }

    extension UISearchBar {
        func setDefaultSearchBar() {
            self.tintColor = UIColor.blue
            self.searchBarStyle = .minimal
            self.backgroundImage = UIImage(color: UIColor.clear)
            let searchBarTextField = self.value(forKey: &quot;searchField&quot;) as! UITextField
            searchBarTextField.textColor = UIColor.white
            searchBarTextField.tintColor = UIColor.blue
            searchBarTextField = .dark
        }
    }

However, the appearance of the search bar fails to update when running the same code on iOS 11.

**iOS 10:**

[![enter image description here][1]][1]

**iOS 11:**

[![enter image description here][2]][2]


  [1]: https://i.stack.imgur.com/ZOj2F.png
  [2]: https://i.stack.imgur.com/GG7z0.png

Much of the attention to this question so far has focused on the text color of the search bar. I am looking at more than this - the background color, tint color, the search indicator, clear button color, etc.

UISearchController iOS 11 Customization

The Apple guy in the [What&#39;s new in Cocoa Touch WWDC video said][1] that the new large-title navigation bar will magically hook into the top-level scroll view of the underlying view controller and collapse/expand itself automatically while scrolling up and down. (And by &quot;magically&quot;, he probably meant that they failed to monkey patch this functionality into the already embarassing `UINavigationController`-`UINavigationBar`-`UINavigationitem` APIs in a usable way, so they had to resort to hooking into some heuristically chosen scroll view behind the scenes)

Even though I was prepared that this &quot;automatic&quot; collapse/expand wouldn&#39;t work if I deviate the slightest from the basic `UINavigationController` + `UITableView`/`UICollectionView` setup, it seems that even in this simplest case it doesn&#39;t work as expected. 

Here&#39;s what I have:

A `UITabBarController` which contains a `UINavigationController`, which contains a `UIViewController`, which has a `UITableView` as its `view`. Tapping the first cell in the table will push a second view controller on the navigation stack:

[![storyboard][2]][2]

No code, just the storyboard. 

I&#39;ve checked *&quot;Prefers large titles&quot;* for the navigation bar to activate large titles. Now, if I run the app and scroll up/down on the table view, the navigation bar stays the same - large - size; it doesn&#39;t collapse:

[![stuck with large title][3]][3]

However, I&#39;ve found that if I set the second view controller&#39;s navigation item to use the small navigation bar (by setting *&quot;Large Title&quot;* to the value *&quot;Never&quot;*), then if I open that page and navigate back, the interactive collapse magically starts working on the first page:

[![interactive collapse works after back navigation][4]][4]

Am I missing something here, or is this feature not working properly? Here&#39;s the sample project I&#39;m using: https://github.com/tzahola/iOS-11-Large-Title-Navigation-Bar

And by the way, I&#39;m using the officially released iOS 11, not the betas. 

*2017-09-23 Update: I&#39;ve sent a bug report to Apple, and opened a ticket on openradar.me: http://www.openradar.me/radar?id=5017601935671296*

  [1]: https://developer.apple.com/videos/play/wwdc2017/201/
  [2]: https://i.stack.imgur.com/hnSlK.png
  [3]: https://i.stack.imgur.com/PM0ru.gif
  [4]: https://i.stack.imgur.com/pJBD9.gif

iOS 11 large-title navigation bar not collapsing

I have a view controller that takes up the whole screen from top to bottom. I would like to hide the home bar indicator on the bottom of the screen on iPhone X devices. 

How can I do this in iOS 11?

iPhone X hide home indicator on view controller

I want to use Xcode 8 with iOS 11.

 should I upgrade my Xcode. However, my code can&#39;t be built by the new compiler, so I want to stay with Xcode 8.

[![enter image description here][1]][1]

How can I achieve that?

**Apple revealed several new iOS 11 features at WWDC 2017.** 


  [1]: https://i.stack.imgur.com/l84Gj.png

Use Xcode 8 with iOS 11

I have built my app using new Xcode 9 beta for ios 11. I have found an issue with UITabBar where items are spread through the UITabBar and title is right aligned to the image. I have tried changing the code to get it to work but still not successful. 

ios 10+ 

[![enter image description here][1]][1]

ios 11

[![enter image description here][2]][2]

I could change the position of title using `tabBarItem.titlePositionAdjustment`
But that is not my requirement as it should automatically come bellow the image itself. I tried setting `tabbar.itemPositioning to UITabBarItemPositioningCentered` and also tried changing `itemSpacing` and `width`, but still did not work. Can someone help me understand why this happens and how to fix this? I want it to like ios 10+ version and images are taken from the left most corner of an iPad.


  [1]: https://i.stack.imgur.com/up2iM.png
  [2]: https://i.stack.imgur.com/4Lxt6.png

ios 11 UITabBar UITabBarItem positioning issue

After migrating to the new iOS 11. We are seeing this new error. Not only we are facing the error but the whole UI is sluggish.

This is a native iOS app written in obj-c. We are not seeing the error in ios 10.2 or earlier. Any ideas?

Apple Maps, Raster Overlays Above Labels - Failed to decode

I&#39;ve update my iPhone 6 plus to iOS 10 beta version and just found that in mobile safari, you can zoom any webpages by double tapping or pinching **IGNORE** the `user-scalable=no` code in the meta tag. I don&#39;t know whether it&#39;s a bug or feature. If it&#39;s considered as a feature, how do we disable viewport zooming iOS 10 safari ?

----------
updated on iOS 11/12 release, iOS 11 and iOS 12 safari still DO **NOT** respect the `user-scalable=no` meta tag.

[![mobile github site on Safari][1]][1]


  [1]: https://i.stack.imgur.com/uVrdO.gif

disable viewport zooming iOS 10+ safari?

I noticed that on iOS 11 beta 2, the silent notifications are not delivered to the `application:didReceiveRemoteNotification:fetchCompletionHandler` regardless the state of the app (background / foreground).

I implemented the `UIApplicationDelegete` method `application:didReceiveRemoteNotification:fetchCompletionHandler` and I send the following silent push

    {  
      &quot;aps&quot;: {  
        &quot;content-available&quot;: 1  
      },  
      &quot;mydata&quot;: {  
        &quot;foo&quot;: &quot;bar&quot;  
      }  
    } 

but the delegate method is not called on iOS 11. 

It works fine on other versions of iOS and the documentation section [Configuring a Silent Notification][1] does not mention that anything else should be done.

Is this a bug in iOS 11 or did I miss something new in iOS 11? 

Please note that I&#39;m not talking about or using the `UserNotification` framework which should not be needed for sending silent pushes.

Here is a [sample project][2] that illustrates the issue (you&#39;ll have to set your own bundle id)

When you lunch the sample project and send a above payload to the app, you can use the macOS console to see that the push is correctly delivered to the device but not to the app.

# UPDATE 10.08

It appears that the behaviour is random. Sometimes after restarting the device, the payload is delivered correctly but it stops working after a while.

As you can see on the following screenshot, the push marked as 1 is delievered only to the device and the push 2 (after device restart) is also delivered to the app.

[![enter image description here][3]][3]

# UPDATE 14.08 - iOS 11 Beta 6

Still the same behaviour. Another thing that is supposed to work but does not is the following. When the application&#39;s scheme is set to &quot;Wait for executable to be launched&quot;, a silent push is supposed to wake up the app and start it in background. 

[![enter image description here][4]][4]



# UPDATE 21.08 - iOS 11 Beta 7

Still the same behaviour and not updates from Apple in the bug report.

#UPDATE 29.08 - iOS 11 Beta 8

Still the same problem. The steps to reproduce I use now are the following:

- In the Xcode project scheme, select &quot;Wait for executable to be launched&quot;
- Add a breakpoint in the `didReceiveRemoteNotification: fetchCompletionHandler`
- Start the app on device
- Send the above silent push

**Expected**: The app is brought from suspended state to background and the `didReceiveRemoteNotification: fetchCompletionHandler` is called

**Actual**: nothing happens 


# UPDATE 06.09 - iOS 11 Beta 10

I&#39;m still having the same buggy behaviour. The ticket from Apple was updated with the following answer:


&gt; Apple Developer Relations September 6 2017, 10:42 PM Engineering has
&gt; provided the following feedback regarding this issue: 
&gt; 
&gt; We were able to get the sample app running and test the behavior. We
&gt; didn’t see any issues when we tested this as described. 
&gt; 
&gt; Pushes aren&#39;t guaranteed to arrive to the app when it is running in
&gt; the background, and the logs here indicate we don&#39;t believe the app is
&gt; being used enough to launch it. 
&gt; 
&gt; We do see us delivering pushes from time to time when conditions are
&gt; good. 
&gt; 
&gt; We believe this is behaving correctly.


# Update 11.09

My Apple bug report was closed and marked as duplicate of `33278611` which remains open


# UPDATE 13.09 - iOS 11 GM
Thanks to kam800&#39;s comments (see below) I did more testing and came up with those observations:


There seem to be a new daemon in iOS 11 `dasd	DuetActivitySchedulerDaemon` that either completely discards the data push or delays the data push delivery:

### Delivery postponed

**Console Logs**

    default	13:11:47.177547 +0200	dasd	DuetActivitySchedulerDaemon	CANCELED: com.apple.pushLaunch.net.tequilaapps.daylight:C03A65 &lt;private&gt;!	lifecycle	com.apple.duetactivityscheduler
    default	13:11:47.178186 +0200	dasd	DuetActivitySchedulerDaemon	Removing a launch request for application &lt;private&gt; by activity &lt;private&gt;	default	com.apple.duetactivityscheduler
    default	12:49:04.426256 +0200	dasd	DuetActivitySchedulerDaemon	Advancing start date for &lt;private&gt; by 6.5 minutes to Wed Sep 13 12:55:31 2017	default	com.apple.duetactivityscheduler
    default	13:21:40.593012 +0200	dasd	DuetActivitySchedulerDaemon	Activity &lt;private&gt;: Optimal Score 0.6144 at &lt;private&gt; (Valid Until: &lt;private&gt;)	scoring	com.apple.duetactivityscheduler
    default	13:21:40.594528 +0200	dasd	DuetActivitySchedulerDaemon	Setting timer (isWaking=1, activityRequiresWaking=0) between &lt;private&gt; and &lt;private&gt; for &lt;private&gt;	default	com.apple.duetactivityscheduler

**Postponed delivery issues**

- When the data push delivery is postponed and the app is launched, the data push is delivered only when the delivery date is reached which can be *several minutes* in the future. This defeats completely the purpose of using data pushes to keep the new app&#39;s content ready for the next launch. I quote here once again Apple&#39;s documentation: 

&gt; &quot;Silent notifications improve the user experience by helping you keep
&gt; your app up-to-date, even when it is not running.&quot;

- When **two** data pushes are sent to a suspended app they are postponed by iOS 11 instead of waking up the app directly. When delivery time is reached, *only the last* data push is delivered! The previous pushes are lost and not delivered via the delegate method resulting in a data loss.

### Delivery cancelled
**Console Logs**

    default	13:35:05.347078 +0200	dasd	DuetActivitySchedulerDaemon	com.apple.pushLaunch.net.tequilaapps.daylight:C03A65:[
    	{name: ApplicationPolicy, policyWeight: 50.000, response: {Decision: Must Not Proceed, Score: 0.00}}
     ], FinalDecision: Must Not Proceed}	scoring	com.apple.duetactivityscheduler

**Cancelled delivery issues**

Well in this case, the data push is completely lost and never delivered on iOS 11 while it was delivered correctly on iOS 10.

# UPDATE 19.09 - iOS 11 GM

I also noticed that when the application is in the foreground and the notification is not delivered to the app, I see the following logs in the console:

    default	08:28:49.354824 +0200	apsd	apsd	&lt;private&gt;: Received message for enabled topic &#39;&lt;private&gt;&#39; onInterface: NonCellular with payload &#39;&lt;private&gt;&#39; with priority 10 for device token: NO	courier-oversized	com.apple.apsd
    
    fault	08:33:18.128209 +0200	dasd	Foundation	&lt;NSXPCConnection: 0x151eee460&gt; connection from pid 55: Exception caught during decoding of received message, dropping incoming message.
    Exception: Exception while decoding argument 0 (#2 of invocation):
    Exception: value for key &#39;NS.objects&#39; was of unexpected class &#39;NSNull&#39;. Allowed classes are &#39;{(
        NSArray,
        NSData,
        NSString,
        NSNumber,
        NSDictionary,
        NSUUID,
        _DASActivity,
        NSSet,
        _DASFileProtection,
        NSDate,
        NWParameters,
        NWEndpoint
    )}&#39;.	general	com.apple.foundation.xpc



  [1]: https://developer.apple.com/library/content/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/CreatingtheNotificationPayload.html#//apple_ref/doc/uid/TP40008194-CH10-SW8
  [2]: https://www.dropbox.com/s/qdk3dh9irpsmbgi/PushBug11.zip?dl=0
  [3]: https://i.stack.imgur.com/d5Avv.png
  [4]: https://i.stack.imgur.com/S5DbS.png

Silent pushes not delivered to the app on iOS 11

After updating to Xcode 9, using Swift 3 and the iPhone X simulator, my console is full of:

    TIC Read Status [11:0x0]: 1:57
    TIC Read Status [11:0x0]: 1:57
    TIC Read Status [11:0x0]: 1:57
    ...

What is that and how do I fix it? Help is very appreciated. 

PS: I prefer not to just &quot;silence&quot; it with an `Environment Variable` in the build scheme. 

What is TIC Read Status 1:57 in iOS11/Xcode 9?

While exploring **Xcode9 Beta** Found **Safe Area** on Interface builders View hierarchy viewer. Got curious and tried to know about Safe Area on Apples documentation, in gist the doc says *&quot;The the view area which directly interacts with Auto layout&quot;* But it did not satisfy me, I want to know Practical use of this new thing. 

Do any one have some clue? 

[![enter image description here][1]][1]

**Conclusion paragraph from Apple doc for Safe area.**

&gt;The UILayoutGuide class is designed to perform all the tasks previously performed by dummy views, but to do it in a safer, more efficient manner. Layout guides do not define a new view. They do not participate in the view hierarchy. Instead, they simply define a rectangular region in their owning view’s coordinate system that can interact with Auto Layout.


  [1]: https://i.stack.imgur.com/qif1w.png

Safe Area of Xcode 9

Anyone having issue with the iPhone X simulator around the UITabBar component?

Mine seem to be rendering the icons and title on top of each other, I&#39;m not sure if I&#39;m missing anything, I also ran it in the iPhone 8 simulator, and one actual devices where it looks fine just as shown on the story board.

**iPhone X:**

[![iPhone X UITabBar bug][1]][1]


**iPhone 8**

[![iPhone 8 UITabBar works][2]][2]


  [1]: https://i.stack.imgur.com/gerXV.png
  [2]: https://i.stack.imgur.com/LMNeu.png

iOS 11 iPhone X simulator UITabBar icons and titles being rendered on top covering eachother

&lt;h3&gt;Summary&lt;/h3&gt; 
We cannot access camera from an iOS11 (public release) home screen web app using either WebRTC or the file input, details below. How can our users continue to access the camera please?

We are serving the web app page over https.

_&lt;h3&gt;Update, April&lt;/h3&gt;_
The public release of iOS 11.3 seems to have fixed the issue and file input camera access is working again!

_&lt;h3&gt;Update, March&lt;/h3&gt;_

As people here have said the Apple docs advise web app camera function is returning in 11.3 along with service workers.  This is good but we are not sure yet if we want to everyone to to reinstall again until we can thoroughly test on 11.3GM.  

_&lt;h3&gt;Solution, November&lt;/h3&gt;_
We lost hope Apple want to fix this and moved forward.  Modified our web app to remove the iOS &quot;Add to home screen&quot; function and asked affected users to remove any previous home screen icon.


_&lt;h3&gt;Update, 6 December&lt;/h3&gt;_

iOS 11.2 and iOS 11.1.2 don&#39;t fix. 

_&lt;h3&gt;Workarounds, 21 September&lt;/h3&gt;_

Seems we could ask existing customers of the web app 

&lt;ul&gt;
&lt;li&gt;not upgrade to iOS11 - good luck with that :) &lt;/li&gt;
&lt;li&gt;take photos in iOS camera and then select them back in the web app&lt;/li&gt; 
&lt;li&gt;wait for next ios beta&lt;/li&gt; 
&lt;li&gt;reinstall as a Safari in-browser page (after we remove ATHS logic) &lt;/li&gt;
&lt;li&gt;switch to Android&lt;/li&gt; 
&lt;/ul&gt;

&lt;h3&gt;File Input&lt;/h3&gt;
Our current production code uses a file input which has worked fine for years with iOS 10 and older. On iOS11 it works as a Safari tab but not from the home screen app. In the latter case the camera is opened and only a black screen is shown, hence it is unusable.
 
       &lt;meta name=&quot;apple-mobile-web-app-capable&quot; content=&quot;yes&quot;&gt;
       ...
       &lt;input type=&quot;file&quot; accept=&quot;image/*&quot;&gt;


&lt;h3&gt;WebRTC&lt;/h3&gt;
Safari 11 on iOS11 offers [WebRTC media capture][1] which is great.  

We can capture a camera image to canvas on a normal web page on desktop and mobile using navigator.mediaDevices.getUserMedia per [the sample code linked here][2].  

When we add the page to iPad or iPhone home screen, &lt;code&gt;navigator.mediaDevices&lt;/code&gt; becomes &lt;code&gt;undefined&lt;/code&gt; and unusable. 

        &lt;meta name=&quot;apple-mobile-web-app-capable&quot; content=&quot;yes&quot;&gt;
        ...
        // for some reason safari on mac can debug ios safari page but not ios home screen web apps 
        var d = &#39;typeof navigator : &#39; + typeof navigator; //object
        d += &#39;typeof navigator.mediaDevices : &#39; + typeof navigator.mediaDevices; // undefined
        // try alternates
        d += &#39;typeof navigator.getUserMedia  : &#39; + typeof navigator.getUserMedia; // undefined
        d += &#39;typeof navigator.webkitGetUserMedia  : &#39; + typeof navigator.webkitGetUserMedia; // undefined
        status1.innerHTML = d;

  [1]: https://developer.apple.com/library/content/releasenotes/General/WhatsNewInSafari/Safari_11_0/Safari_11_0.html
  [2]: https://webrtc.github.io/samples/src/content/getusermedia/canvas/


How to access camera on iOS11 home screen web app?

When using Xcode 9, there are some compiler warnings saying `This function declaration is not a prototype`. It suggests to add `void` to the method body, which will resolve it. The issue I am having is that those warnings are also thrown for system-API&#39;s like `UIApplication` delegate-methods:

    - (void)application:(UIApplication *)application
        handleActionWithIdentifier:(NSString *)identifier
             forRemoteNotification:(NSDictionary *)userInfo
                  withResponseInfo:(NSDictionary *)responseInfo
                 completionHandler:(void (^)())completionHandler

This could be resolved by the following:

    - (void)application:(UIApplication *)application
        handleActionWithIdentifier:(NSString *)identifier
             forRemoteNotification:(NSDictionary *)userInfo
                  withResponseInfo:(NSDictionary *)responseInfo
                 completionHandler:(void (^)(void))completionHandler


Now I am wondering if the delegate methods will still work on the long-term or Apple will insert the `void` in later iOS 11 Beta versions. I am curious because if I include the `void` body, Xcode will complain about mismatching method-selectors (which makes sense). Did someone experience the same issue so far? 

&quot;This function declaration is not a prototype&quot; warning in Xcode 9

I&#39;m trying to display an image from the photo library in a UIImageView

The full error is:

&gt; 2017-06-09 21:55:59.063307+0200 firstapp2.0[12873:1120778] PhotoPicker
&gt; discovery error: Error Domain=PlugInKit Code=13 &quot;query cancelled&quot;
&gt; UserInfo={NSLocalizedDescription=query cancelled}

My code is included below: 

    import UIKit

    class ViewController: UIViewController,UIImagePickerControllerDelegate,UINavigationControllerDelegate{
        
        @IBOutlet weak var pic: UIImageView!
        @IBOutlet weak var text: UILabel!
    
        var chosenImage : UIImage!
        
        override func viewDidLoad() {
            super.viewDidLoad()        
            pic.isUserInteractionEnabled = true;
        }
    
        override func didReceiveMemoryWarning() {
            super.didReceiveMemoryWarning()
            // Dispose of any resources that can be recreated.
        }
    
        func imagePickerController(_ picker: UIImagePickerController, didFinishPickingMediaWithInfo info: [AnyHashable: Any]) {
            var chosenImage = info[UIImagePickerControllerEditedImage]
            self.pic!.image = chosenImage as! UIImage
            picker.dismiss(animated: true, completion: nil)
        }
    
        func imagePickerControllerDidCancel(_ picker: UIImagePickerController) {
            picker.dismiss(animated: true, completion: nil)
        }
        
        @IBAction func tap(_ sender: Any) {        
            self.text.text = &quot;Kreason&quot;
            let imagePicker = UIImagePickerController()    
            imagePicker.delegate = self        
            imagePicker.sourceType = UIImagePickerControllerSourceType.photoLibrary
            imagePicker.allowsEditing = false    
            self.present(imagePicker, animated: true, completion: nil)
        }
    }






PhotoPicker discovery error: Error Domain=PlugInKit Code=13

I&#39;m struggling to release a new version of our app using Xcode 9 built with iOS 11 SDK. Archiving and uploading the binary goes well without any issue. The build appears in iTunes Connect under Activity as &#39;processing&#39; and it gets disappear and I get the following email back.
 

&gt; Dear developer,
&gt; 
&gt; We have discovered one or more issues with your recent delivery for
&gt; &quot;&lt;project&gt;&quot;. To process your delivery, the following issues must be
&gt; corrected: Missing Info.plist value - A value for the Info.plist key
&gt; CFBundleIconName is missing in the bundle &#39;&lt;project_id&gt;&#39;. Apps that
&gt; provide icons in the asset catalog must also provide this Info.plist
&gt; key. For more information see
&gt; http://help.apple.com/xcode/mac/current/#/dev10510b1f7. Once these
&gt; issues have been corrected, you can then redeliver the corrected
&gt; binary. Regards, The App Store team

 
 
The link gives some info about asset bundles. I tried setting a CFBundleIconName key to project name or an image file name and submitted the app again. However, I still get the same email as above. 

Any suggestion of help would be highly appreciated.

Missing CFBundleIconName in Xcode9 iOS11 app release

This code works ok in ios10. i get my label and an image button which is the user photo profile, circular round.. ok. but when running xcode 9 ios11 simulator i get it streched out. the button frame has to be 32x32 , when checking on the sim and getting the view and telling xcode to describe the view i get output as 170x32 or somethint like that.

heres my code.

    let labelbutton = UIButton( type: .system)
        labelbutton.addTarget(self, action:#selector(self.toLogin(_:)), for: .touchUpInside)
        labelbutton.setTitleColor(UIColor.white, for: .normal)
        labelbutton.contentHorizontalAlignment = .right
        labelbutton.titleLabel?.font = UIFont.systemFont(ofSize: 18.00)
        
       
        
        let button = UIButton(type: .custom)
         button.addTarget(self, action:#selector(self.toLogin(_:)), for: .touchUpInside)
         button.frame = CGRect(x: 0, y: 0, width: 32, height: 32)
         button.setTitleColor(UIColor.white, for: .normal)
         button.setTitleColor(UIColor.white, for: .highlighted)
        
      
        var buttomItem : UIBarButtonItem = UIBarButtonItem()
        buttomItem.customView = button
        buttomItem.target = self
        buttomItem.action = &quot;ToLogin&quot;
        
        var labelItem : UIBarButtonItem = UIBarButtonItem()
        labelItem.customView = labelbutton
        labelItem.target = self
        labelItem.action = &quot;ToLogin&quot;
        
        
        if let user = PFUser.current() {
            print(&quot;LOGIN : checkiando si existe usuario &quot;)
                labelbutton.setTitle(USERNAME, for: UIControlState.normal)
                labelbutton.sizeToFit()
            
            if(user[&quot;profile_photo_url&quot;] != nil) {
                print(&quot; ENCONTRO PROFILE PHOTO URL NOT NIL Y ES \(user[&quot;profile_photo_url&quot;])&quot;)
                let photoURL = user[&quot;profile_photo_url&quot;] as! String
                let a = LoginService.sharedInstance
                a.downloadImage(url: photoURL, complete: { (complete) in
                    
                    if (complete) {
                  
                        button.setImage(LoginService.sharedInstance.profile_photo! , for: UIControlState.normal)
                        
                        button.layer.cornerRadius = 0.5 * button.bounds.size.width
                       // button.imageView!.contentMode = .scaleAspectFit
                       // button.imageView!.frame = CGRect(x: 0, y: 0, width: 40, height: 40)
                        //button.imageView!.contentMode = .scaleAspectFit
                        //button.imageView!.clipsToBounds = true
                        //button.imageView!.layer.cornerRadius = 60
                        button.clipsToBounds = true
                        self.NavigationItem.rightBarButtonItems = [buttomItem,labelItem]
                    }
                    
                    
                })
            } else {
                    self.NavigationItem.rightBarButtonItem = labelItem
                
            }
                print(&quot; EL FRAME DEL BUTTON ES \(button.frame)&quot;)
            
        } else {
   
            labelbutton.setTitle(&quot;Login&quot;, for: UIControlState.normal)
            labelbutton.sizeToFit()
            self.NavigationItem.rightBarButtonItem = labelItem
    
        }
   
[![enter image description here][1]][1]


  [1]: https://i.stack.imgur.com/zuB9A.png

navigation bar rightbaritem image-button bug iOS 11

I usually use custom UIColors on iOS using extensions with Swift, but now with iOS 11/ Xcode 9 we can create Colors Sets. How can we use them?

**Update - Tip**

As @Cœur says we can drag&amp;drop de color, and use it like a UIColor object and a possible solution could be use it as a extension:

[![UIColor as an extension][1]][1] 

 Or as a constant:

[![UIColor as a constant][2]][2]

Now I wanna know if we can access them like an UIImage access to an Asset Image or not, like:

    UIImage(named: &quot;image-name&quot;) -&gt; UIColor(named: &quot;color-name&quot;)
    


  [1]: https://i.stack.imgur.com/2bJpe.png
  [2]: https://i.stack.imgur.com/3cpV9.png

How can we use Assets Catalog Color Sets?

I am leasing a self signed certificate using `NSMutableURLRequest` and when the certificate is anchored using a custom certificate with `SecTrustSetAnchorCertificates` `IOS 11` fails with the following error message:

    refreshPreferences: HangTracerEnabled: 1
    refreshPreferences: HangTracerDuration: 500
    refreshPreferences: ActivationLoggingEnabled: 0 ActivationLoggingTaskedOffByDA:0
    ATS failed system trust
    System Trust failed for [1:0x1c417dc40]
    TIC SSL Trust Error [1:0x1c417dc40]: 3:0
    NSURLSession/NSURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9802)
    Task &lt;721D712D-FDBD-4F52-8C9F-EEEA28104E73&gt;.&lt;1&gt; HTTP load failed (error code: -1200 [3:-9802])
    Task &lt;721D712D-FDBD-4F52-8C9F-EEEA28104E73&gt;.&lt;1&gt; finished with error - code: -1200


What used to work for `IOS 10` no longer works in `IOS 11`. 

I am aware that `IOS 11` no longer supports the following:

- RC4 3DES-CBC AES-CBC
- MD5 SHA-1
- &lt;2048-bit RSA Pub Keys - All TLS connections to servers
- http:// 
- SSLv3 
- TLS 1.0 
- TLS 1.1

And the certificate does not use these except for one fingerprint, which is `SHA-1`, but a `SHA-256` fingerprint is also listed.


And by adding the following we can bypass the ATS (App Transport Security) error:

    &lt;key&gt;NSAppTransportSecurity&lt;/key&gt;
    &lt;dict&gt;
            &lt;key&gt;NSExceptionDomains&lt;/key&gt;
            &lt;dict&gt;
                &lt;key&gt;mydomain.com&lt;/key&gt;
                &lt;dict&gt;
                    &lt;!--Include to allow subdomains--&gt;
                    &lt;key&gt;NSIncludesSubdomains&lt;/key&gt;
                    &lt;true/&gt;
                    &lt;key&gt;NSExceptionRequiresForwardSecrecy&lt;/key&gt;
                    &lt;false/&gt;
                &lt;/dict&gt;
            &lt;/dict&gt;
    &lt;/dict&gt;


By installing the root / anchor certificate onto the phone itself also works without the need to whitelist the mydomain.com.

Does this mean that ATS no longer supports self-signed certificates?

The following worked in `IOS 10`:

    SecTrustSetAnchorCertificates(serverTrust, (__bridge CFArrayRef)certs);

Using `nscurl` on a Mac shows many failures, and after installing the root certificate into the &quot;System&quot; Keystore, `nscurl` succeeds.
I did this on `macOS 10.12.6`.    

    nscurl --verbose --ats-diagnostics https://


How can I make this work with a custom certificate, but without the need to install certificates or whitelist the domain?




iOS 11: ATS (App Transport Security) no longer accepts custom anchor certs?

I&#39;m looking for more information on the message below. Xcode 9 seems to be hanging for a couple minutes already...

**How can I tell Xcode 9 to quickly recognize my previously used device updated to iOS 11?**

&gt; .Alex’s iPhone is busy: Preparing debugger support for .Alex’s iPhone  
Xcode will continue when .Alex’s iPhone is finished.

[![Xcode screenshot for above error message][1]][1]

[1]: https://i.stack.imgur.com/uFf0d.png

Fixing Xcode 9 issue: &quot;iPhone is busy: Preparing debugger support for iPhone&quot;

As of now I would like to opt out of the new option iOS 11 gives, that is to suggest passwords in the app. When I run the app on iOS 11 I get the autofill option on top of the keyboard and my username and password textfield don&#39;t even show up.

So, my question is, how can I disable the new password autofill feature all together so the key on the keyboard is not shown at all and the overall behavior is the same as pre iOS 11?

[![enter image description here][1]][1]


  [1]: https://i.stack.imgur.com/ex9u3.png

iOS 11 disable password autofill accessory view option?

I have my `UISearchBar` being part of the navigation bar like:

     let searchBar = UISearchBar()
     //some more configuration to the search bar
     .....
     navigationItem.titleView = searchBar


After updating to `iOS 11` something weird happened to the search bar in my app. On `iOS 10` and prior I had my navigation bar looking like:

[![enter image description here][1]][1]


Now with `iOS 11` I have: 

[![enter image description here][2]][2]

As you can see there is difference in the rounding of the two search bars which does not bothers me. The problem is that the search bar increases the height of the navigation bar. So when I go to another controller it looks weird too:

[![enter image description here][3]][3]

In fact that weird black line&#39;s height plus the current navigation bar&#39;s height is equal to the height of navigation bar shown in the second picture ... 

Any ideas how to get rid of the black line and having consistent navigation bar height across all view controllers ? 

  [1]: https://i.stack.imgur.com/1VpIT.png
  [2]: https://i.stack.imgur.com/GpeXA.png
  [3]: https://i.stack.imgur.com/ec5fQ.png


UISearchBar increases navigation bar height in iOS 11

I just rebuilt my app with the iOS 11 SDK in an attempt to remove the `blue banner` that is now always appearing. I thought - &quot;Brilliant, that worked&quot;, only to discover that location services are now not working at all.

The application used to work with iOS 10 - Has anybody heard anything? 

Location Services not working in iOS 11

With iOS 11 safari, input textbox cursor are outside of input textbox. We did not get why it is having this problem. As you can see my focused text box is email text input but my cursor is outside of it. This only happens with iOS 11 Safari 

[![Problem][1]][1]


  [1]: https://i.stack.imgur.com/34d6d.png

iOS 11 Safari bootstrap modal text area outside of cursor

If I copy something from textedit or web and paste it to localizable file it shows this compilation error. If I type those in localizable file it does not show any error. I am assuring you that I using the correct format and &#39;;&#39; in the file.

    &quot;New&quot; = &quot;New&quot;;
    &quot;In Progress&quot; = &quot;In Progress&quot;;
    &quot;Waiting&quot; = &quot;Waiting&quot;;
    &quot;Closed&quot; = &quot;Closed&quot;;


Localizable.strings - The data couldn’t be read because it isn’t in the correct format

Wireless debugging was recently added as a feature in Xcode 9, iOS 11, and tvOS 11. Apple TV 4K doesn&#39;t have a USB port, so it requires wireless debugging. How do you perform this wireless debugging in Xcode?

How do you perform wireless debugging in Xcode 9 with iOS 11, Apple TV 4K, etc?

Now in iOS 11, the `sizeThatFits` method is not called from `UINavigationBar` subclasses. Changing the frame of `UINavigationBar` causes glitches and wrong insets.
So, any ideas how to customize navbar height now?

iOS 11 navigation bar height customizing

With ObjectiveC I am developing a SingleView app targeting iOS 11 having one view controller/view. In the Main.storyboard on top of the view I&#39;ve dropped a WebKit View (WKWebView). 

I am seeing a crash in both the Simulator and on an iPhone 6 running iOS 11.0.1 :

**Terminating app due to uncaught exception &#39;NSInvalidUnarchiveOperationException&#39;, reason: &#39;Could not instantiate class named WKWebView&#39;**


Do I need anything else to have it working ? Looks like it&#39;s unable to instantiate WKWebView upon waking from storyboard.


Other details:

 - Xcode version 9.0 9A235
 - When I remove the WKWebView from the Storyboard the crash goes away
 - App Base SDK - latest iOS (iOS 11); Deployment target 11.0
 - Using the WebView(deprecated) -- UIWebView, it works
 - I did not attempt to instantiate it manually


 
Crash stack:

    2017-11-06 18:38:27.765519+0200 XYZZMap[15689:1093338] *** Terminating app due to uncaught exception &#39;NSInvalidUnarchiveOperationException&#39;, reason: &#39;Could not instantiate class named WKWebView&#39;
    *** First throw call stack:
    (
    	0   CoreFoundation                      0x00000001056d01cb __exceptionPreprocess + 171
    	1   libobjc.A.dylib                     0x0000000105032f41 objc_exception_throw + 48
    	2   CoreFoundation                      0x0000000105744b95 +[NSException raise:format:] + 197
    	3   UIKit                               0x000000010692d2c0 UINibDecoderDecodeObjectForValue + 323
    	4   UIKit                               0x000000010692d5db UINibDecoderDecodeObjectForValue + 1118
    	5   UIKit                               0x000000010692d172 -[UINibDecoder decodeObjectForKey:] + 89
    	6   UIKit                               0x00000001062f866b -[UIView initWithCoder:] + 969
    	7   UIKit                               0x000000010692d43d UINibDecoderDecodeObjectForValue + 704
    	8   UIKit                               0x000000010692d172 -[UINibDecoder decodeObjectForKey:] + 89
    	9   UIKit                               0x00000001066dd1a7 -[UIRuntimeConnection initWithCoder:] + 178
    	10  UIKit                               0x000000010692d43d UINibDecoderDecodeObjectForValue + 704
    	11  UIKit                               0x000000010692d5db UINibDecoderDecodeObjectForValue + 1118
    	12  UIKit                               0x000000010692d172 -[UINibDecoder decodeObjectForKey:] + 89
    	13  UIKit                               0x00000001066dc3a4 -[UINib instantiateWithOwner:options:] + 1262
    	14  UIKit                               0x00000001063f8d07 -[UIViewController _loadViewFromNibNamed:bundle:] + 383
    	15  UIKit                               0x00000001063f9610 -[UIViewController loadView] + 177
    	16  UIKit                               0x00000001063f9941 -[UIViewController loadViewIfRequired] + 195
    	17  UIKit                               0x00000001063fa19e -[UIViewController view] + 27
    	18  UIKit                               0x00000001062cdd17 -[UIWindow addRootViewControllerViewIfPossible] + 122
    	19  UIKit                               0x00000001062ce41f -[UIWindow _setHidden:forced:] + 294
    	20  UIKit                               0x00000001062e12bf -[UIWindow makeKeyAndVisible] + 42
    	21  UIKit                               0x0000000106255015 -[UIApplication _callInitializationDelegatesForMainScene:transitionContext:] + 4711
    	22  UIKit                               0x000000010625a245 -[UIApplication _runWithMainScene:transitionContext:completion:] + 1720
    	23  UIKit                               0x0000000106615c6c __111-[__UICanvasLifecycleMonitor_Compatability _scheduleFirstCommitForScene:transition:firstActivation:completion:]_block_invoke + 924
    	24  UIKit                               0x00000001069e33ef +[_UICanvas _enqueuePostSettingUpdateTransactionBlock:] + 153
    	25  UIKit                               0x0000000106615865 -[__UICanvasLifecycleMonitor_Compatability _scheduleFirstCommitForScene:transition:firstActivation:completion:] + 249
    	26  UIKit                               0x00000001066160c3 -[__UICanvasLifecycleMonitor_Compatability activateEventsOnly:withContext:completion:] + 668
    	27  UIKit                               0x0000000106f73c11 __82-[_UIApplicationCanvas _transitionLifecycleStateWithTransitionContext:completion:]_block_invoke + 262
    	28  UIKit                               0x0000000106f73aca -[_UIApplicationCanvas _transitionLifecycleStateWithTransitionContext:completion:] + 444
    	29  UIKit                               0x0000000106c61b9c __125-[_UICanvasLifecycleSettingsDiffAction performActionsForCanvas:withUpdatedScene:settingsDiff:fromSettings:transitionContext:]_block_invoke + 420
    	30  UIKit                               0x0000000106e5cc3e _performActionsWithDelayForTransitionContext + 100
    	31  UIKit                               0x0000000106c61998 -[_UICanvasLifecycleSettingsDiffAction performActionsForCanvas:withUpdatedScene:settingsDiff:fromSettings:transitionContext:] + 231
    	32  UIKit                               0x00000001069e2a4c -[_UICanvas scene:didUpdateWithDiff:transitionContext:completion:] + 392
    	33  UIKit                               0x0000000106258ac6 -[UIApplication workspace:didCreateScene:withTransitionContext:completion:] + 523
    	34  UIKit                               0x0000000106821523 -[UIApplicationSceneClientAgent scene:didInitializeWithEvent:completion:] + 369
    	35  FrontBoardServices                  0x000000010b539158 -[FBSSceneImpl _didCreateWithTransitionContext:completion:] + 338
    	36  FrontBoardServices                  0x000000010b541c4d __56-[FBSWorkspace client:handleCreateScene:withCompletion:]_block_invoke_2 + 235
    	37  libdispatch.dylib                   0x00000001096b643c _dispatch_client_callout + 8
    	38  libdispatch.dylib                   0x00000001096bbaf4 _dispatch_block_invoke_direct + 592
    	39  FrontBoardServices                  0x000000010b56d672 __FBSSERIALQUEUE_IS_CALLING_OUT_TO_A_BLOCK__ + 24
    	40  FrontBoardServices                  0x000000010b56d328 -[FBSSerialQueue _performNext] + 464
    	41  FrontBoardServices                  0x000000010b56d897 -[FBSSerialQueue _performNextFromRunLoopSource] + 45
    	42  CoreFoundation                      0x00000001056732b1 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
    	43  CoreFoundation                      0x0000000105712d31 __CFRunLoopDoSource0 + 81
    	44  CoreFoundation                      0x0000000105657c19 __CFRunLoopDoSources0 + 185
    	45  CoreFoundation                      0x00000001056571ff __CFRunLoopRun + 1279
    	46  CoreFoundation                      0x0000000105656a89 CFRunLoopRunSpecific + 409
    	47  GraphicsServices                    0x000000010be609c6 GSEventRunModal + 62
    	48  UIKit                               0x000000010625bd30 UIApplicationMain + 159
    	49  XYZZMap                             0x00000001047274bf main + 111
    	50  libdyld.dylib                       0x0000000109732d81 start + 1
    	51  ???                                 0x0000000000000001 0x0 + 1
    )
    libc++abi.dylib: terminating with uncaught exception of type NSException


Thanks!

iOS11 WKWebview crash due to NSInvalidUnarchiveOperationException

Working with my first application for learning purposes. It goes well but has met into a problem with Xcode. When I try to run the application on the iPhone simulator this message always pops up &quot;This app could not be installed at this time.&quot; 

[![screenshot][1]][1]

What is wrong? There are no errors when trying to build the app. Has tried to clean the build. Reinstall pods. Restarted Xcode. Erased all settings on the simulator device, however, the problems still exist. 

The error message does not give me any information. Is there another logfile I could look into or something? 


  [1]: https://i.stack.imgur.com/5Ahpd.png

Xcode: &quot;This app could not be installed at this time.&quot;

Seeing a behavior on iOS11 with a navigationItem.titleView where the width of the titleView is not the full width of the screen.

I have a custom view that I set as the titleView. Previous to iOS11 the view would fill the navigation bar area. But iOS 11 it is not resizing to fill the width of the screen.

I&#39;ve tried setting the frame of the view before setting titleView but no luck. I&#39;ve tried to force the titleViews superview to layout constraints as well but no luck. 

Screenshots attached:

iOS10:

[![enter image description here][1]][1]


iOS11:

[![enter image description here][2]][2]

Anyone else experience this?


  [1]: https://i.stack.imgur.com/R9Lt8.png
  [2]: https://i.stack.imgur.com/O6cfg.png

iOS 11 navigationItem.titleView Width Not Set

With iOS 11 Apple has redesigned the UISearchBar by making the corners rounder and the height bigger. Adding a UISearchBar to the navigationBar is pretty simple by just setting it as the titleView of the navigationItem using `navigationItem.titleView = searchBar`.

However, in iOS 11 it does not seem to work anymore as expected.
Have a look at the screens where we compare the same setup using iOS 10 and iOS 11

**iOS 10**
[![enter image description here][1]][1] 

**iOS 11**
[![enter image description here][2]][2]


  [1]: https://i.stack.imgur.com/r70hL.png
  [2]: https://i.stack.imgur.com/HCVEW.png

You can clearly see that the SearchBar increases the size of the NavigationBar but the bar buttons do not get aligned correctly. Also the searchBar does not use the available space on the left anymore.

Putting the searchBar into a wrapper view to get the cancel button on iPad as described here https://stackoverflow.com/questions/30474494/cancel-button-is-not-shown-in-uisearchbar also does not seem work anymore since the searchBar is then not visible at all.

If anyone has similar issues or already knowns how to fix/improve this I would be very thankful.

This was built using Xcode 9 Beta 4. Maybe future releases will fix this issue.

**UPDATE:**

Since this does not get fixed we decided to use following solution.
We added a new UIBarButtonItem to the NavBar which then presents a new ViewController where we only put a searchBar and nothing else into the NavBar which seems to work. Using the selected answer may be the best solution since Apple with iOS 11 wants us to use this new design even if it does not give us the result we originally wanted. Another way to possible solve this could be a custom SearchBar but this is another topic.

iOS 11 SearchBar in NavigationBar

iOS 11 Beta 1 uses the increased navigation-bar title for almost all system-apps (it started doing this in iOS 10 and the Music app). I am wondering if Apple has a public API for this coming in iOS 11, or whether it will stay private for now. 

The behavior is that the title has an increased font-size, is left aligned and will move to the navigation-bar once the user scrolls down. I&#39;ve attached some screens showing this behavior in the Messages app here:

[![enter image description here][1]][1]

Although I could not find any reference in the `UINavigationController` and `UINavigationBar` so far, maybe someone knows some more details!


  [1]: https://i.stack.imgur.com/vOITO.png

Use the increased navigation-bar title in iOS 11

I have problem with application using XIBs without autolayout. I don&#39;t know if this is important information. 

I have UILabel with 2 lines using word wrap. In iOS 10 word wrap was working correctly, and first line contained one word + special character, for example ampersand. Example:

[![UiLabel on ios 10][1]][1]


Then on iOS 11 word wrap is working somehow wrong and puts ampresand to the second line:

[![UiLabel on ios 11][2]][2]

This is problematic as longer words, that normally fitted on second line now are not being shown correctly. Any idea what has changed? I know about safeArea but it doesn&#39;t look like reason. Any ideas how to move that ampersand to the top where is plenty of space for it?

Rest of the settings: [![size inspector][3]][3]


  [1]: https://i.stack.imgur.com/y5EZh.png
  [2]: https://i.stack.imgur.com/Xr0R4.png
  [3]: https://i.stack.imgur.com/rC6Hc.png

All Ios11 Solutions on Gang of Coders

Total of 32 Ios11 Solutions