Change Account for In-App Purchases

TL;DR Uninstall app. Go to Play website. Login your preferred account. Request remote install of the app. In-app purchases can now be paid with your preferred account.

On my Android phone I use two Google accounts: my private and my work account. Both are linked to the Play store. While Android supports multiple accounts wonderfully in virtually all aspects, in-app purchases is the exception.

Whenever I wanted to use in-app purchases the Play store only offered me to pay through my work account. I don’t want to link purchases to my work account because I am certain that I won’t work for my employer forever. And I hate to pay twice.

Unfortunately, it is impossible to switch the accounts in the payment workflow or anywhere in the Android UI. The only solution I was able to find was to uninstall the app and request a remote install through the Play website with being logged-in in my private account.

As soon as the app is on your phone, you can pay the in-app purchase with the account you used to install the app.

Spotify in the Browser

I love Spotify’s new web player. No Ads and no weekly limit for no cash. I guess, that’s due to its Beta status. Anyway, it’s great because it works on Linux :)

Btw: Even though the link to the player sends you by Facebook, you don’t need to have a FB account or link your account with Spotify.

First Steps with Apps Script: Read from and Write to a Spreadsheet

With Apps Script the Google Apps get a lot more powerful. Unfortunately, the first steps are not too easy. I found it fairly hard to grasp the mental model of how the scripts interact with the Apps. With a little script and some accompanying description I hope to provide the right hints for everyone to successfully read data from a spreadsheet, do something with it and write the results back to the sheet.

[Read More]

Debugging Tip for the Feedback Service of the APNS

Debugging Apple’s Push Notification service is a pain. Only little feedback if the dispatched notification was malformed or in some other way erroneous. But even worse is the service’s accompanying feedback service. The feedback service provides an iOS developer with a list of devices that have uninstalled your app. Debugging it is hell. Not only will Apple empty the list every time the feedback service is called. Hence, test cases have to be reconstructed strenuously by hand every time. But there is a mean bug. If the iOS device on which you deleted our application doesn’t have another development app installed that uses Apple’s sandbox environment for push notifications the feedback service will never tell you that your app was deleted.

Thus to properly debug the feedback service you need another app that is registered with the APNS. It doesn’t need to be more than a barebone application. When testing if your server can handle the feedback service properly you must always send the device that has deleted your app one more notification so that the APNS learns that the app isn’t there anymore.



Yeah… nerd level increased by a bit. Finally there is code running again under my domain that I can actually see, read, browser, change, modify and eat :)

Anyway… even though there is a very straightforward step-by-step guide for setting up the blog software, I ran into a little problem: Heroku complained that I didn’t specify an app just after I created the app :(

In case anyone else has the issue as well: Good news everyone. It can be solved by the following:

git remote add heroku
git config heroku.remote heroku

Of course, you gotta have to change myblog to whatever you called your application (first command of step 5).