Yes, an arm64 slice is there.  To see it, you need to use `lipo` from the iOS toolchain, not from the host system (which doesn’t know about arm64):

    xcrun -sdk iphoneos lipo -info $(FILENAME)

good old `file` can do the trick, too:

    $ file libTestFlight.a

    libTestFlight.a: Mach-O universal binary with 5 architectures
    libTestFlight.a (for architecture armv7):	current ar archive random library
    libTestFlight.a (for architecture armv7s):	current ar archive random library
    libTestFlight.a (for architecture i386):	current ar archive random library
    libTestFlight.a (for architecture x86_64):	current ar archive random library
    libTestFlight.a (for architecture cputype (16777228) cpusubtype (0)):	current ar archive random library

It seems that nobody at Apple cared to add the arm64 cputype to `file`, yet.

Interestingly, in the iOS 7 Tech Talk Videos (&quot;Architecting Modern Apps, Part 2&quot;, PDF page 35) they show a working file tool&#39;s output:

![enter image description here][1]

  [1]: http://i.stack.imgur.com/xswyC.png

For a `.framework` 


`lipo -info myFramework.framework/MyFramework`

I&#39;m looking for a way to include a layout programmatically instead of using the XML tag  `include` like in my example:

      &lt;include layout=&quot;@layout/message&quot;  
               android:layout_width=&quot;match_parent&quot; 
               android:layout_height=&quot;match_parent&quot; 
               android:layout_weight=&quot;0.75&quot;/&gt;

Need to change this parameter &quot;**layout=&quot;@layout/message**&quot; programmatically, please. 

Any idea how to do this?

How can I programmatically include layout in Android?


I was trying to use adb over TCP/IP. I have followed these steps

    adb tcpip 5555
    
    adb connect 194.68.0.100:5555


I have used my device for 2 days and now I am unable to connect to my IP address like when I do

    adb tcpip 5555

it doesn&#39;t respond anything. Anyone knows what could be the scenario.


adb connection over tcp not working now

I just built a static library for iOS with the build setting for Architectures set to `$(ARCHS_STANDARD_INCLUDING_64_BIT)`. 

I want to make sure that the .a library is properly including that architecture, but when i run `lipo -info` on it, I see:

&gt; Architectures in the fat file: library.a are: armv7 armv7s
&gt; (cputype (16777228) cpusubtype (0))

Does this mean that arm64 isn&#39;t included? If the lipo command can&#39;t tell me, is there another way to tell?

I&#39;m running Xcode 5 with the latest Command Line Tools installed.

How to check if a static library is built for 64-bit?

I just built a static library for iOS with the build setting for Architectures set to <code>$(ARCHS_STANDARD_INCLUDING_64_BIT)</code>.
I want to make sure that the .a library is properly including that architecture, but when i run <code>lipo -info</code> on it, I see:
> Architectures in the fat file: library.a are: armv7 armv7s
> (cputype (16777228) cpusubtype (0))
Does this mean that arm64 isn't included? If the lipo command can't tell me, is there another way to tell?
I'm running Xcode 5 with the latest Command Line Tools installed.

&lt;br&gt;
I tried many ways to set the status bar style (default or lightcontent) but can&#39;t get it to work on a per view controller basis. I can set the status bar style for the whole app only.

Does anyone have a hint?

I tried `UIViewControllerBasedStatusBarAppearance` 

and 

    -(UIStatusBarStyle)preferredStatusBarStyle{ 
        return UIStatusBarStyleLightContent; 
    }

but these methods don&#39;t work.

iOS 7 and later: set status bar style per view controller

I followed [this thread][1] to override `-preferredStatusBarStyle`, but it isn&#39;t called. 
Are there any options that I can change to enable it? (I&#39;m using XIBs in my project.)


  [1]: https://stackoverflow.com/questions/17678881/how-to-change-status-bar-text-color-in-ios-7

preferredStatusBarStyle isn&#39;t called

I&#39;m porting one of apps from iOS 6.1 to iOS 7. I&#39;m using a layout where there&#39;s a `UITextView` that has a fix width, but it&#39;s height is based on its contentsize. For iOS 6.1 checking the contentsize.height and setting it as the textview&#39;s frame height was enough, but it doesn&#39;t work on iOS 7. 

How can I then create a `UITextView` with a fixed width, but dynamic height based on the text it&#39;s showing?

NOTE: I&#39;m creating these views from code, not with Interface Builder.

iOS7 UITextView contentsize.height alternative

I want to set background for Navigation Bar to be **black** and all colors inside it to be **white**.&lt;br/&gt;

So, I used this code :

    [[UINavigationBar appearance] setTitleTextAttributes:
         [NSDictionary dictionaryWithObjectsAndKeys:
          [UIColor whiteColor],
          NSForegroundColorAttributeName,
          [UIColor whiteColor],
          NSForegroundColorAttributeName,
          [NSValue valueWithUIOffset:UIOffsetMake(0, -1)],
          NSForegroundColorAttributeName,
          [UIFont fontWithName:@&quot;Arial-Bold&quot; size:0.0],
          NSFontAttributeName,
          nil]];

But back button **text color**, **arrow** and **bar button** have still default **blue color**.&lt;br/&gt;
How to change those colors like on image below?&lt;br/&gt;


[![navigation bar][1]][1]


  [1]: http://i.stack.imgur.com/xwOa0.jpg

iOS 7 Navigation Bar text and arrow color

I&#39;m creating custom elements in my app and want to match the look and feel of the new iOS. iOS 7 introduced to us a very common lighter blue color, the default color or tint for several elements, including the system button, segmented control, etc. They&#39;ve made it easy to select the color using IB, as seen here:

![enter image description here][1]

However, I haven&#39;t found how to easily access the color programmatically. I checked out the [UIColor documentation][2], and there doesn&#39;t seem to be any accessor for the blue system color in the class itself.

Here&#39;s my question: does a simple accessor exist for this color? `[UIColor ?]` or something like it? If not, does someone know the exact **RGB values** for that color?


  [1]: http://i.stack.imgur.com/deFsk.png
  [2]: https://developer.apple.com/library/ios/DOCUMENTATION/UIKit/Reference/UIColor_Class/Reference/Reference.html

How can I get the iOS 7 default blue color programmatically?

I&#39;m trying to set a tintColor on my UIRefreshControl (building on iOS 7).
I enabled refreshing for the tableViewController in storyboard, then in my ViewController `viewDidLoad` method i did the following:

    [self.refreshControl setTintColor:[UIColor redColor]];

So now, when I pull to refresh, the color of the refresh control is red indeed:

![redSpiny][1]

I want my view to update automatically when it appears, so I did:

    - (void)viewDidAppear:(BOOL)animated{
        [self.refreshControl beginRefreshing];
    }

It didn&#39;t show the spinning wheel, according to https://stackoverflow.com/a/16250679/1809736, I added

    [self.tableView setContentOffset:CGPointMake(0, -self.refreshControl.frame.size.height) animated:NO];

to force show it.
It shows it, but now it is back to default color: 

![enter image description here][2]

 If I try manually to pull to refresh afterwards, it is red.

I tried building it on iOS6 and it works as it should, so is that an iOS7 bug?

P.S.: it is not a problem with the simulator, I tried building it on device, same bug.

P.P.S: I built an example project, can you tell me if you have the same bug or if there is a problem in my code? Here is the link: http://d.pr/f/pGrV

Thanks a lot !

 


  [1]: http://i.stack.imgur.com/CfRhA.png
  [2]: http://i.stack.imgur.com/btDMh.png

iOS 7 UIRefreshControl tintColor not working for beginRefreshing

**UPDATE**

Based on Tim&#39;s answer, I implemented the following in each view controller that had a scrollview (or subclass) that was part of my custom container:

    - (void)didMoveToParentViewController:(UIViewController *)parent
    {
        if (parent) {
            CGFloat top = parent.topLayoutGuide.length;
            CGFloat bottom = parent.bottomLayoutGuide.length;
    
            // this is the most important part here, because the first view controller added 
            // never had the layout issue, it was always the second. if we applied these
            // edge insets to the first view controller, then it would lay out incorrectly.
            // first detect if it&#39;s laid out correctly with the following condition, and if
            // not, manually make the adjustments since it seems like UIKit is failing to do so
            if (self.collectionView.contentInset.top != top) {
                UIEdgeInsets newInsets = UIEdgeInsetsMake(top, 0, bottom, 0);
                self.collectionView.contentInset = newInsets;
                self.collectionView.scrollIndicatorInsets = newInsets;
            }
        }

        [super didMoveToParentViewController:parent];
    }

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

I have custom container view controller called `SegmentedPageViewController`. I set this as a `UINavigationController&#39;s rootViewController`.

The purpose of `SegmentedPageViewController` is to allow a `UISegmentedControl`, set as the NavController&#39;s titleView, to switch between different child view controllers.

![enter image description here][1]

These child view controllers all contain either a scrollview, tableview, or collection view.

We&#39;re finding that the first view controller loads fine, correctly positioned underneath the navigation bar. But when we switch to a new
view controller, the navbar isn&#39;t respected and the view is set underneath the nav bar.

![enter image description here][2]

We&#39;re using auto layout and interface builder. We&#39;ve tried everything we can think of, but can&#39;t find a consistent solution.

Here&#39;s the main code block responsible for setting the first view controller and switching to another one when a user taps on the segmented control:

    - (void)switchFromViewController:(UIViewController *)oldVC toViewController:(UIViewController *)newVC
    {
        if (newVC == oldVC) return;

        // Check the newVC is non-nil otherwise expect a crash: NSInvalidArgumentException
        if (newVC) {

            // Set the new view controller frame (in this case to be the size of the available screen bounds)
            // Calulate any other frame animations here (e.g. for the oldVC)
            newVC.view.frame = self.view.bounds;

            // Check the oldVC is non-nil otherwise expect a crash: NSInvalidArgumentException
            if (oldVC) {
                // **** THIS RUNS WHEN A NEW VC IS SET ****
                // DIFFERENT FROM FIRST VC IN THAT WE TRANSITION INSTEAD OF JUST SETTING


                // Start both the view controller transitions
                [oldVC willMoveToParentViewController:nil];
                [self addChildViewController:newVC];

                // Swap the view controllers
                // No frame animations in this code but these would go in the animations block
                [self transitionFromViewController:oldVC
                                  toViewController:newVC
                                          duration:0.25
                                           options:UIViewAnimationOptionLayoutSubviews
                                        animations:^{}
                                        completion:^(BOOL finished) {
                                            // Finish both the view controller transitions
                                            [oldVC removeFromParentViewController];
                                            [newVC didMoveToParentViewController:self];
                                            // Store a reference to the current controller
                                            self.currentViewController = newVC;
                                        }];
            } else {

                // **** THIS RUNS WHEN THE FIRST VC IS SET ****
                // JUST STANDARD VIEW CONTROLLER CONTAINMENT

                // Otherwise we are adding a view controller for the first time
                // Start the view controller transition
                [self addChildViewController:newVC];

                // Add the new view controller view to the view hierarchy
                [self.view addSubview:newVC.view];

                // End the view controller transition
                [newVC didMoveToParentViewController:self];

                // Store a reference to the current controller
                self.currentViewController = newVC;
            }
        }

    }


  [1]: http://i.stack.imgur.com/O5t9X.png
  [2]: http://i.stack.imgur.com/70B7U.png

Content falls beneath navigation bar when embedded in custom container view controller.

I&#39;m writing an application that requires background location updates with **high accuracy and low frequency**.  The solution seems to be a background NSTimer task that starts the location manager&#39;s updates, which then immediately shuts down.  This question has been asked before:

https://stackoverflow.com/questions/6347503/how-do-i-get-a-background-location-update-every-n-minutes-in-my-ios-application

https://stackoverflow.com/questions/10235203/getting-user-location-every-n-minutes-after-app-goes-to-background?rq=1

https://stackoverflow.com/questions/13377750/ios-not-the-typical-background-location-tracking-timer-issue

https://stackoverflow.com/questions/15650139/ios-long-running-background-timer-with-location-background-mode

https://stackoverflow.com/questions/10706265/ios-full-time-background-service-based-on-location-tracking

but I have yet to get a **minimum example** working. After trying every permutation of the above accepted answers, I put together a starting point.  Entering background:

    - (void)applicationDidEnterBackground:(UIApplication *)application
    {
        self.bgTask = [[UIApplication sharedApplication] beginBackgroundTaskWithExpirationHandler:^{
            NSLog(@&quot;ending background task&quot;);
            [[UIApplication sharedApplication] endBackgroundTask:self.bgTask];
            self.bgTask = UIBackgroundTaskInvalid;
        }];
    
    
        self.timer = [NSTimer scheduledTimerWithTimeInterval:60
                                                      target:self.locationManager
                                                    selector:@selector(startUpdatingLocation)
                                                    userInfo:nil
                                                     repeats:YES];
    }

and the delegate method:

    - (void)locationManager:(CLLocationManager *)manager 
        didUpdateToLocation:(CLLocation *)newLocation 
               fromLocation:(CLLocation *)oldLocation {
    
        NSLog(@&quot;%@&quot;, newLocation);

        NSLog(@&quot;background time: %f&quot;, [UIApplication sharedApplication].backgroundTimeRemaining);
        [self.locationManager stopUpdatingLocation];
    
    }

The current behavior is that the `backgroundTimeRemaining` decrements from 180 seconds to zero (while logging location), and then the expiration handler executes and no further location updates are generated.  How do I modify the above code in order to receive **periodic location updates in the background indefinitely**?

**Update**: I&#39;m targeting iOS 7 and there appears to be some evidence that background tasks behave differently:

https://stackoverflow.com/questions/18901583/start-location-manager-in-ios-7-from-background-task

Periodic iOS background location updates

I am getting an array with null value. Please check the structure of my array below:

     (
        &quot;&lt; null&gt;&quot;
     )

When I&#39;m trying to access index 0 its crashing because of

    -[NSNull isEqualToString:]: unrecognized selector sent to instance 0x389cea70

Currently its crashing because of that array with a crash log:

     *** Terminating app due to uncaught exception &#39;NSInvalidArgumentException&#39;, reason: &#39;-[NSNull isEqualToString:]: unrecognized selector sent to instance 0x389cea70&#39;
    *** First throw call stack:
    (0x2d9fdf53 0x3820a6af 0x2da018e7 0x2da001d3 0x2d94f598 0x1dee57 0x1dfd31 0x302f598d 0x301a03e3 0x3052aeed 0x3016728b 0x301659d3 0x3019ec41 0x3019e5e7 0x30173a25 0x30172221 0x2d9c918b 0x2d9c865b 0x2d9c6e4f 0x2d931ce7 0x2d931acb 0x3262c283 0x301d3a41 0xabb71 0xabaf8)
    libc++abi.dylib: terminating with uncaught exception of type NSException

How can I check if an object in an NSArray is NSNull?

I&#39;m Trying to Link a static Library to a shared library , I&#39;m Getting the Following error

&lt;pre&gt;
/usr/bin/ld: ../../../libraries/log4cplus/liblog4cplus.a(fileappender.o): relocation R_X86_64_32S against `a local symbol&#39; can not be used when making a shared object; recompile with -fPIC
../../../libraries/log4cplus/liblog4cplus.a: could not read symbols: Bad value
collect2: ld returned 1 exit status
&lt;/pre&gt;

But this worked on a 32bit machine without any such error. I tried adding The `-fPIC` flags manually to the Makefile that too didn&#39;t solve the problem

I tried the `-whole-archive` flag as suggested [here](https://stackoverflow.com/questions/14889941/link-a-static-library-to-a-shared-one-during-build) but with no success.

&lt;pre&gt; 
/usr/bin/ld: ../../../libraries/log4cplus/liblog4cplus.a(appenderattachableimpl.o): relocation R_X86_64_32S against `vtable for log4cplus::spi::AppenderAttachable&#39; can not be used when making a shared object; recompile with -fPIC
../../../libraries/log4cplus/liblog4cplus.a(appenderattachableimpl.o): could not read symbols: Bad value
collect2: ld returned 1 exit status
&lt;/pre&gt;

### Creation of liblog4cplus.a: ###
 1. `unzip log4cplus-1.1.0.zip`
 2. `./configure --enable-static=yes --enable-threads=yes`
 3. `vi Makefile` and added -fPIC to CXXFLAGS and CFLAGS
 4. `make`

### Then for Compiling my shared library: ###

 1. `g++ -frtti -w  -c -fPIC -I&quot;Include_Directory&quot; myfile.cpp`
 2. `g++ -shared -fPIC -frtti -I&quot;Include_Directory&quot; -o mysofile.so myfile.o -Wl,--whole-archive &quot;../../../libraries/log4cplus/liblog4cplus.a&quot; -Wl,--no-whole-archive -ldl`


&quot;relocation R_X86_64_32S against &quot; linking Error

I have to admit that with the release of iOS 8 I am a bit confused about dynamic and static frameworks in iOS.

I am looking for a way to distribute a library that I created, and I need to support iOS 7 and above. (Note: This will be a proprietary framework. I cannot use cocoa pods, and I also cannot distribute the source). Here is what I already know:

- iOS 8 introduced &quot;embedded frameworks&quot; for iOS, but, as I understand, they do not work for iOS 7, only for iOS 8 and above.
- I have the option of distributing my library as a static library (.a file) and also distribute the headers. I know that this is a common way of dealing with the situation, but I would like to find something simpler than that (and also to bundle some resources with it, if possible).
- I have also found that iOS 7 does not support dynamic .framework libraries (only static) because it doesn&#39;t support dynamic linking. But iOS 8 does, as well as static linking.

And here are my questions regarding this information:

- I saw that I can create a .framework target, and make it static, by changing the Mach-O type to &quot;static library. Would that be enough in order to support iOS 7 without any problems, and also to distribute my library as a .framework bundle? If so, why is &quot;embedded frameworks&quot; in iOS 8 that big of a deal, as many resources on the internet are suggesting? Am I missing something?
- Is it necessary to codesign the .framework just as I do with any other application I make?
- What if I need to include other resources (like Core Data or Images) with my .framework file? Will I need to make a separate .bundle file for that?

iOS Static vs Dynamic frameworks clarifications

I know `.o` are object files, `.a` are static libraries and `.so` are dynamic libraries? What is their physical significance? When can I use some and when not?

What is the difference between .o, .a, and .so files?

I have used `use_frameworks!` in CocoaPods `Podfile` many times. I just wonder why do we use it? I couldn&#39;t get the straight forward answer of it.

Example:

    platform :ios, &#39;8.0&#39;
    use_frameworks!
    
    target &quot;CityWhether&quot; do
        pod &#39;Alamofire&#39;
        pod &#39;SwiftyJSON&#39;
    end

Why do we use use_frameworks! in CocoaPods?

I have a problem with linking my mixed language framework to a project.&lt;p&gt;
1. I create a framework with Swift and Objective-C classes.
1. The main logic was stored in the Swift file. For example the class with a method that calls NSLog(&quot;Swift log was called&quot;).
1. Objective-C file has a class that has a method in which I create an instance of Swift class and call Swift-log method.
1. I link this framework with my Objective-C project, I can call all that I need in this project, but when I want to build this project I receive error `linker command failed with exit code 1 (use -v to see invocation)`
  
    And warnings:
```
ld: warning: Could not find auto-linked library &#39;swiftFoundation&#39;
ld: warning: Could not find auto-linked library &#39;swiftDarwin&#39;
ld: warning: Could not find auto-linked library &#39;swiftCoreFoundation&#39;
ld: warning: Could not find auto-linked library &#39;swiftCore&#39;
ld: warning: Could not find auto-linked library &#39;swiftCoreGraphics&#39;
ld: warning: Could not find auto-linked library &#39;swiftObjectiveC&#39;
ld: warning: Could not find auto-linked library &#39;swiftDispatch&#39;
ld: warning: Could not find auto-linked library &#39;swiftSwiftOnoneSupport&#39;
```

I also saw the solution with importing empty Swift-file, but it necessary to make a project without any trash.

Why do I get iOS linker errors with my static libraries?

I have an app using a linked and embedded custom framework. The app built properly for iOS devices and simulators until Xcode 12.2. Starting from Xcode 12.3 however, I&#39;m getting the following error:

`Building for iOS Simulator, but the linked and embedded framework &#39;My.framework&#39; was built for iOS + iOS Simulator.`

The framework is built for both devices and simulators (as the error actually says) and merged using `lipo`, so it should be able to run everywhere without issues.

Am I missing something here? Is there any relevant change on Xcode 12.3?

Content Type	Original Author	Original Content on Stackoverflow
Question	Joel Fischer	View Question on Stackoverflow
Solution 1 - Ios	Stephen Canon	View Answer on Stackoverflow
Solution 2 - Ios	Nikolai Ruhe	View Answer on Stackoverflow
Solution 3 - Ios	Matthieu Riegler	View Answer on Stackoverflow

How to check if a static library is built for 64-bit?

Ios Problem Overview

Ios Solutions

Solution 1 - Ios

Solution 2 - Ios

Solution 3 - Ios

adb connection over tcp not working now

How can I programmatically include layout in Android?

Attributions