Yes, something must be caching the app cast somewhere. Last few times it
took about a day before a posting was seen by the updater. I have still no
idea what and under what condition the caching takes place. I suspect it
has to do with sourceforge's new servers.
Christiaan:
I was able to update from 1.4.33 on a laptop running macOS Sierra
10.12.6.
On another desktop machine running macOS High Sierra 10.13.4 my skim
is 1.4.33 and even if I close the app and open it again, it claims
"You're up-to-date! Skim 1.4.33 is currently the newest version
Please do not use 1.4.33 when you have a large number of notes! This has a
writing bug, and I see you ran into that (from the "failed to read unique key
net_sourceforge_skim-app_unique_key for 0 fragments from property list.”
error). You should update to 1.4.34 ASAP. This may well be the cause
Hi Christiaan,
I am pretty sure the ‘saving’ trouble is introduced by osx 10.13. I now have a
mix of Apple workstations running osx 10.10.5 and osx 10.13.2
We did not update skim so we are running skim version 1.4.9 on these
workstations.
For testing I use osx 10.10.5 and skim 1.4.33 (107) on
> On 11 Apr 2018, at 14:58, Rob van Halteren wrote:
>
> Hello,
>
> I have a strange more or less inconsistent problem saving my existing skim
> documents ( with external skim-notes file ) to my storage using Mac osx 10.10
> and 10.13
> It only happens when Skim opens a PDF
Hello,
I have a strange more or less inconsistent problem saving my existing skim
documents ( with external skim-notes file ) to my storage using Mac osx 10.10
and 10.13
It only happens when Skim opens a PDF file and a popup comes up saying that
"external notes file is found”
After opening en