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 wrote:
> Em 11/09/2
Em 11/09/2014, à(s) 01:07, Rick C. 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?
1) Do all preferenc
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 wrote:
> On Sep 10, 2
On Sep 10, 2014, at 10:50 PM, Graham Cox wrote:
> On 11 Sep 2014, at 1:19 pm, Charles Srstka wrote:
>
>> NSDictionary *domain = [def persistentDomainForName:@"com.apple.TextEdit"];
>
>
> The documentation states that this is not supported under sandboxing.
>
> When you say "does not ... work
On Sep 10, 2014, at 10:34 PM, Marco S Hyman wrote:
> On Sep 10, 2014, at 8:19 PM, Charles Srstka wrote:
>
>>
>>> Where did you get the idea that NSUserDefaults doesn't work for sandboxed
>>> apps? It certainly does.
>>
>> #import
>>
>> int main(int argc, const char * argv[]) {
>> @autore
On 11 Sep 2014, at 1:19 pm, Charles Srstka 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 mean.
--Graham
___
On Sep 10, 2014, at 8:19 PM, Charles Srstka wrote:
>
>> Where did you get the idea that NSUserDefaults doesn't work for sandboxed
>> apps? It certainly does.
>
> #import
>
> int main(int argc, const char * argv[]) {
>@autoreleasepool {
>NSUserDefaults *def = [NSUserDefaults stand
On Sep 10, 2014, at 9:39 PM, Graham Cox wrote:
> On 11 Sep 2014, at 12:14 pm, Charles Srstka 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 sandb
On 11 Sep 2014, at 12:14 pm, Charles Srstka 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.
--Graham
On Sep 10, 2014, at 7:04 PM, Scott Ribe 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. Apparently
> there's someth
On Sep 10, 2014, at 7:41 PM, Kyle Sluder 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 NSUserDefaults…
>
On Sep 10, 2014, at 6:42 PM, Graham Cox 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 through
> the defaults
On 11 Sep 2014, at 10:32 am, 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…
Then you should be fine. The point is that the .plist d
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
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 fig
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
> 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 t
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 Prefe
On 10 Sep 2014, at 3:43 pm, Rick C. 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”];
> [[NSUserDefaults standard
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." het volgende
> geschreven:
>
> Thanks for the help. So I have double-checked and the info in question that
> is no
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”];
On 9 Sep 2014, at 3:36 pm, Rick C. 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 very much out of date
22 matches
Mail list logo
