stuartmorgan-g
stuartmorgan-g
> the project started demanding a new compileSdk version Can you elaborate on what you mean by "demanded"? You've referred to this several times as a warning; warnings are advisory,...
> Yes, a warning is usually just a warning, but the language on this warning (which I know is not from you guys but from Android SDK itself) got me...
> Also, since increasing the compileSdk exposes a whole new set of API changes, I would not say that this does not affect the API surface -- it does affect...
> How about simply not even showing the warning, if you are convinced if a library uses newer APIs, the build will break? Because a build break message caused by...
> Doesn't that cut out many potential new users of your app, because they won't even be able to download the app from the Google Play store if their API...
Not that I am finding; thanks for following up on this!
> does the current behavior align with the exception handling patterns in the package repo? Only to the extent that our current patterns don't align with our goals 🙃. This...
(We may also have the list of registered channels on the Dart side, in which case we could prevent the native exception from being thrown in the first place by...
When you say "clean up applications", do you mean explicitly uninstalling them from mobile devices/simulators?