Unable to print checks

[frangalista]

At the risk of repeating other reports, I am seeing the same error. I have attempted to force a complete reload on the page in case there was a code caching error all to no avail. I am seeing the following error trace in the console of the developer tools:

vendor.ea96ab4c897f5279b393.js:21 ReferenceError: i is not defined
at Scope.scope.getNextCheckToPrint (https://lcrf.churchofjesuschrist.org/fi ... :21:133048)
at Scope.scope.printChecks (https://lcrf.churchofjesuschrist.org/fi ... :21:128316)
at fn (eval at compile (https://lcrf.churchofjesuschrist.org/fi ... :21:221621), <anonymous>:4:329)
at expensiveCheckFn (https://lcrf.churchofjesuschrist.org/fi ... :21:123215)
at callback (https://lcrf.churchofjesuschrist.org/fi ... :21:252516)
at Scope.$eval (https://lcrf.churchofjesuschrist.org/fi ... :21:142173)
at Scope.$apply (https://lcrf.churchofjesuschrist.org/fi ... :21:142512)
at HTMLButtonElement.<anonymous> (https://lcrf.churchofjesuschrist.org/fi ... :21:252623)
at defaultHandlerWrapper (https://lcrf.churchofjesuschrist.org/fi ... s:21:25434)
at HTMLButtonElement.eventHandler (https://lcrf.churchofjesuschrist.org/fi ... s:21:25282) undefined
(anonymous) @ vendor.ea96ab4c897f5279b393.js:21
(anonymous) @ vendor.ea96ab4c897f5279b393.js:21
(anonymous) @ app.83842bd2e9d08fc35fdd.js:1
$apply @ vendor.ea96ab4c897f5279b393.js:21
(anonymous) @ vendor.ea96ab4c897f5279b393.js:21
defaultHandlerWrapper @ vendor.ea96ab4c897f5279b393.js:21
eventHandler @ vendor.ea96ab4c897f5279b393.js:21

[bryanbeardall]

Having the same issue. Been happening for several weeks. Seems to be server issue and when we try again later, sometimes it will work.

[brpeck]

Been unable to print checks all day. Tried Chrome, Edge, Firefox, cleared cache, cookies, etc... Incognito mode as another thread suggested.
Opened a ticket.... Just letting others know issue is still there.

[ramcreekman]

I have had the same issue yesterday (Sunday) and expect that it was a server problem. I expect the church IT department will be on it right away today. At least I hope so. I'll give them a call when they open in a few hours.

[scgallafent]

They are aware of it and working on a fix.

[betteroffsal]

Anyone find a fix?

[scgallafent]

There isn't a fix that you can make. I talked to the developer working on the issue yesterday and he said that they are aware of it and working on a fix.

[dallasallad]

May have been fixed. -- I was just able to print some today after being unable to print on Sunday. I also heard from our stake clerk that two other wards were also able to print checks today. No idea what the issue was or what changed, other than maybe less connections to the server today.