6 Replies Latest reply on Oct 18, 2015 6:12 AM by Fred(CH)

Keychain does not remember Login

seevogel Oct 17, 2015 8:33 PM

FMP 14.0.3 (and earlier)

OS X 10.11

I have to log in manually every time.

The bigger one:

Every time I trigger an AppleScript to set a Reminder in "Reminders" I get a dialog 70 times to give permissions for FileMaker 14 to access reminders.

… FileMaker is registered already to have access to reminders.app (security panel in system preferences)

1. Re: Keychain does not remember Login

Fred(CH) Oct 18, 2015 1:51 AM (in response to seevogel)

Just have to restart the computer one time after the update and that is done.
Like Show 0 Likes(0)

Actions
2. Re: Keychain does not remember Login

Benjamin Fehr Oct 18, 2015 1:55 AM (in response to Fred(CH))

I think we saw a similar behavior with FMP 13 in the past
Like Show 0 Likes(0)

Actions
3. Re: Keychain does not remember Login

Fred(CH) Oct 18, 2015 1:59 AM (in response to Benjamin Fehr)

Yup and if my memory is good, seevogel too
Like Show 0 Likes(0)

Actions
4. Re: Keychain does not remember Login

seevogel Oct 18, 2015 4:09 AM (in response to Fred(CH))

ok, restart solved the problem ( the AppleScript problem too) temporarily but either that behavior should be fixed or the FileMaker Installer should force to restart after the installation process or at least there should be a message for the user better to restart.
And YES I had the same issue one and/or two years ago and it is not fixed until now. Seems to be an exotic bug (?)
Like Show 0 Likes(0)

Actions
5. Re: Keychain does not remember Login

Benjamin Fehr Oct 18, 2015 4:23 AM (in response to seevogel)

with FMP 13, one restart solved the problem permanently, afaik.

Off topic but maybe relevant: I saw similar issues with Mac OS betas when starting JAVA Applications
Like Show 0 Likes(0)

Actions
6. Re: Keychain does not remember Login

Fred(CH) Oct 18, 2015 6:12 AM (in response to Benjamin Fehr)

Yes it is the case. This can only reoccur after another software update.

with FMP 13, one restart solved the problem permanently, afaik.
Like Show 0 Likes(0)

Actions

Go to original post