I am having problems with the app on my android phone.
Best Answers
-
Hm ...
Short Answer: ONLY a "Transcription" of the Details of the Record; NOT, an "Image" of the actual Record.
When I 'Select' that "Compare" ...
The next page/screen is a comparison of, the Record (on the 'left-had-side'); and, what is in "Family Tree" (on the 'right-hand-side'),
In the side for the Record there appears to be a 'Thumb Nail" of the "Image" ...
When I 'Select' that, it appears to start to be going to the "Image" ...
But, the next page/screen comes up with "Oops, something went wrong. Please refresh the page" ...
Whereas, there is NO way to "Refresh the Page" ...
Question: Is that what you are referring to? [ ie. Do you get the "Details"; but, cannot access, an "Image? ]
Brett
0 -
Suggestion
So ...
That said ...
'Yes', there DOES appear, to be a problem/issue, with regard to accessing "Images", for the "Record Hints", as presented, through the "Mobile" Application version of "Family Tree" of 'FamilySearch'.
I am just another 'lowly' User/Patron like yourself ...
[ And, as I originally advised, NOT one who uses the "Mobile" Application version of "Family Tree" of 'FamilySearch' for any REAL work ... ]
As such ...
Can I humbly suggest that; as,
In regard to this in this "Community.FamilySearch" Forum ...
(1) There is NO specific 'Group', pertaining to; and,
(2) There is NO specific 'Topic', in the 'Ideas' ( "Feedback" ), for
the "Mobile" Application version of "Family Tree" of 'FamilySearch'
And, as such, that you may be 'best off', providing 'Feedback' DIRECTLY through to the "Team", Designing and Developing, the "Mobile" Application version of "Family Tree" of 'FamilySearch', itself.
[ As, the "Computer" Web version; and, the "Mobile" Application version, of "Family Tree" of 'FamilySearch', are two (x2), separate; and, distinct, "Teams" ... ]
Here is a "Screenshot" of the page/screen that results when you try to access an "Image" of a Record; and, that, ERROR Message of ... "Oops, something went wrong. Please refresh the page" ... appears.
IF, you have a look on the 'right-hand-side' of that page/screen (ie. in this case, the "Image"); THEN, you will 'see' a "Feedback" 'Link'/'Button.
Select that ...
You will then be presented with two (x2) "Options" / "Choices".
▬ Specific feedback ... on that specific page/screen
▬ Generic feedback ... General to the application
I would suggest that you select that FIRST one (ie. Option/Choice)
Then RAISE this matter as a Problem / Issue ( ie. Fault / Flaw ), SPECIFICALLY, in relation to the "Mobile" Application version of "Family Tree" of 'FamilySearch'.
From there, it is just a matter of waiting for, a response; and, hopefully, a resolution.
I know that this is not much help; but, I hope this provides you with some direction to take.
Brett
0
Answers
-
FYI
Although, I don't use the "Mobile" Application version of "Family Tree" of 'FamilySearch' for any REAL work ...
I just checked, the "Mobile" Application version, of "Family Tree" of 'FamilySearch', on my 'Android' "Mobile" Phone; plus, I am using the latest version of the application ...
The "Record Hint(s)" (ie. that Little 'Blue' Icon, on the 'left-hand-side', next to the 'Portrait' and 'Name') OPENS (well, 'drops down') just fine to be able to, 'View' the record(s), with, both, a "Not a Match"; and, "Compare", links/buttons, at the bottom.
I just thought I would pass that on.
Brett
ps: Just in case, make certain that you are using, the lastest, up-to-date, version, of the "Mobile" Application version of "Family Tree" of 'FamilySearch', on your "Mobile" Device - just a thought.
0 -
Were you able to see the actual record? The photo of the Census, etc????? That is the part that will not open.
0 -
Thank you Brett. For my REAL work I also use the computer, but when I am sitting in a waiting room or waiting for my wife somewhere, I like the app. Thanks for the confirmation that it's the app that is the problem.
Charlie
0 -
😀
0 -
I am using the FamilySearch app on an IOS device and if the image is available on FamilySearch, I can also see it on my IOS device. I think it may be a problem with the Android app that the engineers will have to address. Your feedback would be helpful. Good luck.
0