Just installed the 10.0.0 update and tried to download a tree from Ancestry. It still fails and cancel on the countdown window still does not work requiring a force quit to exit RM.
It has been 9 months since this issue was reported and still no resolution. We now have a new version and it is still Intel code, requiring Rosetta to run. It seems Mac issues are not a priority.
I would not say Mac issues are not a priority. With the problem you are reporting its just been extremely difficult to find what the issue is when the trees are extremely large. If we could find a smaller tree with the same issue it would make finding the cause a little easier. If you have access to a Windows computer that can also complete the download of the tree, and that’s not always a guarantee depending on the issue, I would suggest using that. Then see if it will open in TreeShare on the Mac.
have you considered the interplay of internet service speed down/up with tree size and timeout issues. My small 400# tree is fine on fast speed but failed on a slow service. Mac.
Hi Renee, I first reported this issue 9 months ago and going back through the forums, I found someone had reported the same issue under version 8, so it has been going on for awhile. I have downloaded smaller trees with no issue, so it appears to be size related. Another user replied under my original post that it is some SQLite file and he can duplicate the problem at will. I don’t have a Windows computer and have no desire to get one or use one. If RM is being sold as a Mac program, it should work on a Mac without requiring a Windows intermediary.
Hi Rooty, Internet speed and/or the requirement for Rosetta to run RM was my first suspicion, but another user claims it’s related to a SQLite file used for the download. I don’t really know what the underlaying issue is, I would just like to get it fixed.
Renee, I would like to reiterate my offer for your developers to keep a copy of my database and use it for testing. It would make it easy for your developers to reproduce many of the issues we are seeing, there’s only a handful of living people in there and nothing that’s not already published elsewhere. There are several books and the only RM feature I’m not using extensively is associations.
Have you already shared it and the Ancestry tree with us? I know we have a selected handful of them to work from.
Do not expect a resolution from the team any time soon.
I’m still waiting for a positive response to the version 8 issues I had on my PC.
There were Mac issues when 9 was released, best to wait and let others Beta test and have the headache.
Just installed the 10.0.1 update and tried to download a tree from Ancestry. It still fails and cancel on the countdown window still does not work requiring a force quit to exit RM.
Just installed the 10.0.2 update and tried to download a tree from Ancestry. It still fails and cancel on the countdown window still does not work requiring a force quit to exit RM.
There were no changes in this update addressing any issues with existing Ancestry trees not downloading. If something like that is included it will be on the update history list.
Renee, Thanks for responding. I am ever hopeful that if this isn’t specifically listed, it Is included in the miscellaneous fixes. Even if it isn’t, I want to keep the issue alive. I first reported it in October of last year, so it’s been unresolved for nearly a year.
This is an old issue that seems to be a RM timeout problem under conditions where FTM handled the same file just fine. When I switched to a faster internet service RM worked.
Hi Rooty, I have the fastest available to me connection, but the issue is ongoing. I like the features of RM, but I may have to consider switching to something specifically written the the Mac. Whatever translator RM is using does not appear to create very efficient code.
First development needs to find what the issue is with the Ancestry tree that is causing the download issue. The larger the tree the more it becomes looking for a needle in a haystack. Rooty could be right and its something on your end. We have some trees, don’t recall off hand if one is yours or not, that don’t download even on our Macs, even Windows too. Hopefully, when the cause is determined for one of those it will address your specific issue. When fixed it wouldn’t be considered a minor issue and not listed. We would want others to test and report if it addressed their problem too.
Renee, keithcstone (in this thread) claims to have isolated it to a file in the database and has offered to help with any additional analysis. Has anyone pursued this lead?
RM is intel only code which is translated by Apple’s efficient Rosetta app and I was told a year ago there was no interest in mac native code. Since my 400# file worked fine in FTM 2019 (2024 out this fall) and RM failed with both on a slow connection but worked on a fast connection RM definitely has a timeout issue with Ancestry. I suspect the Windows version does better since the mac port was done without outside professional help.