In order to get rid of this error un check clip to bounds option and put scale to fill to view to all view,UIStackView you have used in your project.

This is a bug in iOS, and still exists in the latest version, iOS 9.1. If you&#39;re reading this, please do us all a favor and file a bug report with Apple.

You may duplicate my radar (id: 23666339), which can be viewed on Open Radar here: [https://openradar.appspot.com/23666339][1]

The bug causes the keyboard to take forever to appear, and exists only on iPad as well as the iPad simulators.

**UPDATE:** This issue has been resolved as of iOS 9.2 (13C75).

  [1]: https://openradar.appspot.com/radar?id=4947771354251264

It could happen because you changed drawing attribute of the StackView:

[![enter image description here][1]][1]


  [1]: https://i.stack.imgur.com/fvLaj.png

when I set clips to bounds to true I get this warning

In case anybody is facing this issue because of a UIStackView in iOS 14, please check out this article:

https://useyourloaf.com/blog/stack-view-background-color-in-ios-14/

Long story short:

In iOS 14, UIStackView has changed from using a CATransformLayer to using a CALayer. I saw this first mentioned by Renaud Lienhart (@layoutsubviews) and then confirmed by David Duncan (@rincewindsama). This change is not (yet) mentioned in any release note or documentation (bug report FB8363575).

**Problem Warning**  -&gt; &lt;CATransformLayer: 0x600000946e40&gt; - changing property masksToBounds in transform-only layer, will have no effect

**Solution = Simply uncheck the clip to bound from UIstackview box.**

[![enter image description here][1]][1]


  [1]: https://i.stack.imgur.com/OnYM8.png

I&#39;ve been using `PDFTK` Server on `OSX pre 10.11` for over a year without any issues running commands on the command line.

After installing OSX 10.11 beta, I can no longer run any `PDFTK` Server commands on the command line.  It does not throw any error, all the commands I try to execute just hang indefinitely.

I installed from a pkg I downloaded from the `PDFTK` Server website as always: 

https://www.pdflabs.com/tools/pdftk-server/

I&#39;ve also tried installing from source with Homebrew.  The installation works, but I get the same results, the commands just hang in the terminal:

[Homebrew tap][1]

**I&#39;ve sent in the complaint to Apple via their Feedback Assistant application that gets installed when installing the beta two months ago without a response.**

I&#39;ve been told regarding the Apple Feedback Assistant:

&gt; You likely won&#39;t ever receive a response. Apple only replies through
&gt; Feedback Assistant for major bugs of the operating system where they
&gt; need additional information. It is not a way to obtain support, even
&gt; less so for a third-party application. 


&lt;strike&gt;**I&#39;ve also reached out to [PDF Labs][2], the makers of the package, without response.**&lt;/strike&gt;



**On [MacPorts][3] they&#39;re having an issue with the build on OS X 10.11, does this mean that there is a compatibility issue with PDFtk and 10.11 at the software level?**

I&#39;ve searched the web for a clue as to what might be causing the issue and how to fix it, but have found nothing tangible.

On OS X, I don&#39;t know how to go about figuring out if there is now a permission or path or even a Java issue after the upgrade.

Any help either trouble shooting the root cause or offering a fix is appreciated. 


----------


**UPDATE 1:**

I heard back from [Sid Steward at PDF Labs][2]:

&gt; We have been wrestling with this almost as long as the beta has been
&gt; out. We are still working on it. There appears to be an
&gt; incompatibility with one of the (non-Apple) libraries that pdftk uses
&gt; and OS X 10.11. Presently I am installing yet another update to
&gt; Apple&#39;s developer tools with the hope that it will solve the problem.
&gt; I will update you with our progress.


----------

**UPDATE 2:** 

[Sid Steward at PDF Labs][2] again:

&gt; It looks like there are two threads running under pdftk, and that they
&gt; are deadlocked. That means that each thread is waiting for the other
&gt; to finish. I&#39;m not an expert here, but that&#39;s my impression. Here is a
&gt; screenshot from Mac&#39;s Activity Monitor to illustrate:

[![enter image description here][4]][4]

&gt; The above snapshot is from trying to run the pdftk binary currently on
&gt; our site on OS X 10.11. The libgcj library noted above comes with
&gt; pdftk, where the others are OS X libraries.
&gt; 
&gt; As I say, I just installed Xcode 7.0.1, which was released yesterday
&gt; on the App store. I will now attempt to use these tools to build
&gt; pdftk.


----------

**UPDATE 3:**

[MacPorts][3] is working the build issue with PDFtk, this is an [update on that thread][3] (Note: this is unrelated to PDFtk Labs):


&gt; This is due to the recompilation of libunwind in 10.11 using Apple
&gt; Clang 7 producing new valid optimizations (according to Apple) that
&gt; tickle an unknown bug in FSF boehm-gc.

​https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66848

&gt; Don&#39;t expect any fixes from Apple as they can&#39;t touch the GPLv3 code
&gt; to look at the FSF boehm-gc problem (unless they used the gcc43
&gt; package which should still be GPLv2). That this issue is triggered by
&gt; the recompilation of libunwind is demonstrated by that fact that
&gt; substituting the libunwind.dylib from 10.10 eliminates both the
&gt; boehm-gc and gcj failures.
&gt; 
&gt; Note that is was filed as radr://21372179, &quot;the FSF boehm-gc library
&gt; built on 10.10 fails to pass its tests on 10.11&quot; but closed as being
&gt; an FSF boehm-gc bug.

----------

**UPDATE 4:**

[MacPorts][3] found a way to solve the build issue, this is an [update on that thread][3]

&gt; The attached Portfile.diff (when used with the proposed gcc5 update on
&gt; [#49227][5] which fixes gcj) solves the build issue with pdftk.

----------

**UPDATE 5:** 

[Sid Steward at PDF Labs][2] has a successful build, his feedback:

&gt; A fix for MacPorts gcc5 allowed me to build a working pdftk that
&gt; merges PDFs on El Capitan. The fix was added to the ticket you had
&gt; posted to:

[MacPorts][3]

&gt; I will proceed to fully test this pdftk before packing it up into an
&gt; installer. This process could take a couple days. 


----------


  [1]: https://github.com/docmunch/homebrew-pdftk
  [2]: https://www.pdflabs.com/company/contact/
  [3]: https://trac.macports.org/ticket/48528
  [4]: http://i.stack.imgur.com/3fa38.png
  [5]: https://trac.macports.org/ticket/49227

PDFtk Server on OS X 10.11

With Xcode 6.3 there were new annotations introduced for better expressing the intention of API&#39;s in **Objective-C** (and to ensure better Swift support of course). Those annotations were of course `nonnull`, `nullable` and `null_unspecified`.

But with Xcode 7, there is a lot of warnings appearing such as:

&gt;Pointer is missing a nullability type specifier (_Nonnull, _Nullable or _Null_unspecified).

In addition to that, Apple uses another type of nullability specifiers, marking their C code ([source](https://developer.apple.com/videos/wwdc/2015/?id=401)):

`CFArrayRef __nonnull CFArrayCreate( CFAllocatorRef __nullable allocator, const void * __nonnull * __nullable values, CFIndex numValues, const CFArrayCallBacks * __nullable callBacks);`

So, to sum up, we now have these 3 different nullability annotations:

- `nonnull`, `nullable`, `null_unspecified`
- `_Nonnull`, `_Nullable`, `_Null_unspecified`
- `__nonnull`, `__nullable`, `__null_unspecified`

Even though I know why and where to use which annotation, I&#39;m getting slightly confused by which type of annotations should I use, where and why. This is what I could gather:

- For properties I should use `nonnull`, `nullable`, `null_unspecified`.
- For method parameters I should use `nonnull`, `nullable`, `null_unspecified`.
- For C methods I should use `__nonnull`, `__nullable`, `__null_unspecified`.
- For other cases, such as double pointers I should use `_Nonnull`, `_Nullable`, `_Null_unspecified`.

But I&#39;m still confused as to why we have so many annotations that basically do the same thing.

So my question is:

**What is exact difference between those annotations, how to correctly place them and why?**


Difference between nullable, __nullable and _Nullable in Objective-C

I am receiving this warning in the debugger console when I launch my app on **iPad Xcode 7 beta 6**. There was no such warning till **Xcode 6**. I don&#39;t understand why it may have come and that too, only on iPad.

According to [an Apple forum thread][1] it could be a bug from Apple&#39;s side. Has anyone found a solution for this?


  [1]: &lt;https://forums.developer.apple.com/thread/13716&gt;

&quot;changing property masksToBounds in transform-only layer, will have no effect&quot; in Xcode 7

I am receiving this warning in the debugger console when I launch my app on iPad Xcode 7 beta 6. There was no such warning till Xcode 6. I don't understand why it may have come and that too, only on iPad.
According to <a>an Apple forum thread</a> it could be a bug from Apple's side. Has anyone found a solution for this?

I have an iOS app that I need to extend to tvOS.
All the information that I found are explaining how to start from scratch!
Is there any way to extend my app to tvOS or I should start a new project with it?

**Update1:**
My question is: How to extend my existing project to support tvOS without building it from scratch? 

**Update2:**
Jess Bower point on Apple&#39;s website:
&gt; Empower customers to enjoy their favorite apps on both iOS and the new
&gt; Apple TV with a single purchase by enabling universal purchase for
&gt; your app on the App Store.

Which means that we need to create a new bundle on our existing project and enable &quot;universal&quot; purchase so it will count as one app on App Store.


How to extend iOS app to tvOS

I am trying to simulate a force touch using Xcode 7 GM on the iPhone 6S or iPhone 6S Plus simulator.  In particular, I am trying to simulate the force touch on the icon of the test app which is implementing Application Shortcuts.

Let me know if there is a solution to simulate this, I tried the long press which the Watch simulator uses to simulate force touch, didn&#39;t work since the iPhone captures it as a long press gesture.

Update: I downloaded the ViewControllerPreview Sample code from Apple.  Running their sample application I see that the simulator, although an iPhone 6s, does not support for 3D / force touch feature.  I am still unsure if it would support the feature if I were to be using a macbook with a force touch enabled trackpad.

[![enter image description here][1]][1]

EDIT:  Can someone with a macbook that has a force touch trackpad attempt to use the force touch on the trackpad to simulate 3D touch on the iPhone 6s or 6s Plus simulator?  My theory is that you can maybe use the force touch trackpad on the new MacBooks to simulate the 3D touch on new iPhone simulators.  Add a comment noting the results if you try it and I can update the post.

EDIT2:  It seems that Force Touch trackpads on the newer model macbook pros do not help.


  [1]: http://i.stack.imgur.com/rIGxe.png

Simulate force touch / 3D touch on iPhone 6S or iPhone 6S Plus simulators

My app shares photo on Instagram, to do this it first saves it on a temporary directory:

    let writePath = NSTemporaryDirectory().stringByAppendingPathComponent(&quot;instagram.igo&quot;)

It was working on `Swift 1.2`, but does not work on `Swift 2.0`.

Given error message is: 
&gt;stringByAppendingPathComponent is unavailable: use URLByAppendingPathComponent on NSURL instead.

stringByAppendingPathComponent is unavailable

I just re-wrote an app in Swift 2.  I&#39;m trying to upload the app to iTunesConnect (via Xcode 7 GM) for internal testing.

I wrestled with an &quot;Invalid Swift Support&quot; error for awhile ([which has other, related questions][1]) ... but now it&#39;s changed to something a little different.

The error from Apple now says:

**Invalid Swift Support**

The files libswiftCoreLocation.dylib, libswiftCoreMedia.dylib, libswiftCoreData.dylib, libswiftAVFoundation.dylib don’t match 

/Payload/App.app/Frameworks/libswiftCoreLocation.dylib, /Payload/App.app/Frameworks/libswiftCoreMedia.dylib, /Payload/App.app/Frameworks/libswiftCoreData.dylib, /Payload/App.app/Frameworks/libswiftAVFoundation.dylib

***Make sure the files are correct*** (?), rebuild your app, and resubmit it. 

Don’t apply post-processing to 

/Payload/App.app/Frameworks/libswiftCoreLocation.dylib, /Payload/App.app/Frameworks/libswiftCoreMedia.dylib, /Payload/App.app/Frameworks/libswiftCoreData.dylib, /Payload/App.app/Frameworks/libswiftAVFoundation.dylib.


I&#39;ve been unable to find similar errors by searching for &quot;Don’t apply post-processing&quot;, &quot;Make sure the files are correct, rebuild your app, and resubmit it&quot;, etc.

**Does anyone know how I can &quot;Make sure the files are correct&quot; --or-- have any other recommendations?  Thank you.**

  [1]: https://stackoverflow.com/questions/26163856/invalid-swift-support-invalid-implementation-of-swift

Invalid Swift Support - Files don’t match

In Xcode 7 GM I started to get this warning:

&gt; Pointer is missing a nullability type specifier (_Nonnull, _Nullable, or _Null_unspecified)

In the following function declaration (NSUserDefaults extension)

    - (void)setObject:(nullable id)value
               forKey:(NSString *)defaultName
        objectChanged:(void(^)(NSUserDefaults *userDefaults, id value))changeHandler
        objectRamains:(void(^)(NSUserDefaults *userDefaults, id value))remainHandler;

[![Screenshot][1]][1]

Why this warning is showing and how should I fix it?


  [1]: https://i.stack.imgur.com/c4TE2.png

Pointer is missing a nullability type specifier

Code below should get current location. But above error is generated. Function didUpdateLocations never gets called. 

Running this on a device (iPhone 5s)iOS 9.1. Info.plist has Required device capabilities and Privacy - Location usage description configured as shown in the attached image. Please help! 


    let locationManager = CLLocationManager()

    override func viewDidLoad() {
        super.viewDidLoad()
        locationManager.delegate = self
        locationManager.requestAlwaysAuthorization()
        locationManager.requestLocation()
    }

 
    func locationManager(manager: CLLocationManager,
        didFailWithError error: NSError) 
        print(error.description)
    }

    func locationManager(manager: CLLocationManager, didUpdateLocations
          locations: [CLLocation]) {        
     print(“got location”)
    }
 
[![Info.plist][1]][1]


  [1]: http://i.stack.imgur.com/psXKa.png

IOS 9 Error Domain=kCLErrorDomain Code=0 &quot;(null)&quot;

I have updated iPhone 6 plus to iOS 9 beta and trying to perform Facebook login but each time its presenting UIWebView with Facebook login form. 

I have Facebook sdk 

    FB_IOS_SDK_VERSION_STRING @&quot;3.24.0&quot;
    FB_IOS_SDK_TARGET_PLATFORM_VERSION @&quot;v2.2&quot;

And I am using following methods to perform Facebook Login 

        NSArray *permissions = @[@&quot;email&quot;,@&quot;user_birthday&quot;,@&quot;public_profile&quot;];
        
        
         FBSessionStateHandler completionHandler = ^(FBSession *session, FBSessionState status, NSError *error) {
             [self sessionStateChanged:session state:status error:error];
         };
         
         if ([FBSession activeSession].state == FBSessionStateCreatedTokenLoaded) {
         // we have a cached token, so open the session
             [[FBSession activeSession]openWithBehavior:FBSessionLoginBehaviorUseSystemAccountIfPresent
                                     fromViewController:nil
                                      completionHandler:completionHandler];
         } else {
             
         [self clearAllUserInfo];
        [[NSURLCache sharedURLCache] removeAllCachedResponses];

         // create a new facebook session
         FBSession *fbSession = [[FBSession alloc] initWithPermissions:permissions];
         [FBSession setActiveSession:fbSession];
         [fbSession openWithBehavior:FBSessionLoginBehaviorUseSystemAccountIfPresent
                  fromViewController:nil
                   completionHandler:completionHandler];
         }


I have following setting under plist file

    	&lt;key&gt;LSApplicationQueriesSchemes&lt;/key&gt;
    	&lt;array&gt;
    		&lt;string&gt;fbapi&lt;/string&gt;
    		&lt;string&gt;fbapi20130214&lt;/string&gt;
    		&lt;string&gt;fbapi20130410&lt;/string&gt;
    		&lt;string&gt;fbapi20130702&lt;/string&gt;
    		&lt;string&gt;fbapi20131010&lt;/string&gt;
    		&lt;string&gt;fbapi20131219&lt;/string&gt;
    		&lt;string&gt;fbapi20140410&lt;/string&gt;
    		&lt;string&gt;fbapi20140116&lt;/string&gt;
    		&lt;string&gt;fbapi20150313&lt;/string&gt;
    		&lt;string&gt;fbapi20150629&lt;/string&gt;
    		&lt;string&gt;fb-messenger-api20140430&lt;/string&gt;
    		&lt;string&gt;fbauth&lt;/string&gt;
    		&lt;string&gt;fbauth2&lt;/string&gt;
       &lt;array&gt;
Please let me know what I am missing here. First it is checking for `iPhone device Setting-&gt; Facebook credentials` but never open Facebook app for login. Seems it does not recognize Facebook app installed on device.

Native Facebook app does not open with Facebook login in iOS 9

My apps&#39; splash screens are all plain black after upgrading to iOS9.

Does anybody know why this is? Some of them are using a .xib splash screen and some are using images, but they&#39;re all just black now. Does an app have to be built with Xcode 7 for the splash screen to work in iOS9? Has anyone seen some documentation on whether this is an intended breaking change from Apple?

Thank you!

**UPDATE:** Looking through the apps again it seems my older apps, which only had a Launch image and no .xib are still displaying correctly, so the issue seems related to the launch screen .xib

**UPDATE2:**
As _hagi_ pointed out in the comment, after re-installing the very same binary it starts working again so the cause is probably that launch images are generated from the xib whenever the app is installed, and stored somewhere, and then when upgrading to iOS9, for some reason (unintended Apple bug most likely), the generated images are cleared, and the app ends up with no splash. And that&#39;s why the old-fashioned launch images are still safe and not affected by this, cause they&#39;re already baked into the app.

I&#39;ll report it as a bug to Apple.

iOS 9 Splash screen is black

I am facing the Problem when I have updated my Xcode to 7.0 or iOS 9.0.
Somehow it started giving me the Titled error

&gt; &quot;The resource could not be loaded because the App Transport Security
&gt; policy requires the use of a secure connection&quot;


Webservice Method:

    -(void)ServiceCall:(NSString*)ServiceName :(NSString *)DataString
    {
    NSURLSessionConfiguration *sessionConfiguration = [NSURLSessionConfiguration defaultSessionConfiguration];
        [sessionConfiguration setAllowsCellularAccess:YES];
        [sessionConfiguration setHTTPAdditionalHeaders:@{ @&quot;Accept&quot; : @&quot;application/json&quot; }];
        NSURLSession *session = [NSURLSession sessionWithConfiguration:sessionConfiguration];
        
        NSURL *url = [NSURL URLWithString:[NSString stringWithFormat:@&quot;%@&quot;,ServiceURL]];
        NSLog(@&quot;URl %@%@&quot;,url,DataString);
        // Configure the Request
        NSMutableURLRequest *request = [NSMutableURLRequest requestWithURL:url];
        [request setValue:[NSString stringWithFormat:@&quot;%@=%@&quot;, strSessName, strSessVal] forHTTPHeaderField:@&quot;Cookie&quot;];
        request.HTTPBody = [DataString dataUsingEncoding:NSUTF8StringEncoding];
        request.HTTPMethod = @&quot;Post&quot;;
        
        // post the request and handle response
        NSURLSessionDataTask *postDataTask = [session dataTaskWithRequest:request completionHandler:^(NSData *data, NSURLResponse *response, NSError *error)
                                              {
                                                  // Handle the Response
                                                  if(error)
                                                  {
                                                      NSLog(@&quot;%@&quot;,[NSString stringWithFormat:@&quot;Connection failed: %@&quot;, [error description]]);
                                                      
                                                      // Update the View
                                                      dispatch_async(dispatch_get_main_queue(), ^{
                                                          
                                                          // Hide the Loader
                                                          [MBProgressHUD hideHUDForView:[[UIApplication sharedApplication] delegate].window animated:YES];
                                                          
                                                          
                                                      });
                                                      return;
                                                  }
                                                  NSArray * cookies = [[NSHTTPCookieStorage sharedHTTPCookieStorage] cookiesForURL:request.URL];
                                                  for (NSHTTPCookie * cookie in cookies)
                                                  {
                                                      NSLog(@&quot;%@=%@&quot;, cookie.name, cookie.value);
                                                      strSessName=cookie.name;
                                                      strSessVal=cookie.value;
                                                      
                                                  }
                                                  
                                                  NSString *retVal = [[NSString alloc] initWithData:data encoding:NSUTF8StringEncoding];
    }];
    [postDataTask resume];
        
    }

The service is Running fine for Xcode earlier versions and iOS previous versions But when I have updated to Xcode 7.0 that is on iOS 9.0, it started to give me the Problem like following when I am calling the above web service method. The Logged Error which I am getting is:

&gt; Connection failed: Error Domain=NSURLErrorDomain Code=-1022 &quot;The
&gt; resource could not be loaded because the App Transport Security policy
&gt; requires the use of a secure connection.&quot;
&gt; UserInfo={NSUnderlyingError=0x7fada0f31880 {Error
&gt; Domain=kCFErrorDomainCFNetwork Code=-1022 &quot;(null)&quot;},
&gt; NSErrorFailingURLStringKey=**MyServiceURL**,
&gt; NSErrorFailingURLKey=**MyServiceURL**,
&gt; NSLocalizedDescription=The resource could not be loaded because the
&gt; App Transport Security policy requires the use of a secure
&gt; connection.}

I have tried Following Questions and answers but did not get any result there, is there any advance idea how I can remove that service call error?

1. [https://stackoverflow.com/questions/32069393/the-resource-could-not-be-loaded-is-ios9][1]
2. [https://stackoverflow.com/q/32427300][2]
3. [https://stackoverflow.com/a/32609970][3]


  [1]: https://stackoverflow.com/questions/32069393/the-resource-could-not-be-loaded-is-ios9
  [2]: https://stackoverflow.com/q/32427300
  [3]: https://stackoverflow.com/a/32609970

The resource could not be loaded because the App Transport Security policy requires the use of a secure connection

Installed the app on iPhone 6 iOS9 and here is what happened. Notice black bars on top and bottom. It works just fine on iOS8. How I can fix it?

I&#39;ve tried building with Xcode 6.4 &amp; 7. Same result.

(iPhone 5 used to run iPhone 4 apps like this)

[![enter image description here][1]][1]

  [1]: http://i.stack.imgur.com/4S93T.png

Content Type	Original Author	Original Content on Stackoverflow
Question	StudentX	View Question on Stackoverflow
Solution 1 - Ios	Amit Verma	View Answer on Stackoverflow
Solution 2 - Ios	T Blank	View Answer on Stackoverflow
Solution 3 - Ios	Паша Матюхин	View Answer on Stackoverflow
Solution 4 - Ios	Jeremie Vincke	View Answer on Stackoverflow
Solution 5 - Ios	Milan Savaliya M	View Answer on Stackoverflow

"changing property masksToBounds in transform-only layer, will have no effect" in Xcode 7

Ios Problem Overview

Ios Solutions

Solution 1 - Ios

Solution 2 - Ios

Solution 3 - Ios

Solution 4 - Ios

Solution 5 - Ios

Difference between nullable, __nullable and _Nullable in Objective-C

PDFtk Server on OS X 10.11

Attributions