-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move FIRSecureStorage to GoogleUtilities #5329
Conversation
@@ -22,6 +22,8 @@ | |||
#import "FBLPromises.h" | |||
#endif | |||
|
|||
#import <GoogleUtilities/GULKeychainStorage.h> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: alphabetically below FirebaseCore
@@ -34,6 +34,8 @@ other Google CocoaPods. They're not intended for direct public usage. | |||
es.source_files = 'GoogleUtilities/Environment/**/*.[mh]' | |||
es.public_header_files = 'GoogleUtilities/Environment/**/*.h' | |||
es.private_header_files = 'GoogleUtilities/Environment/**/*.h' | |||
|
|||
es.dependency 'PromisesObjC', '~> 1.2' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Separate from this review - but are we comfortable allowing minor version updates of Promises. It might be safer to lock to patch version updates ...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice Messaging can start using this to remove IID dependency!
|
||
- (instancetype)init { | ||
NSCache *cache = [[NSCache alloc] init]; | ||
// Cache up to 5 installations. | ||
cache.countLimit = 5; | ||
return [self initWithService:@"com.firebase.FIRInstallations.installations" cache:cache]; | ||
return [self initWithService:@"com.gul.KeychainStorage" cache:cache]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems like the location has changed, how do we ensure the old keychain data is not wiped when update to this version?
And do we care about backward compatibility?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch! Let me make sure the service name is always set by client, so Installations will keep using the same service as before.
* FIRSecureStorage -> GULKeychainStorage: renamed and moved to GoogleUtilities * FIS updated to GULKeychainStorage * Run ./scripts/style.sh * Headers order * GULKeychainUtils API docs * GULKeychainStorage: require Keychain service name
FIRSecureStorage
moved to GoogleUtilities and renamed toGULKeychainStorage
GULKeychainStorage