The issue here is when you set the region, the map zoom level “snaps” out to the nearest zoom threshold. (I suspect these zoom thresholds are the amounts of zoom you get when you double-tap or two-finger-tap) So if the map is showing zoom level 1 for instance, and you set the region to that … Read more
Sqlite3 is more useful for keeping large database and to access to the database elements. You can sort the items of Sqlite3 database, you can search very fast for item in Sqlite3 dtabase. Sqlite3 database has many privileges that NSUserDefaults didn’t have ! NSUserDefaults vs Sqlite3 NSUserDefaults is for user preferences, usually basic objects like … Read more
No, it will not. I use NSUserDefaults in the exact same manner, and it will not stay after the app is deleted. You can verify this via Organizer if you need to. It will however persist through updates. I have been using TestFlightApp for all of my beta testing, and the token (and other saved … Read more
NSUserDefaults always returns immutable objects, even if the original object was mutable. It’s in the documentation for objectForKey: The returned object is immutable, even if the value you originally set was mutable. You will need to create a copy of the returned object before you modify it, using [NSMutableArray arrayWithArray:] Probably also best to use … Read more
I just had the same problem. There seems to be an issue with NSUserDefaults when first running the iOS8 or 9 simulator and then the iOS10 simulator. Rebooting the mac solved the issue for me.
Update for Swift 2, Xcode 7: As @atxe noticed, NSUserDefaults dictionaries are now mapped as [String, AnyObject]. This is a consequence of the Objective-C “lightweight generics” which allow to declare the Objective-C method as – (NSDictionary<NSString *,id> *)dictionaryForKey:(NSString *)defaultName (Default objects must be property lists and in particular the dictionary keys can only be strings.) … Read more
You are mixing up the protocols Codable and NSCoding 1) NSCoding NSKeyed(Un)Archiver belongs to NSCoding. To use it you have to declare Order as class inheriting from NSObject and to adopt the protocol and its required methods class Order: NSObject, NSCoding { var item_id : String // no need to assign default values var quantity … Read more
NSUserDefaults is quite easy to use and stores one value per key only. But apparently, it is not a very secure method, as there is no encryption. But the Keychain is secure, though it is a bit hard to code. You can refer these link to use keychain access. http://log.scifihifi.com/post/55837387/simple-iphone-keychain-code you can also use this … Read more
Note: NSUserDefaults will always return an immutable version of the object you pass in. To store the information: // Get the standardUserDefaults object, store your UITableView data array against a key, synchronize the defaults NSUserDefaults *userDefaults = [NSUserDefaults standardUserDefaults]; [userDefaults setObject:arrayOfImage forKey:@”tableViewDataImage”]; [userDefaults setObject:arrayOfText forKey:@”tableViewDataText”]; [userDefaults synchronize]; To retrieve the information: NSUserDefaults *userDefaults = [NSUserDefaults … Read more
I would highly recommend you use the keychain – it’s exactly what Facebook do for storing their session tokens. NSUserDefaults is not secure or encrypted – it can be easily opened and read, both on device and when synced to a Mac. So whilst user defaults is a good place for things like preferences and … Read more