Motherfucking Android Fucking Studio. Just told me there is an update for the fucking simulator, and after the update it refuses to even sync. Fuck!

Could on physical device? Also not to be “that guy” but it’s an emulator and only reason I’m being picky is I’m used to iOS simulator and there is a huge difference. But physical devices is the way to go if it’s an option

@NSGangster
It's not related to the device. Problem is, why updating the emulator even touches the build tool chain?

@FuckJava new assemblies the gradle doesn’t have compilers for?

@NSGangster

That is besides the point. The point is, project was compiling and gradle was fucking working. How is updating the emulator related to even touching gradle?

@FuckJava um because if your outdated build tool targets a version of droid that expects methods that don’t exist in build tools compiler it can’t compile to binaries? If you want a better idea then try using android studio from five years ago to build a project that uses android wear, before it existed. How you expect it to build? You can expect a lot of build tools to be backwards compatible, but I’ve never heard of one that is forwards compatible.

@NSGangster

Seems like you don't get my point. Nothing whatsoever in the toolchain was supposed to changed. The only component that was updated was the fucking emulator and intel HAXM. When I replace the wiper blades on my car, I don't expect to get a flat tyre.

I think your frustration lies in that they suggested an update for a emulator that wasn’t compatible for your current gradle to build on. In iOS you can’t get the simulator updates UNTIL you update the Xcode SDK/build tools (Xcode update installs the new simulator runtimes after it itself is updated.) they should considerably that pattern or at least for current gradle plugin compatible

@NSGangster
Hence, mother fucking Android fucking Studio. But I should have expected short-sightedness to be a necessity for Java developers