You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm still having problems with using use_frameworks! in conjunction with OnePasswordExtension 1.6.3 installed via CocoaPods 0.39.0.
I can reliably reproduce this by:
Create new Swift project
Add Objective-C file, and create bridging header
Add podfile with simply use_frameworks! and pod '1PasswordExtension', '~> 1.6.3'
pod install
Open workspace
Any reference to OnePasswordExtension from Swift results with a "Use of unresolved identifier OnePasswordExtension" error
If I simply go to the pod file and remove use_frameworks! and pod install again, change the bridging header import to #import "OnePasswordExtension.h" the project will build fine.
I saw that #268 which was included with 1.6.3 was related to this.
The text was updated successfully, but these errors were encountered:
@obuseme, I am really glad that you guys sorted it all out.
In our README we recommend installing the latest version of 1Password and of Xcode. May be CocoaPods ought to specify that version 0.39.0 requires Xcode 7.1 or later...
Anyway, since this is not an App Extension API-specific issue, I am closing this issue as invalid.
I'm still having problems with using
use_frameworks!
in conjunction with OnePasswordExtension 1.6.3 installed via CocoaPods 0.39.0.I can reliably reproduce this by:
Create new Swift project
Add Objective-C file, and create bridging header
Add podfile with simply
use_frameworks!
andpod '1PasswordExtension', '~> 1.6.3'
pod install
Open workspace
Any reference to
OnePasswordExtension
from Swift results with a "Use of unresolved identifier OnePasswordExtension" errorIf I simply go to the pod file and remove
use_frameworks!
andpod install
again, change the bridging header import to#import "OnePasswordExtension.h"
the project will build fine.I saw that #268 which was included with 1.6.3 was related to this.
The text was updated successfully, but these errors were encountered: