> On 8 Sep 2018, at 21:20, Andreas Falkenhahn wrote:
>
> Unfortunately not. I can see my app in the lsdump and the path points to the
> network share but purging the LS database doesn't have any effect. macOS
> still loads the old version of my app, not the latest one on the share. Only
> by
On 07.09.2018 at 23:45 Sean McBride wrote:
> On Mon, 3 Sep 2018 15:31:37 +0200, Andreas Falkenhahn said:
>>Optimally, I'm looking for a solution to flush the app bundle cache on
>>the iMac from the makefile that I run on the Mac Mini I use for building.
> Not sure what "the app bundle cache" is
On Mon, 3 Sep 2018 15:31:37 +0200, Andreas Falkenhahn said:
>Optimally, I'm looking for a solution to flush the app bundle cache on
>the iMac from the makefile that I run on the Mac Mini I use for building.
Not sure what "the app bundle cache" is, but maybe nuking the LaunchServices db
would
On 6 Sep 2018, at 13:59, Andreas Falkenhahn wrote:
>
> On 06.09.2018 at 11:31 Alastair Houghton wrote:
>
>> On 6 Sep 2018, at 05:23, Jeff Szuhay wrote:
>> Did you try clearing the defaults persistent domain in your code?
>> I don’t think that is likely to help. Andreas was complaining that
>>
On 06.09.2018 at 11:31 Alastair Houghton wrote:
> On 6 Sep 2018, at 05:23, Jeff Szuhay wrote:
> Did you try clearing the defaults persistent domain in your code?
> I don’t think that is likely to help. Andreas was complaining that
> the code in his bundle was being cached somewhere, so when he
>
On 6 Sep 2018, at 05:23, Jeff Szuhay wrote:
>
> Did you try clearing the defaults persistent domain in your code?
I don’t think that is likely to help. Andreas was complaining that the code in
his bundle was being cached somewhere, so when he rebuilt it didn’t always load
the new version.
Did you try clearing the defaults persistent domain in your code?
Something like the following (the juicy bits are in red) :
NSUserDefaults * myAppDefaults;
myAppDefaults = [[NSUserDefaults alloc] initWithSuiteName: (NSString*)
myAppBundleID ];
then, to clear:
#if
On 4 Sep 2018, at 19:57, Andreas Falkenhahn wrote:
>
> On 04.09.2018 at 18:27 Marco S Hyman wrote:
>
>> Have you tried disabling SMB client side caching?
>> https://support.apple.com/en-us/HT207520
>
> Doesn't change anything. Maybe because the share is SMB 1, not SMB 2 or 3 as
> stated in
On 04.09.2018 at 21:02 Alex Zavatone wrote:
> I meant just the bundle for your app. If you get the wrong bundle
> and you know it, what would happen if you deleted or renamed that bundle,
> even if only temporarily?
> Would it force the new bundle to resolve?
Yes, but once again, I can have
I meant just the bundle for your app. If you get the wrong bundle and you know
it, what would happen if you deleted or renamed that bundle, even if only
temporarily?
Would it force the new bundle to resolve?
Sent from my iPhone
> On Sep 4, 2018, at 2:00 PM, Andreas Falkenhahn wrote:
>
>>
On 04.09.2018 at 19:33 Alex Zavatone wrote:
> Question, what causes the bundle to be cached in the first place?
> Is there a way to force that to happen again? If you know what the
> bundle is, can you rename part of it or delete it to force an
> update?
Sure, as I wrote in my very first
On 04.09.2018 at 18:27 Marco S Hyman wrote:
> Have you tried disabling SMB client side caching?
> https://support.apple.com/en-us/HT207520
Doesn't change anything. Maybe because the share is SMB 1, not SMB 2 or 3 as
stated in the article.
--
Best regards,
Andreas Falkenhahn
Question, what causes the bundle to be cached in the first place?
Is there a way to force that to happen again? If you know what the bundle is,
can you rename part of it or delete it to force an update? Cheezy, I know, but
I’m just trying to get some insight into how to do this.
> On Sep 4,
Have you tried disabling SMB client side caching?
https://support.apple.com/en-us/HT207520
I don’t know if that note pertains to current versions of macos.
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or
> Le 4 sept. 2018 à 17:01, Andreas Falkenhahn a écrit :
>
> On 04.09.2018 at 15:54 Alastair Houghton wrote:
>
>> OK. Have you tried logging the path of a file in the bundle, so you
>> can see where it’s being read from?
>
> CFBundleCopyBundleURL(CFBundleGetMainBundle()) always returns the
On 04.09.2018 at 15:54 Alastair Houghton wrote:
> OK. Have you tried logging the path of a file in the bundle, so you
> can see where it’s being read from?
CFBundleCopyBundleURL(CFBundleGetMainBundle()) always returns the path
of the bundle on the network volume.
> If the path still says the
On 4 Sep 2018, at 14:30, Shane Stanley wrote:
>
> On 4 Sep 2018, at 11:28 pm, Alastair Houghton
> wrote:
>>
>> On 4 Sep 2018, at 00:19, Shane Stanley wrote:
>>>
>>> On 3 Sep 2018, at 11:31 pm, Andreas Falkenhahn
>>> wrote:
I'm looking for a solution to flush the app bundle
On 4 Sep 2018, at 11:28 pm, Alastair Houghton
wrote:
>
> On 4 Sep 2018, at 00:19, Shane Stanley wrote:
>>
>> On 3 Sep 2018, at 11:31 pm, Andreas Falkenhahn
>> wrote:
>>>
>>> I'm looking for a solution to flush the app bundle cache
>>
>> If you find one, I'd love to know what it is. I had
On 04.09.2018 at 15:28 Alastair Houghton wrote:
> Is the application in question sandboxed? If so, have you checked
> to see whether the application bundle gets copied into the sandbox?
> (I don’t have time to look right now myself, but it might make sense
> to do that for sandboxed bundles
On 4 Sep 2018, at 00:19, Shane Stanley wrote:
>
> On 3 Sep 2018, at 11:31 pm, Andreas Falkenhahn wrote:
>>
>> I'm looking for a solution to flush the app bundle cache
>
> If you find one, I'd love to know what it is. I had no luck at all.
Is the application in question sandboxed? If so, have
On 04.09.2018 at 01:19 Shane Stanley wrote:
> On 3 Sep 2018, at 11:31 pm, Andreas Falkenhahn wrote:
>> I'm looking for a solution to flush the app bundle cache
> If you find one, I'd love to know what it is. I had no luck at all.
Aren't there any Apple engineers on this list anymore? :-)
--
On 3 Sep 2018, at 11:31 pm, Andreas Falkenhahn wrote:
>
> I'm looking for a solution to flush the app bundle cache
If you find one, I'd love to know what it is. I had no luck at all.
--
Shane Stanley
,
___
Cocoa-dev mailing list
On 03.09.2018 at 16:07 Mark Allan wrote:
> Sounds like you need a way to refresh the filesystem cache rather
> than some sort of "app cache". Being a network volume, I suspect a
> fair amount of file/directory cacheing goes on.
That's what I was suspecting as well but it really turned out to be
Not really Cocoa-related but maybe somebody on here knows how to solve this:
I build my application on a Mac Mini system using makefiles on a network drive
(SMB). I don't use Xcode. Now I want to run the application from the network
drive on a different machine, an iMac.
However, the iMac
24 matches
Mail list logo
