I’m having the same issue.
Hi, Thanks for reporting this issue. We are unable to reproduce it on our test machines currently, but are still looking to investigate further. Are you using the version of Aeon Timeline downloaded from our website, or are you using it from the AppStore? Thanks, Jess
Hi Aeonjess, I’m using Version 2.8.2 (33609) of Ulysses and Version 2.2.2 (2.2.2) of Aeon Timeline. Aeon Timeline is able to load and run Ulysses, but can’t create an interface with it. The same error message is received whether Ulysses is running or not when initiating the connection. I believe it is some kind of permission problem, but have not been able to determine exactly what that is. The reason I say that is because the first time I tried to connect, there was a dialogue box (from Ulysses) that asked if I would grant permission to Aeon. I tried to click on the box, but it disappeared as soon as it achieved focus. That box has never reappeared, after multiple tries with reloading both programs, etc. Cheers, DW
Hi Donald, Thanks for the additional information. Can you confirm if you downloaded Aeon Timeline via the AppStore or directly from our website? We suspect the AppStore Sandbox is likely to be involved in blocking Ulysses' response back to Aeon, so if you can confirm the source of your original download that will help narrow down the possibilities. Jess
Right. I am using the version from the App Store.
Can you try to download and install from our website here: http://www.aeontimeline.com/download/ We suspect that running that version once (in trial mode is fine, even with the trial mode blocked may work) will allow the AppStore version to work from then on. If it does, then we have most likely identified the cause and re-submit a version for the AppStore with the appropriate sandbox permissions. Jess
Okay. I’ll give it a try.
You can either install it to a different location, or if you put it in Applications, delete it once you have run it, and re-install from the AppStore after that. While you have the direct-download version installed, it may be worth creating a test file to see if you can get further with the Ulysses testing first before moving back to the AppStore version.
I got that to work. I first ran the direct-download version, and that forced the permission dialogue to reappear in Ulysses. Then, I re-ran the App Store version of Aeon, and Ulysses asked for permission again, and that worked as well. Now, there are two problems. 1) Speed. I have 950+ files/pages in Ulysses and Aeon is reading the entire structure into the cloud window. Can I just identify a single directory/group, and have that group linked to the Aeon project. 2) Changing the display options works intermittently. I want to add tags to the display, but it won’t respond. It did work once, but now has quit working. Thanks, DW
Hi Donald, Glad you got it working. I will submit an update to the AppStore today to fix the issue for others, and ask them to expedite the review process if possible. To cover your other items: *1) Large Ulysses Projects* Yes, this is something that didn't really get picked up during beta testing but has been something I have been thinking about over the last few days... the size of some people's Ulysses libraries caught me by surprise. There is currently no workaround, but I am considering options here. It seems the best option may be to allow the user to select a specific directory as the "Top Level" directory, and then only look at the content within that tree. The hard part is working out a User Interface to allow that to happen, and to allow the user to get back to the full tree if they feel they have made a bad choice. I would also need to consider what to do with the other "special" folders in that situation - the Inbox and Trash, for instance, that I probably need to interact with in any case. As someone with such a large repository, do you have any though ts on how you would ideally like to see it work, or what would be most useful to you? Once we nail down an approach, I imagine I can implement a change pretty quickly. *2) Display Settings* Bane of my existence, this one. It is the one known bug that I haven't been able to crush, as no one has been able to report a consistent use case to make it happen. For most people, simply closing the timeline file and re-opening it makes the drag and drop in Display Settings start functioning correctly again. I have seen the issue occasionally too, but have yet to come up with a set of steps that can reliably reproduce it, which makes it impossible to fix. If you have a particular timeline file or particular steps that cause the problem to reappear in a consistent manner, I would love to hear it! :-) Thanks, Matt
Hi sorry for late reply, I also did the trial download but could not run it as it say's I have 0 days of trial available. Regardless I closed (cancelled) it and ran the Aeon2 I have already installed from app store and the sync seems to work. at least I'm further in set up then I could before. Thanks kindly for investigating this!
Hi, No problem, I expected it would work even if the trial blocked you. The key bit of magic happens before the trial window kicks in. What is actually happening there is that Aeon Timeline is telling MacOS to expect commands for "aeon" URLs and to send them our way. The website version does this, but the AppStore version does not. So once you run the regular version once, Apple knows about the "aeon" URLs from then on and can send them our way even when you are running the AppStore version. Didn't show up in our testing because we tested both versions on the same group of machines, and there is no easy beta testing through the AppStore, and so the problem was hidden from us until we deployed through the AppStore. I will submit a fix for it today. Sorry for the bug and thanks for your patience! Matt
Hi All, The Apple Review team set a record time for approving the release, so version 2.2.3 has just been released to the AppStore and should fix this issue. If anyone else experiences an error message like the one above after upgrading to 2.2.3, please let me know. Thanks, Matt
Great work! I can confirm the appstore update works fine for the issue I was experiencing.