If you are trying to sync LDS Tools, the servers are down and will not be up again until later this evening at the earliest.gfuentesc wrote:What's going on it tel me to try again later
It hasn't been down that long. What version of the app are you running? It may be out of date.robpneu wrote:Is there a current server status site to see if its actually down? I haven't been able to sync on my iPhone and iPad nor has my wife on her iPhone since the beginning of March.
Mine is also syncing now.russellhltn wrote:I did a sync just now and it went though. Version 3.5.4, Android.
This is not a user device issue. It is a connection to the server issue and is beyond your control and may be due to either heavy server load, servers going down, or server maintenance in progress. Just as the message states, try again later. If you get the message on Sunday, then try on a weekday when the activity is lower for the servers.heapgt wrote:I'm getting error "Lds.org down for maintenance . Please try again later" I've uninstalled the app and tried again. Others seem to be able to update. Any special instructions on how to fix this? ver 3.5.3 (6417). Iphone X 12.2
Agreed. I can’t remember the last time i could sync on a Sunday (which is kind of a pain...given that Sunday’s are when presidency meetings are...and we would like to sync)bigmac182 wrote:It seems that every Sunday this is down. That doesn’t seem normal. One would think the Church’s servers would handle traffic.
I have no problem to exit the sync screen and use the app on sync failure (Android).nwtaylor wrote:Same error as everyone else...all day...both devices... and cannot exit the Sync screen. If the possibility exists that the server is down for maintenance then at least allow us the option to see and use the standard UI and not be stuck at the Sync view. Also, the error that ChurchOfJesusChrist.org is down for maintenance is misleading as I can clearly load and see that url.
Thanks
Neil Taylor
Ok, 2 requests (from a software developer of 39 years, including 7 iOS/mobile):jdlessley wrote:The message is cryptic and used for a variety of server issues. There are more than one server used in completing the synchronization process. Only one of those servers needs to be down for you to get the message. Syncing on Sundays during the one day of the week when nearly the entire church is using the online church resources typically causes usage and access overloads. Try syncing on weekdays rather than on Sundays.
I'd suggest routing those to the "contact us" link under "help" in the app. That gets to developers.nwtaylor wrote:Ok, 2 requests (from a software developer of 39 years, including 7 iOS/mobile):
Outdated data is not the only concern. Part of what happens with a sync is to validate that you are still a member of a specific unit and should have access to data for that unit. That verification happens during the sync process. If the app continued to run with syncing, it would be possible for a user to maintain a copy of old data indefinitely by preventing the device from syncing.nwtaylor wrote:2) UX that allows the user to continue to use the app when the state is "Sync required" but when attempts to connect/sync are failing. For example, include options with the new message in the popup above to "Continue using LDS Tools with current (possibly outdated) data" and "Cancel/Retry Sync Later". Something to that effect. Disclaimer that data is possibly outdated is built into the message of the first option. Users can certainly live with that.
What about allowing it just a one-week extension if the syncing fails? The member would have to remember to try and sync sometime during the week, but it would avert a problem with being locked out if the initial time-out coincides with down servers.scgallafent wrote:If the app continued to run with syncing, it would be possible for a user to maintain a copy of old data indefinitely by preventing the device from syncing.
Yes. That would be a simple and acceptable policy and UX.russellhltn wrote:What about allowing it just a one-week extension if the syncing fails? The member would have to remember to try and sync sometime during the week, but it would avert a problem with being locked out if the initial time-out coincides with down servers.scgallafent wrote:If the app continued to run with syncing, it would be possible for a user to maintain a copy of old data indefinitely by preventing the device from syncing.
That's a reasonable idea. We've got some other work going on around this, so it may not be something that goes in just because there is other work going on to improve the process.russellhltn wrote:What about allowing it just a one-week extension if the syncing fails? The member would have to remember to try and sync sometime during the week, but it would avert a problem with being locked out if the initial time-out coincides with down servers.
Hopefully the underlying problem is getting fixed and has priority. But there's always local situations that might arise that prevents syncing when the directory is most needed. So, I'm hoping some implementation of my idea comes to pass.scgallafent wrote:That's a reasonable idea. We've got some other work going on around this, so it may not be something that goes in just because there is other work going on to improve the process.
You already get five chances to pass. I don't know how long that would last, but I would think you would be able at least to get to Monday.russellhltn wrote:What about allowing it just a one-week extension if the syncing fails?
Handbook 1 in LDS Tools, where do I find it?lajackson wrote:
During the long no-sync problem earlier this year, the app kept running for me even though the sync failed. The app recorded the failed sync as the last sync and kept right on going. I did lose specialty items, such as Handbook 1,
Touche! It has been a long month so far, and I am still winding down.Biggles wrote:Handbook 1 in LDS Tools, where do I find it?
You probably got a response...LDS Tools/Library/Leaders/Handbook 1Biggles wrote:Handbook 1 in LDS Tools, where do I find it?lajackson wrote:
During the long no-sync problem earlier this year, the app kept running for me even though the sync failed. The app recorded the failed sync as the last sync and kept right on going. I did lose specialty items, such as Handbook 1,
The smiley face in the Biggles post was an indicator that Handbook 1 is not in Member Tools. It is in Gospel Library. Touche is a French word that, roughly translated, means, Wow, I really should have known that.nwtaylor wrote:You probably got a response...LDS Tools/Library/Leaders/Handbook 1
That's pretty common on Sunday. How are you connecting to the internet? The network you're using may be blocking it, or perhaps a security app is blocking it.KeithT wrote:I have been trying to sync LDS Tools on several iPhones since Sunday morning (May 26) without any luck. The response is LDS.org is down for maintenance. Are there others that are seeing the same problem?
Yes. iOS 10 is no longer supported.lmitchel wrote:Has anyone heard from the developers?
No support for iOS 10laneysearch wrote:Haven't been able to use LDSTools app for the last several weeks on my iPhone 5. Sync gives error "LDS.org is currently down for maintenance. Please try again later." What is the deal?
They're up and down. More down than up. They're trying to figure out "why".toonetown wrote:Is there an estimate when they will be back?
No. And unfortunately, things that go down on the weekend usually do not come back up until Monday, at the earliest. It is painful, but really the only method we mere users have is just to keep trying. Often someone posts here when they are successful so that we can all jump in and overload it again.toonetown wrote:Is there some kind of status page that we can use to know...so we don’t need to post here?
No suggestion but I have the same problem. Two or three tries this morning, Monday 12/9/19jakobfisher wrote:Unable to sync. Getting error message that says LDS.org is down for maintenance. Been seeing this all day.
iPhone 8
iOS 12
Any suggestions?
I'm in the same boat. I even uninstalled the app and reinstalled just for kicks and giggles but still same error when trying to login. Though It tells me that its the wrong login if i use an incorrect password so not the auth servers.toonetown wrote:Been getting this error now for 3 days...is something going on?
Please read through the posts before yours in this topic to learn about the problem and how it is being addressed. Also, this is a user-to-user forum, so no one here will be able to do anything about the problem. There are other numerous topics on this same subject here at the forum that will shed some light on the issue.taaronbennett wrote:Please fix this.