Since the credentials in the package are no longer valid, we're no longer violating Google's Terms of Service. And the package works if you generate an AndroidID with dummydroid, and use your own credentials, so its ready for testing.
Therefore, this bug can be downgraded in severity while we figure out the best approach to handle this. We will not be able to auto-generate the AndroidID since dummydroid is a GUI-only process, so I don't think its worth anything to prompt the user for their username/password in the package install. I think we can post a message saying you have to run dummydroid or get credentials from elsewhere for this to work. People who want to use matlink's credentials are always free to get it from his git repo. You have to do that anyway, since the credentials change often. No one seems willing to maintain the credentials in the package, so I don't think its so useful right now. If you set up credentials with dummydroid, then they stay working. There are even websites where people share username/password combos for test accounts, one of those could be used with dummydroid to generate the AndroidID in a much more reliable way than including matlink's.
