Framework Structure Issue

Question

I am creating Distributed App outside the Mac App Store on Mac osX 10.9.5 with XCode 6. I have used Developer ID Application certificate, custom Framework which was Developed by me. I have signed this framework with same Developer ID Application certificate which used for Mac App. I have Export a Developer ID signed Application in my Mac.
Now, The Problem is when I download ".app" from mail in my Mac and double click, It display Alert Message " App can not be open because identity of developer can not be found". I have attached Image of Error.
When I run codesign command on terminal, It shows "WSBluetoothFramework.framework/: bundle format is ambiguous (could be app or framework)".
So I checked and found that after export signed app "Headers" folder is missing. But before archive and export Framework contain Proper structure of Framework.
Before Archive Framework Structure
After Archive Framework Structure
I want that When App double click it should ask for Open Permission instead of the Error Message.
So Can anyone now about this issue?

Answer 1

You have to structure your workspace properly if you want an embedded framework to work. It should look something like this:
Project/
     Application/
          Application/
               Application.xcodeproj
     Application Workspace/
          Application.xcworkspace
     Framework/
          Framework/
               Framework.xcodeproj
Hopefully I have the indentation correct, but this is the general idea. Replace "Project" with your project name, "Application" with your app name, and "Framework" with your framework name. It may be possible to get it to work using some other structure, but I know this works. If you have it setup properly, when you add your embedded framework, Xcode should setup all of the copy files and run script build phases to properly embed and code sign your framework.
In your example, missing the Headers is normal. It the the code signature that you need. It looks like you have code-signed your development version. That won't work. You have to let Xcode do it the way Xcode wants. If you try to fight Xcode, you will always lose.