4 ms·
I had the same thing happening to a bunch of apps based upon a framework I built. The newer API version had problems with existing dependencies, really a shit t
by dep_b 3y ago
I had the same thing happening to a bunch of apps based upon a framework I built. The newer API version had problems with existing dependencies, really a shit ton of work to get back to exactly the same place I was already.
I really respect Microsoft a lot more, where stuff from the 90's has less issues running on the latest Windows version that mobile apps I wrote four years ago on Android.
- kramerger 3y agoUnless the framework you used came from Google that is an unfair statement. You don't blame Microsoft for Adobe Flash not working on Windows 11 store, do you?
- dep_b 3y agoIf Google breaks the framework I built, I still blame Google.
- kramerger 3y agoWhy? Should Android be bloated with compatibility layers for every buggy framework ever existed? Including third part stuff such as Cordova and Ionic that have more or less stopped development? And it's not like Google is randomly breaking things. And even when there are breaking changes they provide support libraries and explain very clearly what has changed and why it needed to be changed. Still, no sympathy for app shops that work according to fire and forget.
- dep_b 3y ago"Compatibility layers": it was a setting that is still a valid setting but you need special permissions for it nowadays. The code was compiling perfectly.
- jonmb 3y ago> Including third part stuff such as Cordova and Ionic that have more or less stopped development? FYI - Ionic is in active development, along with Capacitor, their replacement of Cordova. I recently updated my app’s target to the new Google guidelines and Capacitor made it easy with an automated cli.