I'm year 10 and my final project for APCS is to make a game/app and turn in the code, a video of it running, and a written response. My problem is that the entire class was taught using Code.org's AppLab and the readRecords() function is seemingly broken , I think its readRecords() because the concept version of the game doesn't use readRecords and works fine, but the current version does and nearly half of the buttons in the game don't work most of the time. Including the buttons to log in, sign up, etc.Meaning I can't even get past the welcome screen. My code isn't the issue and this is due in a few hours. s u g g e s t i o n s p l e a s e.
AppLab "readRecords()" is broken
367 Views Asked by Stanly At
2
There are 2 best solutions below
2

Because you are saying that your buttons do not work "most of the time", and the readRecords() command is asynchronous, I suspect you have a timing issue of some kind. To help determine if the problem is with the readRecords() command or with how you're using it in your project, you could put the share link to your project here, or in a message to code.org support.
applab docs for
readRecords
it looks like
readRecords
should probably still be supportedyou should use your browser's javascript console/debugger to find your application's point of failure
here's some ideas for where that point of failure might be:
in your code which is using
readRecords
incorrectlyin applab's
readRecords
code itself (less likely)