I coded exactly the same as it was in the video, however I got a different result in my log...

Hi, Ben! It's good to hear from you! I actually found the mistake I made by comparing my code with the Ben Deitch's. For some unknown reason I typed the line with the Log in the catch {} block )) so, surely it was never reached)) and I was not getting the log messages that our songs are being "downloaded". Sorry for bothering... however, it worked like a "radio check" and proved to me, that you do come back with assistance!!!

Since your're anyway reading this, you might be interested in some bugs that I found in your Treehouse Android App.

I apologise in advance if you feel unhappy about the lines below. I want you to know that I'm in love with the Treehouse program and I think it is one of the best ones I have ever encountered. So these lines are there only because I see how it can become irreproachable. Hope, you read the lines below with a smile and understanding.

 I often watch your webinars via my mobile while driving to or from my office. It turns traffic jams into a classroom for me and saves heaps of time. Special thanks for that! However, every time I get to quizes - bugs wake up))

1. When there's a "situation" on the road and I cannot type or click the right or wrong)) answers the app's thread gets killed and I have to start it all over again. Sometimes, when I redo a quiz, due to such cases, it returns opposite outcomes for the same answers. E.g. in the previous attempt it says that the right answer for question A is "true" in the next attempt it says the "true" reply is a mistake for the very same question. It is a little confusing... Foreseeing your possible counter arguments, I surely noticed that every next time the answers swap positions and I carefully read the question and the answers before clicking an option)) It is something different... turning a quiz into a riddle)) "Guess what the app is proposing this time")) As a possible hint: Still other red button apears alongside with a message saying that there was a problem connecting to... something I do not remember, either a server or a database... and the app cannot evaluate the reply at all. Usually I reset the program and redo the whole quiz to overcome this issue. Maybe, the two bugs are of the same nature. As a possible solution, may be a package of answers could be soemehow delivered to the app togeather with the quiz and regardless of the connection failures the app could keep staying sure of what in this world is right or wrong))

2. Another uncomfortable thing is that the font is not sizeable in the coding quizes. The letters are big and only few words fit in a line. Once a user taps the screen for scroling, the keyboard pops up and leaves the coding area so tiny that only two or three lines fit in it. This prevents users from seeing the blocks of code and it takes time to find the right place where the lines of new code must fit in. Making this screen sizeable could easily solve this misfortune)) Another idea, in case making this editable field or its font sizeable is hard, is a separate button for turning the keyboard on/off. In such case scroling the area will not inevitably cause "fighting")) with the annoying keyboard.

3. Still other bug "living" in the "coding quizes" prevents the app from showing the possible mistakes in the code prior to sending the answeres for evaluation. Thus, the coding quizes can only be successfully passed on a PC, where everything works perfect. It seems like the Android App is trying to come up with the hints of the mistakes in the code, but something goes wrong and it gives up. Maybe, this code evaluater needs a separate thread or service... I'm sure you can find a better solution))

   Anyway, thanks for your great job in teaching coding!!! Your program is really awesome!!! Despite all the minor drawbacks and regardless whether you ammend the Android App bugs or not, I'm staying with you and learn from you till I become a profeccional coder!!!

Dmitry Bruhanov, Yekaterinburg, Russia

Which course are you working on? (The Music Machine project appears in a few of our courses.) We can also try to help troubleshoot if you paste in your full code and more details from the log.