To recap our hangouts meeting on this topic Sounds like the stance we are to take is to officially only support the cordova default target/compile sdk version (which is currently 29). Users can change this if they wish at their own risk. Norman Breau Software Developer
nor...@normanbreau.com (mailto:nor...@normanbreau.com) https://breautek.com On Oct 15 2020, at 6:05 am, Pieter Van Poyer <pieter.vanpo...@portofantwerp.com> wrote: > > Hi > > > I'd like to give my opinion. Because the discussion about the sdk version was > with me. > > I don't like to disagree with Norman, but the problem with the CameraPlugin > was IMO not with the targetSdkVersion. I could lower the targetSdkVersion to > 22 without any problems. > > The problem was with the compileSdkVersion. > I was not able to use a constant available in android 28 > (Build.VERSION_CODES.P, if I am right), because Norman suggested it would be > able to compile with android level 22. > So I did change it to the numerical 28 . > > > > > > > So IMO, there may be more guidelines > About the targetSdkVersion. Not sure about that one. ( > https://developer.android.com/guide/topics/manifest/uses-sdk-element.html#target > ) > About the compileSdkVersion (only support officially the one used for > cordova-android – 29). > With using the latest compileSdkVersion and skipping the previous (now 22 – > 28), plugin developers can use the features from api 29. > > > > > And for a plugin, this settings must indeed be based on the supported cordova > (-android) version of that plugin. It must indeed be able to run on the > defaultMinSdkVersion for the supported cordova-android versions. > > Kind regards > Pieter Van Poyer > > -----Oorspronkelijk bericht----- > Van: julio cesar sanchez <jcesarmob...@gmail.com> > Verzonden: donderdag 15 oktober 2020 00:39 > Aan: dev@cordova.apache.org > Onderwerp: Re: Minimum Target SDK > > > > Despite we allow users to configure the target SDK, I don’t think we should > allow other than the default on latest cordova-android. > > By allow I mean on issues, users are free to use whatever they want, but if > they don’t use latest they should take care of possible problems themselves. > With that being said, camera plugin requires latest cordova-android, so that > means target sdk 29. > > But also we need to have in mind that if the plugin allowed older > cordova-android versions and we add some code that requires a higher sdk than > the default on that cordova-android version we should bump the dependency to > the version that targets that sdk as default. > > BTW, sdk 29 is already a requirement for new apps since August, November is > for existing apps. > > El El mié, 14 oct 2020 a las 23:46, Norman Breau <nor...@normanbreau.com > (mailto:nor...@normanbreau.com)> > escribió: > > > Hi team, > > > > A recent discussion came up about what the minimum Target SDK we > > should support. Google enforces apps to be built with at least Target > > SDK 28 (soon to be 29 coming November), but Cordova users may not be > > publishing to the Google Play store, particularly with enterprise > > businesses with internal distribution systems. > > This is currently not documented and I would like it to be documented > > because we were close to merging a PR that would make the camera > > plugin require Target SDK 28. But before I submit a documentation PR I > > would like some feedback on what our minimum Target SDK should be. > > Logically I think it makes the most sense to say that whatever what > > our Minimum SDK level is should be our minimum supported Target SDK > > (which is currently 22 for cordova-android@9). > > For clarity because terminology here is a little confusion: > > Minimum SDK = The minimum supported OS Target SDK = The SDK level used > > to compile an app. > > > > Norman Breau > > Software Developer > > > > nor...@normanbreau.com (mailto:nor...@normanbreau.com) ( > > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flink > > .getmailspring.com%2Flink%2FC6CAC914-84D1-430D-9FD4-ACD8F2BCDEB2%40get > > mailspring.com%2F0%3Fredirect%3Dmailto%253Anorman%2540normanbreau.com% > > 26recipient%3DZGV2QGNvcmRvdmEuYXBhY2hlLm9yZw%253D%253D&data=04%7C0 > > 1%7CPieter.VanPoyer%40portofantwerp.com%7Cecf599a37cc34aa15b0908d87091 > > fc11%7C2337dcc63a214d95bf72da5551a9b048%7C0%7C0%7C637383119593982450%7 > > CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1 > > haWwiLCJXVCI6Mn0%3D%7C1000&sdata=p5d0xNO3r2jfgXWzReOH%2Fannd0WAln3 > > VilI68tFngyY%3D&reserved=0 > > ) > > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbrea > > utek.com%2F&data=04%7C01%7CPieter.VanPoyer%40portofantwerp.com%7Ce > > cf599a37cc34aa15b0908d87091fc11%7C2337dcc63a214d95bf72da5551a9b048%7C0 > > %7C0%7C637383119593982450%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAi > > LCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=jERwWv > > Q8Kr04RoFF6NReZLtVZCpixqaRG%2FVL%2B0A4PeU%3D&reserved=0 ( > > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flink > > .getmailspring.com%2Flink%2FC6CAC914-84D1-430D-9FD4-ACD8F2BCDEB2%40get > > mailspring.com%2F2%3Fredirect%3Dhttps%253A%252F%252Fbreautek.com%26rec > > ipient%3DZGV2QGNvcmRvdmEuYXBhY2hlLm9yZw%253D%253D&data=04%7C01%7CP > > ieter.VanPoyer%40portofantwerp.com%7Cecf599a37cc34aa15b0908d87091fc11% > > 7C2337dcc63a214d95bf72da5551a9b048%7C0%7C0%7C637383119593982450%7CUnkn > > own%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwi > > LCJXVCI6Mn0%3D%7C1000&sdata=AJa8kuv5udNUDlX2%2Bpm3jMHvoAMxMAPRgfrs > > jXvfT9I%3D&reserved=0 > > ) > > > > > > Deze e-mail en alle gekoppelde bestanden zijn officiele documenten van > Havenbedrijf Antwerpen NV van publiek recht en kunnen vertrouwelijke of > persoonlijke informatie bevatten. Gelieve de afzender onmiddellijk via e-mail > of telefonisch te verwittigen als u deze e-mail per vergissing heeft > ontvangen en verwijder vervolgens de e-mail zonder deze te lezen, te > reproduceren, te verspreiden of te ontsluiten naar derden. Havenbedrijf > Antwerpen NV van publiek recht is op geen enkele manier verantwoordelijk voor > fouten of onnauwkeurigheden in de inhoud van deze e-mail. Havenbedrijf > Antwerpen NV van publiek recht kan niet aansprakelijk gesteld worden voor > directe of indirecte schade, verlies of ongemak veroorzaakt als gevolg van > een onnauwkeurigheid of fout in deze e-mail. > English Translation: This e-mail and all attached files are official > documents of Antwerp Port Authority and may contain confidential or personal > information. If you have received this e-mail in error, you are asked to > inform the sender by e-mail or telephone immediately, and to remove it from > your system without reading or reproducing it or passing it on to other > parties. Antwerp Port Authority is in no way responsible for any errors or > inaccuracies in the contents of this e-mail, nor can it be held liable for > any direct or indirect loss, damage or inconvenience arising from any such > errors or inaccuracies.
