Closed Bug 1127505 Opened 7 years ago Closed 7 years ago

Linking against dylib not safe for use in application extensions: Storage.framework

Categories

(Firefox for iOS :: Build & Test, defect)

All
iOS 8
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: st3fan, Assigned: rnewman)

Details

Attachments

(1 file)

47 bytes, text/x-github-pull-request
st3fan
: review+
Details | Review
Description: Linking against dylib not safe for use in application extensions: /Library/Developer/XcodeServer/Integrations/Caches/fe797f1fea55af5d92a791fbbd6ba1ca/DerivedData/Build/Products/Debug-iphonesimulator/Storage.framework/Storage.

What does this mean? Is the Storage project generating the wrong kind of artifact?
Here is a hint: "To configure an app extension target to use an embedded framework, set the target’s “Require Only App-Extension-Safe API” build setting to Yes. If you don’t, Xcode reminds you to do so by displaying the warning “linking against dylib not safe for use in application extensions”.

https://developer.apple.com/library/prerelease/ios/documentation/General/Conceptual/ExtensibilityPG/ExtensionScenarios.html
So... that's puzzling, because that setting *is* set to Yes for those targets.
Status: NEW → ASSIGNED
OS: Mac OS X → iOS 8
Hardware: x86 → All
Attached file Add flag. v1
Attachment #8556757 - Flags: review?(sarentz)
I think that setting needs to be in the project that generates the framework?
So in Storage/Storage.xcodeproj/project.pbxproj ?
Attachment #8556757 - Flags: review?(sarentz) → review+
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.