Someone hasn't tried to do Azure development with Visual Studio if they think this Release/Debug type management is a nightmare. Oh let me name the number of inconsistent ways of transforming config files depending on environments.
Granted, given all the complex permutations and needs the iOS development team and XCode and Apple App Store has to support, there's probably a lot of method to the madness, a lot of "necessary" complexity. The problem is that if you zoom out a bit, much of the complexity one originally thinks is necessary, is not actually necessary, if you change one or more of your premises.
I'd have killed for a simple macro syntax to use within my config files. Hell, at one point I was actually (stupidly, one of the more futile tasks I've ever tried) editting the MSBUILD files by hand.
This means I have to manually edit connection strings, debug settings and more that vary between our local ASP.NET servers, our intranet dev server, our local emulator environment and then debug/prod Azure instances.
If I'm mistaken I would be ecstatic to be corrected. Hell, I'd have paid money out of pocket for a macro/conditional solution for this problem when I was working on this project. Also, if it's just too off-topic, please accept my sincere apologies. I just found it kinda nitpicky to pick on Android for this, although I can sympathize with the author if they're accustomed to more "open" languages and frameworks that are more tool-friendly.