Exception in rendering! Message: window is not defined ReferenceError: window is not defined at new c (/tmp/execjs20161208-103658-nbk0imjs:136:3912) at m.mountComponent (/tmp/execjs20161208-103658-nbk0imjs:47:15602) at /tmp/execjs20161208-103658-nbk0imjs:49:31860 at a.r.perform (/tmp/execjs20161208-103658-nbk0imjs:47:12503) at Object.a [as renderToString] (/tmp/execjs20161208-103658-nbk0imjs:49:31821) at r (/tmp/execjs20161208-103658-nbk0imjs:50:21164) at Object.S.ReactOnRails.serverRenderReactComponent (/tmp/execjs20161208-103658-nbk0imjs:32:6073) at eval (eval at <anonymous> (/tmp/execjs20161208-103658-nbk0imjs:173:8), <anonymous>:10:23) at eval (eval at <anonymous> (/tmp/execjs20161208-103658-nbk0imjs:173:8), <anonymous>:17:3) at /tmp/execjs20161208-103658-nbk0imjs:173:8
My car’s old fobs broke or cracked so I sent to the dealership. They were able to replace them with a new key and fob and didn’t have to program it since he was able to use the old chips. For a week it worked fine, but then the remote sometimes wouldn’t work consistently. Sometimes the car wouldn’t start without manually activating the door locks a few times. After that the fob remotes completely stopped working. Could it be old batteries, lack of programming, or what do you suggest would solve this problem?
Hello. I believe the key fob chip is the problem. Since the other parts on the key failed first, it is likely that the chip wasn't too far behind. Replacing the chip in the fob should fix your problem. I suggest taking the key back to the dealer. Inform them of the key fob issue you are having and that it was just fixed there not long ago. That should influence them to at least diagnose the car under warranty. Depending on what the fob needs, they may fix it under warranty, too being that they were the last to have worked on it.
Have a car question? Get free advice from our top-rated mechanics.
Our certified mechanics come to you ・Backed by 12-month, 12,000-mile guarantee・Save up to 30%