keejef
/
session-ios
mirror of https://github.com/oxen-io/session-ios
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
master
dev
voice-calls-2
voice-calls
authentication
2.5.0
2.4.5
2.4.4
2.4.3
2.4.2
2.4.1
2.4.0
2.3.2
2.3.1
2.3.0
2.2.14
2.2.13
2.2.12
2.2.11
2.2.10
2.2.9
2.2.6
2.2.4
2.2.2
2.2.1
2.2.0
2.1.1
2.0.3
2.0.2
2.0.1
2.0.0
1.0.0-alpha.1
audit-2
audit
2.8.0
2.7.4
2.7.3
2.7.2
2.7.1
2.7.0
2.6.3
2.6.2
2.6.1
2.6.0
2.2.8
2.2.7
2.2.5
2.2.3
2.1.0
1.9.7
1.9.6
1.9.5
1.9.4
1.9.3
1.9.1
1.9.0
1.8.3
1.8.2
1.8.1
1.8.0
1.7.8
1.7.7
1.7.6
1.7.5
1.7.4
1.7.3
1.7.2
1.7.0
1.6.5
1.6.4
1.6.3
1.6.2
1.6.1
1.6.0
1.5.3
1.5.2
1.5.1-beta
1.5.0-beta
1.5.0
1.4.7
1.4.6
1.4.5
1.4.4
1.4.3
1.4.2
1.4.0-beta
1.4.0
1.3.0-alpha.1
1.3.0
1.2.6
1.2.5
1.2.4
1.2.3
1.2.1
1.2.0-alpha.2
1.2.0-alpha.1
1.2.0
1.13.0
1.12.9
1.12.8
1.12.7
1.12.6
1.12.5
1.12.4
1.12.2
1.12.1
1.11.9
1.11.8
1.11.7
1.11.6
1.11.5
1.11.4
1.11.3
1.11.24
1.11.23
1.11.22
1.11.21
1.11.20
1.11.2
1.11.19
1.11.18
1.11.17
1.11.16
1.11.15
1.11.14
1.11.13
1.11.12
1.11.11
1.11.10
1.11.1
1.11.0
1.10.2
1.10.1
1.10.0
1.1.0-alpha.4
1.1.0-alpha.3
1.1.0-alpha.2
1.1.0-alpha.1
1.1.0
1.0.8
1.0.7
1.0.6
1.0.5
1.0.4
1.0.3
1.0.2
1.0.1
1.0.0-alpha.3
1.0.0-alpha.2
1.0.0
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'e1f131f09c'
${ noResults }
session-ios/SignalMessaging/utils/OWSPreferences.h

99 lines
2.5 KiB
C
Raw Normal View History Unescape Escape

Add WebRTC setting. // FREEBIE
9 years ago
//
Aggressively nag iOS 8 users to upgrade iOS.
8 years ago
// Copyright (c) 2018 Open Whisper Systems. All rights reserved.
Add WebRTC setting. // FREEBIE
9 years ago
//
Fix registration flow / Keep push tokens in sync * Separate registering an account from registering for push notifications * Allows us to complete registration without prompting user for notification settings. UX Changes ---------- * Automatically keep push tokens in sync on startup. Push tokens *can* change, though they rarely do. It happens more often for people switching between appstore/beta builds. fixes #1174 * Show alert with registration failure * add secret 8-tap debug log gesture to registration flow * Move registration to separate flow * don't see flash of inbox when first launching * show useful error messages when given wrong code / no code * remove background fetch We werent using it, but only relying on a side effect of it which is no longer necessary. Code Changes ------------ * More registration logging. * Install PromiseKit with carthage Our dependencies are not yet framework compatible, so we can't use cocoapods. * Merge preferences util "category" into superclass. The immediate reason for this is Swift interop was assuming optional types were not optional, and exploding when a value was nil. This is clearer anyway, since we were treating it like a subclass, and it was the only thing using the class anyway. * auto-genstrings now searches *.swift (and *.h, which was previously broken) for translateable strings. // FREEBIE
9 years ago
NS_ASSUME_NONNULL_BEGIN
WIP: WebRTC calling * Ensure NotificationsManager has dependencies Otherwise it's easy to mess up the order of the required dependencies. * move AccountManager into Environment, it's heavy to construct // FREEBIE
9 years ago
/**
* The users privacy preference for what kind of content to show in lock screen notifications.
*/
Fix registration flow / Keep push tokens in sync * Separate registering an account from registering for push notifications * Allows us to complete registration without prompting user for notification settings. UX Changes ---------- * Automatically keep push tokens in sync on startup. Push tokens *can* change, though they rarely do. It happens more often for people switching between appstore/beta builds. fixes #1174 * Show alert with registration failure * add secret 8-tap debug log gesture to registration flow * Move registration to separate flow * don't see flash of inbox when first launching * show useful error messages when given wrong code / no code * remove background fetch We werent using it, but only relying on a side effect of it which is no longer necessary. Code Changes ------------ * More registration logging. * Install PromiseKit with carthage Our dependencies are not yet framework compatible, so we can't use cocoapods. * Merge preferences util "category" into superclass. The immediate reason for this is Swift interop was assuming optional types were not optional, and exploding when a value was nil. This is clearer anyway, since we were treating it like a subclass, and it was the only thing using the class anyway. * auto-genstrings now searches *.swift (and *.h, which was previously broken) for translateable strings. // FREEBIE
9 years ago
typedef NS_ENUM(NSUInteger, NotificationType) {
NotificationNoNameNoPreview,
NotificationNameNoPreview,
NotificationNamePreview,
};
Migrate legacy db stored logging preferences to NSUserDefaults This is part of making sure we can log *before* the DB is initialized. // FREEBIE
9 years ago
// Used when migrating logging to NSUserDefaults.
Rename app preferences class. // FREEBIE
8 years ago
extern NSString *const OWSPreferencesSignalDatabaseCollection;
extern NSString *const OWSPreferencesKeyEnableDebugLog;
A lighter touch for the fix-call connect. Though it should be fine, reloading the callUIAdapter is a bit heavy handed. And the current implementation is prone to being broken, since we sometimes forget not to treat callUIAdapter as a singleton. Longer term we can find a way to either: make callUIAdapter a true singleton or possibly make callUIAdapter a private member of something which *is* a true singleton. Since we only *need* it to be reloaded the one time the migration runs (or when a user changes settings which should be rare) it makes sense to remove it from the happy path. // FREEBIE
8 years ago
extern NSString *const OWSPreferencesCallLoggingDidChangeNotification;
Migrate legacy db stored logging preferences to NSUserDefaults This is part of making sure we can log *before* the DB is initialized. // FREEBIE
9 years ago
Fix build break // FREEBIE
8 years ago
@class YapDatabaseReadWriteTransaction;
Rename app preferences class. // FREEBIE
8 years ago
@interface OWSPreferences : NSObject
initial commit
12 years ago
Fix registration flow / Keep push tokens in sync * Separate registering an account from registering for push notifications * Allows us to complete registration without prompting user for notification settings. UX Changes ---------- * Automatically keep push tokens in sync on startup. Push tokens *can* change, though they rarely do. It happens more often for people switching between appstore/beta builds. fixes #1174 * Show alert with registration failure * add secret 8-tap debug log gesture to registration flow * Move registration to separate flow * don't see flash of inbox when first launching * show useful error messages when given wrong code / no code * remove background fetch We werent using it, but only relying on a side effect of it which is no longer necessary. Code Changes ------------ * More registration logging. * Install PromiseKit with carthage Our dependencies are not yet framework compatible, so we can't use cocoapods. * Merge preferences util "category" into superclass. The immediate reason for this is Swift interop was assuming optional types were not optional, and exploding when a value was nil. This is clearer anyway, since we were treating it like a subclass, and it was the only thing using the class anyway. * auto-genstrings now searches *.swift (and *.h, which was previously broken) for translateable strings. // FREEBIE
9 years ago
#pragma mark - Helpers
- (nullable id)tryGetValueForKey:(NSString *)key;
- (void)setValueForKey:(NSString *)key toValue:(nullable id)value;
TextSecureKit Refactoring - Using same clang format file for old and new files. - Moving out all TextSecure code to allow other clients (OS X, iOS) to integrate easily TextSecure functionality. - Use TextSecure API to signup.
10 years ago
- (void)clear;
initial commit
12 years ago
Fix registration flow / Keep push tokens in sync * Separate registering an account from registering for push notifications * Allows us to complete registration without prompting user for notification settings. UX Changes ---------- * Automatically keep push tokens in sync on startup. Push tokens *can* change, though they rarely do. It happens more often for people switching between appstore/beta builds. fixes #1174 * Show alert with registration failure * add secret 8-tap debug log gesture to registration flow * Move registration to separate flow * don't see flash of inbox when first launching * show useful error messages when given wrong code / no code * remove background fetch We werent using it, but only relying on a side effect of it which is no longer necessary. Code Changes ------------ * More registration logging. * Install PromiseKit with carthage Our dependencies are not yet framework compatible, so we can't use cocoapods. * Merge preferences util "category" into superclass. The immediate reason for this is Swift interop was assuming optional types were not optional, and exploding when a value was nil. This is clearer anyway, since we were treating it like a subclass, and it was the only thing using the class anyway. * auto-genstrings now searches *.swift (and *.h, which was previously broken) for translateable strings. // FREEBIE
9 years ago
#pragma mark - Specific Preferences
Clean up ahead of PR.
8 years ago
+ (BOOL)isReadyForAppExtensions;
Continue TSStorageManager refactor.
8 years ago
+ (void)setIsReadyForAppExtensions;
Migrate to shared data NSUserDefaults.
8 years ago
CR: clean up preferences
7 years ago
- (BOOL)hasSentAMessage;
Fix registration flow / Keep push tokens in sync * Separate registering an account from registering for push notifications * Allows us to complete registration without prompting user for notification settings. UX Changes ---------- * Automatically keep push tokens in sync on startup. Push tokens *can* change, though they rarely do. It happens more often for people switching between appstore/beta builds. fixes #1174 * Show alert with registration failure * add secret 8-tap debug log gesture to registration flow * Move registration to separate flow * don't see flash of inbox when first launching * show useful error messages when given wrong code / no code * remove background fetch We werent using it, but only relying on a side effect of it which is no longer necessary. Code Changes ------------ * More registration logging. * Install PromiseKit with carthage Our dependencies are not yet framework compatible, so we can't use cocoapods. * Merge preferences util "category" into superclass. The immediate reason for this is Swift interop was assuming optional types were not optional, and exploding when a value was nil. This is clearer anyway, since we were treating it like a subclass, and it was the only thing using the class anyway. * auto-genstrings now searches *.swift (and *.h, which was previously broken) for translateable strings. // FREEBIE
9 years ago
- (void)setHasSentAMessage:(BOOL)enabled;
Enable logging in SAE; rework log file management to include multiple log directories.
8 years ago
+ (BOOL)isLoggingEnabled;
+ (void)setIsLoggingEnabled:(BOOL)flag;
Fix registration flow / Keep push tokens in sync * Separate registering an account from registering for push notifications * Allows us to complete registration without prompting user for notification settings. UX Changes ---------- * Automatically keep push tokens in sync on startup. Push tokens *can* change, though they rarely do. It happens more often for people switching between appstore/beta builds. fixes #1174 * Show alert with registration failure * add secret 8-tap debug log gesture to registration flow * Move registration to separate flow * don't see flash of inbox when first launching * show useful error messages when given wrong code / no code * remove background fetch We werent using it, but only relying on a side effect of it which is no longer necessary. Code Changes ------------ * More registration logging. * Install PromiseKit with carthage Our dependencies are not yet framework compatible, so we can't use cocoapods. * Merge preferences util "category" into superclass. The immediate reason for this is Swift interop was assuming optional types were not optional, and exploding when a value was nil. This is clearer anyway, since we were treating it like a subclass, and it was the only thing using the class anyway. * auto-genstrings now searches *.swift (and *.h, which was previously broken) for translateable strings. // FREEBIE
9 years ago
- (BOOL)screenSecurityIsEnabled;
- (void)setScreenSecurity:(BOOL)flag;
- (NotificationType)notificationPreviewType;
- (void)setNotificationPreviewType:(NotificationType)type;
- (NSString *)nameForNotificationPreviewType:(NotificationType)notificationType;
- (BOOL)soundInForeground;
- (void)setSoundInForeground:(BOOL)enabled;
Don't show the "no contacts" mode of new conversation view again after it has been dismissed. // FREEBIE
9 years ago
- (BOOL)hasDeclinedNoContactsView;
- (void)setHasDeclinedNoContactsView:(BOOL)value;
Aggressively nag iOS 8 users to upgrade iOS.
8 years ago
- (void)setIOSUpgradeNagDate:(NSDate *)value;
- (nullable NSDate *)iOSUpgradeNagDate;
Nag users on iOS 8 to upgrade. // FREEBIE
9 years ago
One time thumbnail generation // FREEBIE
8 years ago
- (BOOL)hasGeneratedThumbnails;
- (void)setHasGeneratedThumbnails:(BOOL)value;
users can opt out of CallKit // FREEBIE
9 years ago
#pragma mark Callkit
Simplify call privacy settings We've long allowed users to configure what shows up in message notifications: - name: content (by default) - just name (no content) - generic notification (no name nor content) Now we're dual purposing that setting to apply to calls. If someone doesn't want to show names in the message notifications, presumably also don't want that name showing up in the call log. Also, since the earlier CallKit/iCloud issues had been addressed before iOS11, we upgrade all iOS11 users to the more intuitive CallKit interface. Also: introduce "use system call logs" toggle when available. It will be enabled by default, but we disable it for legacy users who'd explicitly opted *out* of CallKit. // FREEBIE
8 years ago
- (BOOL)isSystemCallLogEnabled;
- (void)setIsSystemCallLogEnabled:(BOOL)flag;
#pragma mark - Legacy CallKit settings
Be more conservative about logging legacy users into "Recents" // FREEBIE
8 years ago
- (void)applyCallLoggingSettingsForLegacyUsersWithTransaction:(YapDatabaseReadWriteTransaction *)transaction;
Respond to CR. // FREEBIE
9 years ago
- (BOOL)isCallKitEnabled;
- (void)setIsCallKitEnabled:(BOOL)flag;
Simplify call privacy settings We've long allowed users to configure what shows up in message notifications: - name: content (by default) - just name (no content) - generic notification (no name nor content) Now we're dual purposing that setting to apply to calls. If someone doesn't want to show names in the message notifications, presumably also don't want that name showing up in the call log. Also, since the earlier CallKit/iCloud issues had been addressed before iOS11, we upgrade all iOS11 users to the more intuitive CallKit interface. Also: introduce "use system call logs" toggle when available. It will be enabled by default, but we disable it for legacy users who'd explicitly opted *out* of CallKit. // FREEBIE
8 years ago
Add “nag” to call settings view that prods the user to change their privacy settings after calls. // FREEBIE
9 years ago
// Returns YES IFF isCallKitEnabled has been set by user.
- (BOOL)isCallKitEnabledSet;
Add and honor the “CallKit Privacy” setting. // FREEBIE
9 years ago
- (BOOL)isCallKitPrivacyEnabled;
- (void)setIsCallKitPrivacyEnabled:(BOOL)flag;
Add “nag” to call settings view that prods the user to change their privacy settings after calls. // FREEBIE
9 years ago
// Returns YES IFF isCallKitPrivacyEnabled has been set by user.
- (BOOL)isCallKitPrivacySet;
users can opt out of CallKit // FREEBIE
9 years ago
TURN-only option, and for unknown caller Now, by default, we only use TURN for incoming calls from unknown contacts. We will potentially directly connect for outgoing calls and for incoming calls from known contacts. Optionally, the user can disable direct connection altogether, at the cost of some call quality. // FREEBIE
9 years ago
#pragma mark direct call connectivity (non-TURN)
- (BOOL)doCallsHideIPAddress;
- (void)setDoCallsHideIPAddress:(BOOL)flag;
Fix registration flow / Keep push tokens in sync * Separate registering an account from registering for push notifications * Allows us to complete registration without prompting user for notification settings. UX Changes ---------- * Automatically keep push tokens in sync on startup. Push tokens *can* change, though they rarely do. It happens more often for people switching between appstore/beta builds. fixes #1174 * Show alert with registration failure * add secret 8-tap debug log gesture to registration flow * Move registration to separate flow * don't see flash of inbox when first launching * show useful error messages when given wrong code / no code * remove background fetch We werent using it, but only relying on a side effect of it which is no longer necessary. Code Changes ------------ * More registration logging. * Install PromiseKit with carthage Our dependencies are not yet framework compatible, so we can't use cocoapods. * Merge preferences util "category" into superclass. The immediate reason for this is Swift interop was assuming optional types were not optional, and exploding when a value was nil. This is clearer anyway, since we were treating it like a subclass, and it was the only thing using the class anyway. * auto-genstrings now searches *.swift (and *.h, which was previously broken) for translateable strings. // FREEBIE
9 years ago
#pragma mark - Push Tokens
- (void)setPushToken:(NSString *)value;
- (nullable NSString *)getPushToken;
- (void)setVoipToken:(NSString *)value;
- (nullable NSString *)getVoipToken;
Ensure we re-upload push tokens after re-registering. // FREEBIE
8 years ago
- (void)unsetRecordedAPNSTokens;
initial commit
12 years ago
@end
Fix registration flow / Keep push tokens in sync * Separate registering an account from registering for push notifications * Allows us to complete registration without prompting user for notification settings. UX Changes ---------- * Automatically keep push tokens in sync on startup. Push tokens *can* change, though they rarely do. It happens more often for people switching between appstore/beta builds. fixes #1174 * Show alert with registration failure * add secret 8-tap debug log gesture to registration flow * Move registration to separate flow * don't see flash of inbox when first launching * show useful error messages when given wrong code / no code * remove background fetch We werent using it, but only relying on a side effect of it which is no longer necessary. Code Changes ------------ * More registration logging. * Install PromiseKit with carthage Our dependencies are not yet framework compatible, so we can't use cocoapods. * Merge preferences util "category" into superclass. The immediate reason for this is Swift interop was assuming optional types were not optional, and exploding when a value was nil. This is clearer anyway, since we were treating it like a subclass, and it was the only thing using the class anyway. * auto-genstrings now searches *.swift (and *.h, which was previously broken) for translateable strings. // FREEBIE
9 years ago
NS_ASSUME_NONNULL_END