I am trying to archieve my app for submission however I am running into issues with code signing.

Basically I have a Today Widget extension for my app. I am unsure about what I should be setting the provisioning profile as. I assumed that I would just use the same profile that I have used for my app, however I get this error:

**The provisioning profile specified in your build settings (“AppName”) has an AppID of “BundleID” which does not match your bundle identifier “BundleID2”.  Xcode can resolve this issue by downloading a new provisioning profile from the Member Center.**

I can of course click &#39;Fix Issue&#39;, but does this actually solve the problem? It just changes my distribution settings to &#39;iOS Developer&#39; and providing profile to &#39;Automatic&#39;.



Provisioning profile for Today Widget extension

After I add Today App Extension Target,I become impossible to compile project.
below is error:

&gt;     error: Embedded binary is not signed with the same certificate as the parent app. Verify the embedded binary target&#39;s code sign settings match the parent app&#39;s.
Embedded Binary Signing Certificate:	iPhone Developer: (Developer name) (number)

&gt; Parent App Signing Certificate:		iPhone Developer: (Developer name) (number)



but Embedded binary certificate and parent app&#39;s cerificate are the same.
So I&#39;m confusing now...

Xcode6:Embedded binary is not signed with the same certificate as the parent app

I add following code:
 
    - (IBAction)done {
        // Return any edited content to the host app.
        // This template doesn&#39;t do anything, so we just echo the passed in items.
    
        NSURL *url = [NSURL URLWithString:@&quot;lister://today&quot;];
        [self.extensionContext openURL:url completionHandler:^(BOOL success) {
            NSLog(@&quot;fun=%s after completion. success=%d&quot;, __func__, success);
        }];
        [self.extensionContext completeRequestReturningItems:self.extensionContext.inputItems completionHandler:nil];
    
    }

after I create the Action Extension target. But it can not work.
 
My purpose is that: when user view a photo in Photos.app (the iOS&#39;s default Photos.app or called gallery), and he click the share button to launch our extension view.
We can transfer the image from Photos.app to my own app and deal or upload the image in my app.
 
I also try &quot;CFBundleDocumentTypes&quot; but it also can not work.

Any help will be appreciated.

openURL not work in Action Extension

In iOS 8, when we create an app extension, we have to decide which target it is attached to. The extension will have the same bundle ID&#39;s prefix as the target.

 1. Is there any way to change the target afterward?
 2. If my project contains 2 (or more) targets (for example one for debug/simulator, one for production/device), what&#39;s the best way to work with extensions? Do I need to create another extension and duplicate the code (very bothersome to keep the same code for both targets)?

iOS extensions with multiple targets

My Today extension needs to have a dynamic height based on the contents the widget is displaying. I was able to achieve this by adding a constraint on my bottom-most element: bottom layout guide&#39;s top is less than or equal to the bottom most element&#39;s bottom, with a constant of 0, priority 999, multiplier 1.

This works exactly as expected on iPhones - the widget height fits all content plus the default bottom margin is applied before the next widget is shown.

But on iPad it seems to be setting my widget&#39;s height equal to the max height Notification Center will allow a widget to be - there&#39;s a lot of space underneath my widget, it&#39;s nearly full screen.

***How can I remove that extra space?***

I know exactly what the problem is but am not sure how to solve it - see the &quot;The Problem&quot; section. First let me explain the setup:

**The Setup:**  
I set this extension&#39;s view up in a storyboard, nothing is done programmatically. The view consists of 5 elements stacked vertically, and some others horizontally. These are the auto layout constraints for that vertical line from top to bottom - where not stated priority is 1000, multiplier 1:

    UILabel: height = 35, top space to top layout guide with constant of 10
    UIButton: equal height and width to a different button (whose aspect ratio is 1:1, there is no fixed width/height), top space to label 10
    UIButton: equal height and width to same button, top space to above button 8
    UIButton: equal height and width to same button, top space to above button 8
    UIButton: equal height and width to same button, top space to above button 8, bottom space to bottom layout guide &lt;= 0 with priority 999

**The Necessary Behavior:**  

 - I need a grid of 4x4 buttons located underneath a single full-width label
 - Each button should be the exact same width and height - all perfect squares
 - No extra space underneath the last row of buttons

**The Result:**  
![enter image description here][1]

**The Expected Result:**  
![enter image description here][2]

**The Problem:**  
The aspect ratio constraints on all of the buttons end up indirectly imposing an &#39;implicit&#39; aspect ratio constraint on the height of the widget view when it is sent `systemLayoutSizeFittingSize:withHorizontalFittingPriority:verticalFittingPriority:`, where it’s passed the necessary width (724) for layout at the required priority and a height of 0 (to compress the view) at the fitting level priority. This results in a tall widget view on iPad where the view is wider to begin with. But there is no actual aspect-ratio constraint that can be removed. Essentially, because I&#39;ve applied aspect-ratio constraints to all the button, the height of the today extension is dependent on its width (considering all the constraints together, aspect-ratio and otherwise). Thus the height of the extension is ungainly in a wide area, manifesting itself on a wide device like the iPad. The constraints on the buttons need to be reconsidered, or somehow adjusted.

**The Sample Project:**  
A [sample project that demonstrates the issue][3] is available from CloudApp so you can download and play with it.

**What I&#39;ve Tried:**  
I tried removing the default margin insets by overriding `widgetMarginInsetsForProposedMarginInsets` and returning `0` for the bottom. This did remove the default padding, therefore decreased the height a bit, but there&#39;s still a lot of extra space underneath it.

The `UILabel` had a constraint on it: label&#39;s leading equal to superview&#39;s leading - constant 0, priority 1000, multiplier 1. If I simply change that to the superview&#39;s leading **margin**, the extra bottom spacing magically disappears. I wondered if it was because the elements were becoming too large, so increasing the amount of left spacing would decrease their size, but I tried keeping it set to the regular leading and increasing the constant and that didn&#39;t resolve the issue. But this only resolves the issue for iPad in portrait. And it doesn&#39;t even fully resolve it, every time you pull down Notification Center it starts at the large height then shrinks down to the proper size. In landscape it never does shrink to the proper size.

**Attempted Solutions:**

 - @Lefteris proposed hardcoding the size, which won&#39;t work in this case
   as the height is dynamic and the widget is available for many screen
   sizes/orientations.
 - @Yuyutsu attempted to solve it, but it unfortunately doesn&#39;t meet the requirements and exhibits conflicting constraints and a modified layout.


  [1]: https://i.stack.imgur.com/De0Pd.png
  [2]: https://i.stack.imgur.com/KooVk.png
  [3]: https://dzwonsemrish7.cloudfront.net/items/1X2O3b053x0a2D2L1c2S/TestWidgetHeight.zip

Today Extension height for iPad much larger than specified

We have 3 new options in &quot;Frameworks, Libraries, and Embedded Content&quot; section of Xcode11 Beta for adding libraries.

**Xcode Libraries section screenshot**

[![enter image description here][1]][1]


Can anyone explain what they do?


  [1]: https://i.stack.imgur.com/pMHUm.png

&quot;Do Not Embed&quot;, &quot;Embed &amp; Sign&quot;, &quot;Embed Without Signing&quot;. What are they?. What they do?

    - (void)viewDidLoad
    {
        NSLog(@&quot;%s&quot;, __func__);
        // ...
    }

in `viewDidLoad` of an iOS 8 _extension_. the  `NSLog` outputs nothing in Xcode. `NSLog` works as usual in the container app though.

How can I get output from debug messages from an extension?


How to debug iOS 8 extensions with NSLog?

iOS 8 revealed a new API yesterday concerning App Groups. It was kind of messy before to share data and communicate between apps and I believe that&#39;s precisely what App Groups is intended to correct.

In my app I have enabled App Groups and added a new group but I just can&#39;t find any documentation on how to use it. Documentation and API references only state how to add a group.

So what is App Groups really intended to do? Is there any documentation somewhere on how to use it?



Communicating and persisting data between apps with App Groups

I&#39;m trying to build a photo App Extension in Xcode 6 Beta-6 that uses cocoapods libraries.
The bridging header that Xcode creates for the photo extension can&#39;t see anything from cocoapods.

For example: `#import &lt;GPUImage/GPUImage.h&gt;` results in the error `&quot;GPUImage/GPUImage.h&quot; file not found`.

I&#39;ve tried every conceivable path for the import (with brackets and quotes) and have had almost no success.  The exception is that for simple pods like `SVProgressHUD`, the following ugly terrible hack works:
`#import &quot;../Pods/SVProgressHUD/SVProgressHUD/SVProgressHUD.h&quot;`.

But for GPUImage, it walks into the `GPUImage.h` header and decides it suddenly can&#39;t see `GPUImageContext.h` despite having no issue when this is imported with the bridging header for the normal swift code that is not part of the app extension.

What is different about the compilation of app extensions that is preventing the bridging header from behaving sanely?

Note:
I&#39;ve read every possible permutation of [this tutorial][1] and it is not immediately applicable, just in case anyone thinks they have found the answer there.

Also, the problem described in [this SO question][2] may be related, but I asked this question anyway in case my issue is specific to app extensions.  


  [1]: https://medium.com/@stigi/swift-cocoapods-da09d8ba6dd2
  [2]: https://stackoverflow.com/q/25495225/579405

Use Cocoapods with an App Extension

I&#39;m trying to build an extension project and Xcode keeps throwing the error in subject.

![Xcode log error][1]

Needless to day, the extension&#39;s bundle id *is* prefixed with app&#39;s bundle id.

Product Name: `ro.chitza.TodayPics.$(TARGET_NAME:rfc1034identifier`

![Extension bundle id][2]

I&#39;ve tried cleaning the build folder and rebuilding, no luck. The funny thing is the entire project got built for a few times, but after some code and UI changes it started failing. Even if I create new projects, the same thing happens after about 5-6 builds.

Did anyone else encounter this error? Any hints for a solution or workaround?


  [1]: http://i.stack.imgur.com/3d8Du.png
  [2]: http://i.stack.imgur.com/Q0HR4.png

Xcode 6 error: &quot;Embedded binary&#39;s bundle identifier is not prefixed with the parent app&#39;s bundle identifier.&quot;

I am trying to add a Today Extension in Swift to my Objective-C app. I keep getting this message in my debugger log: `Failed to inherit CoreMedia permissions from 3005: (null)`. The number ex. 3005 is different every time. I am reading from NSUserDefaults from within the widget but I am reading/writing in the app itself. The only code in my TodayViewController is this the following:

    override func viewDidLoad() {
        super.viewDidLoad()
        
        let formatter = NSNumberFormatter()
        formatter.numberStyle = .CurrencyStyle
        totalLabel.text = formatter.stringFromNumber(0)
        coinsLabel.text = formatter.stringFromNumber(0)
        
        formatter.maximumFractionDigits = 0
        billsLabel.text = formatter.stringFromNumber(0)
        
    }
    
    func widgetMarginInsetsForProposedMarginInsets(defaultMarginInsets: UIEdgeInsets) -&gt; UIEdgeInsets {
        return UIEdgeInsetsMake(8.0, 16.0, 8.0, 16.0)
    }
    
    func widgetPerformUpdateWithCompletionHandler(completionHandler: ((NCUpdateResult) -&gt; Void)!) {
        // Perform any setup necessary in order to update the view.

        // If an error is encountered, use NCUpdateResult.Failed
        // If there&#39;s no update required, use NCUpdateResult.NoData
        // If there&#39;s an update, use NCUpdateResult.NewData

        completionHandler(NCUpdateResult.NewData)
    }


Today Extension Failed to inherit CoreMedia permissions from

Creating a Today widget and I am using `UserDefaults(suiteName:)` to persist some data. In the main application I am using `UserDefaults.standard()`. This can&#39;t be read (or can it?) by the extension which is why I use the `suiteName:` constructor. 

Data that user persist to `UserDefaults.standard()` in the main app needs to be available in the extension. 

At this time I am persisting to both so that the values can be shared
 

     UserDefaults.standard().set:...forKey:...
     UserDefaults(suiteName:...)().set:...forKey:...
     ...

Question is should I drop `UserDefaults.standard()` all together and just use `UserDefaults(suiteName:)` in my application, or is this bad practice and if so why?

Edit: I am using an App group container. For clarification I am asking should I just replace `standard()` with `suiteName:`  throughout my project?

Sharing UserDefaults between extensions

Recently, I&#39;ve been making a simple iOS 8 share extension to understand how the system works. As Apple states in its [App Extension Programming Guide][1]: 

&gt; By default, your containing app and its extensions have no direct access to each other’s containers.

Which means the extension and the containing app do not share data. But in the same page Apple brings a solution:

&gt; If you want your containing app and its extensions to be able to share data, use Xcode or the Developer portal to enable app groups for the app and its extensions. Next, register the app group in the portal and specify the app group to use in the containing app.

Then it becomes possible to use NSUserDefaults to share data between the containing app and the extension. This is exactly what I would like to do. But for some reason, it does not work.

In the same page, Apple suggests the standard defaults:

    var defaults = NSUserDefaults.standardUserDefaults()
In a WWDC presentation (217), they suggest a common package:

    var defaults = NSUserDefaults(suiteName: kDefaultsPackage)
Also, I enabled App Groups for both the containing app target and the extension target, with the same App Group name:
![XCode Target capabilities, App Groups][2]

But all this setup is for nothing. I cannot retrieve the data I stored in the containing app, from the extension. It is like two targets are using completely different NSUserDefaults storages.

So, 

 1. Is there a solution for this method?
 2. How can I share simple data between the containing app and the share extension? The data is just user credentials for an API.

  [1]: https://developer.apple.com/library/prerelease/ios/documentation/General/Conceptual/ExtensibilityPG/ExtensionScenarios.html#//apple_ref/doc/uid/TP40014214-CH21-SW1
  [2]: http://i.stack.imgur.com/nJZyy.png

Sharing data between an iOS 8 share extension and main app

I&#39;ve implemented a Today widget for my application +Quotes which displays the day&#39;s quote within the notification center with the help of these [Apple Docs][1]. What I&#39;d like to accomplish is opening the Containing App, in this case +Quotes, when the user taps the +Quotes widget within their Today notification view, not entirely sure what to call this, as Calendar would if you tapped it in the Today view. I&#39;ve tried overlaying a button over the label which would call 
`-(void)openURL:(NSURL *)URL completionHandler:(void (^)(BOOL success))completionHandler`
upon it being tapped, then open the Custom URL Scheme I have declared to open the Containing App. The issue is it doesn&#39;t open the Containing App.

![+Quotes Today App Extension Widget][2]

    -(IBAction)myButton:(id)sender {
        NSURL *customURL = [NSURL URLWithString:@&quot;PositiveQuotes://&quot;];
        [self openURL:customURL completionHandler:nil];
    }

  [1]: https://developer.apple.com/library/prerelease/ios/documentation/General/Conceptual/ExtensibilityPG/index.html#//apple_ref/doc/uid/TP40014214-CH20-SW1 &quot;Apple&#39;s Docs&quot;
  [2]: http://i.stack.imgur.com/NGmcr.png

Today App Extension Widget Tap To Open Containing App

What does the red dot (circle) next to the app name below the app icon mean?

![enter image description here][1]

I added a Today Extension (Widget) to the app. It appears only when I launch the app on the iOS 8, it does not appear on iOS 7 simulator. Even though I removed the extension and cleared the simulator, it still appears before the app name.


  [1]: http://i.stack.imgur.com/i6fKr.png

Red dot (circle) next to the app name below the app icon on the iPhone Home Screen on iOS 8

I have a problem while archiving my app.
 
I created a new target for an iOS 8 extension.
 
When I archive the app, I receive a warning.
 
The warning is 

&gt; &quot;PBXCp Warning&quot;, &quot;warning: skipping copy phase strip, binary is code
&gt; signed:
&gt; /Users/Library/Developer/Xcode/DerivedData/App/Build/Intermediates/ArchiveInter
&gt; mediates/AppName/IntermediateBuildFilesPath/UninstalledProducts/AppExtappex/AppE
&gt; xt&quot;



The app is in Objective-C.

All Ios App-Extension Solutions on Gang of Coders

Total of 16 Ios App-Extension Solutions