4 ms·
Okay. That's almost crazy. In my almost 3 years of maintaining our app that was originally written in Eclipse, we never had to face any single issues like this.
by mundanevoice 9y ago
Okay. That's almost crazy. In my almost 3 years of maintaining our app that was originally written in Eclipse, we never had to face any single issues like this. There were some minor issues but never like this. It makes me wonder if the your project structure or the way project is written is crappy.
- pjmlp 9y agoWell, just spend some time reading Android developer forums on Reddit, G+ or Google groups, every time there are new SDK or Studio stable releases. The dheera is not alone.
- mundanevoice 9y agoWell, the rule of thumb is that if you need stability, never upgrade on the first day of release but rather wait for 1 week or two. I personally have faced and upgraded my apps through many of these upgrades and there was rarely an earth-shattering issue that I was not able to solve. YMMV.
- V-2 9y agoWell, yes, it always happens to someone - I mean, every upgrade will break some stuff for some devs. After all, the userbase of Android Studio is quite sizeable. What I find hard to believe is that these problems would hit the same bunch of people every time, and on the top of it, affecting every project they work on. Come on. And this is what dheera claimed ("almost every release of Android Studio has succeeded in breaking every single Android app"). If it's really so extreme, I'd say that he - or she - is not unlikely to be alone, or close to that.
- kuschku 9y agoThe crazy part is, while I have the same issues with every release of Android Studio – the same project in IDEA works just fine, without any trouble, ever. In fact, JetBrains quality and reliability has been much higher than the piece of shit IDE Google has been producing.