1. Only certain ones that I know of
2. At application launch
3. No
4. I think Mavericks but not 100% certain
5. For the affected users yes
6. Not sure about this could check
7. Upon my request yes
8. Not sure would have to check
On Sep 11, 2014, at 3:21 PM, Bavarious bavari...@icloud.com
Em 11/09/2014, à(s) 01:07, Rick C. rickcort...@gmail.com escreveu:
This is all very interesting and shows that there are issues out there, but
back to my original issue if I’m writing and reading via NSUserDefaults and
its not returning the expected values what else could be the trouble?
On 10 Sep 2014, at 3:43 pm, Rick C. rickcort...@gmail.com wrote:
Thanks for the help. So I have double-checked and the info in question that
is not sticking is NSString/NSData being written:
[[NSUserDefaults standardUserDefaults] setObject:stringObject
forKey:@“MyStringKey”];
I've run into issues of app preferences/defaults not persisting (across lots of
apps, not necessarily just my own), and in the past few years when it's
happened it's been an early symptom of filesystem corruption. Sometimes there
have been a bunch of leftover temporary lock(?) files in the
in the past few years when it's happened it's been an early symptom of
filesystem corruption. Sometimes there have been a bunch of leftover
temporary lock(?) files in the Preferences directory.
If you're getting reports of this from users of your app, it might be worth
asking them to run
On Wed, Sep 10, 2014, at 11:15 AM, Todd Heberlein wrote:
in the past few years when it's happened it's been an early symptom of
filesystem corruption. Sometimes there have been a bunch of leftover
temporary lock(?) files in the Preferences directory.
If you're getting reports of this
Thanks to everyone for the help. I’m pretty sure about this Graham but I will
take one last look. Problem is I’m never able to reproduce this issue and as I
mentioned this is happening to a very small percentage of users which would
seem to mean it’s not my code (???). It’s just trying to
On Wed, Sep 10, 2014, at 07:32 PM, Rick C. wrote:
And about not relying on the .plist if we don’t rely upon it how do we
write our prefs? I understand I should not manipulate it directly, but I
am calling everything via NSUserDefaults…
Continue using NSUserDefaults for all interaction with
On 11 Sep 2014, at 10:32 am, Rick C. rickcort...@gmail.com wrote:
And about not relying on the .plist if we don’t rely upon it how do we write
our prefs? I understand I should not manipulate it directly, but I am
calling everything via NSUserDefaults…
Then you should be fine. The point
On Sep 10, 2014, at 6:42 PM, Graham Cox graham@bigpond.com wrote:
Then you should be fine. The point is that the .plist does not necessarily
represent the current state of the defaults for your app. Trashing it for
example no longer resets the defaults like it used to, you have to go
On Sep 10, 2014, at 7:41 PM, Kyle Sluder k...@ksluder.com wrote:
On Wed, Sep 10, 2014, at 07:32 PM, Rick C. wrote:
And about not relying on the .plist if we don’t rely upon it how do we
write our prefs? I understand I should not manipulate it directly, but I
am calling everything via
On Sep 10, 2014, at 7:04 PM, Scott Ribe scott_r...@elevated-dev.com wrote:
The real point: plenty of sites on the web state that the .plist no longer
represents the current state, but that the defaults command will read the
current state so you can use it for debugging. They are wrong.
On 11 Sep 2014, at 12:14 pm, Charles Srstka cocoa...@charlessoft.com wrote:
If that's true, then why does the 'defaults' program work for sandboxed apps,
while NSUserDefaults does not?
Where did you get the idea that NSUserDefaults doesn't work for sandboxed apps?
It certainly does.
On Sep 10, 2014, at 9:39 PM, Graham Cox graham@bigpond.com wrote:
On 11 Sep 2014, at 12:14 pm, Charles Srstka cocoa...@charlessoft.com wrote:
If that's true, then why does the 'defaults' program work for sandboxed
apps, while NSUserDefaults does not?
Where did you get the idea that
On Sep 10, 2014, at 8:19 PM, Charles Srstka cocoa...@charlessoft.com wrote:
Where did you get the idea that NSUserDefaults doesn't work for sandboxed
apps? It certainly does.
#import Foundation/Foundation.h
int main(int argc, const char * argv[]) {
@autoreleasepool {
On 11 Sep 2014, at 1:19 pm, Charles Srstka cocoa...@charlessoft.com wrote:
NSDictionary *domain = [def persistentDomainForName:@com.apple.TextEdit];
The documentation states that this is not supported under sandboxing.
When you say does not ... work, you really need to make clear what you
On Sep 10, 2014, at 10:34 PM, Marco S Hyman m...@snafu.org wrote:
On Sep 10, 2014, at 8:19 PM, Charles Srstka cocoa...@charlessoft.com wrote:
Where did you get the idea that NSUserDefaults doesn't work for sandboxed
apps? It certainly does.
#import Foundation/Foundation.h
int
On Sep 10, 2014, at 10:50 PM, Graham Cox graham@bigpond.com wrote:
On 11 Sep 2014, at 1:19 pm, Charles Srstka cocoa...@charlessoft.com wrote:
NSDictionary *domain = [def persistentDomainForName:@com.apple.TextEdit];
The documentation states that this is not supported under
This is all very interesting and shows that there are issues out there, but
back to my original issue if I’m writing and reading via NSUserDefaults and its
not returning the expected values what else could be the trouble?
rc
On Sep 11, 2014, at 11:59 AM, Charles Srstka
On 9 Sep 2014, at 3:36 pm, Rick C. rickcort...@gmail.com wrote:
I write some data to my .plist using standard NSUserDefaults
Are you writing the .plist file, or are you using the NSUserDefaults object
exclusively? From 10.9 the .plist isn't updated by NSUserDefaults, so values
there can be
Thanks for the help. So I have double-checked and the info in question that is
not sticking is NSString/NSData being written:
[[NSUserDefaults standardUserDefaults] setObject:stringObject
forKey:@“MyStringKey”];
[[NSUserDefaults standardUserDefaults] setObject:dataObject
forKey:@“MyDataKey”];
Are you calling synchronise too when you're writing?
[[NSUserDefault standardUserDefaults] synchronise]
Verstuurd vanaf mijn iPhone
Op 10 sep. 2014 om 07:43 heeft Rick C. rickcort...@gmail.com het volgende
geschreven:
Thanks for the help. So I have double-checked and the info in
Hi,
I write some data to my .plist using standard NSUserDefaults but recently I
have been getting user feedback (less than 5% of users) that after every launch
of the app the data needs to be entered again. I’m in the process of doing
some debugging but can anyone think of a reason why this
23 matches
Mail list logo
