Tech Forum Archive

Endless Refresh Loop for Donations on iOS (all browsers) and Safari for Mac

3 postsstarted by janssenv 1,001 viewsoriginal topic

janssenv
New Member
#1
I already have a workaround for this problem, I’m just posting it to help others. I have submitted feedback on the church website as well.

The page donations.churchofjesuschrist.org enters an endless refresh loop on all browsers for iOS. I am using iPhone with iOS 18.4 and I’ve tried Safari, Chrome, Firefox, and Edge. I did not find an iOS browser that worked. On macOS, the Safari browser has the same problem, but Firefox and Chrome worked fine. Chrome on Windows 11 and Android has no problem.

The new website donationsfe.churchofjesuschrist.org works fine (notice the “fe”).
rmrichesjr
Community Moderators
#2
janssenv wrote: Sat Apr 05, 2025 4:59 am I already have a workaround for this problem, I’m just posting it to help others. I have submitted feedback on the church website as well.

The page donations.churchofjesuschrist.org enters an endless refresh loop on all browsers for iOS. I am using iPhone with iOS 18.4 and I’ve tried Safari, Chrome, Firefox, and Edge. I did not find an iOS browser that worked. On macOS, the Safari browser has the same problem, but Firefox and Chrome worked fine. Chrome on Windows 11 and Android has no problem.

The new website donationsfe.churchofjesuschrist.org works fine (notice the “fe”).
Thanks for posting such a detailed analysis of the looping problem. Also, thank you for submitting feedback to the official channel.

The links above somehow became broken. I opened a moderator/administrator discussion about that in case it might be a bug in the forum software. These links are intended to work better:
- https://donations.churchofjesuschrist.org
- https://donationsfe.churchofjesuschrist.org
janssenv
New Member
#3
Thanks for providing fixed links. I’m new to this forum and haven’t learned the quirks yet.

I got a response from the church donation system technical support group. Apparently my stake is part of a pilot program for an upgraded system and that’s why we got the bug. They’re working on a fix and confirmed the workaround described above.