Replies: 2 comments 1 reply
-
Here you can find the Capacitor Support Policy which should answer some of your questions: https://capacitorjs.com/docs/main/reference/support-policy |
Beta Was this translation helpful? Give feedback.
1 reply
-
Google requires to target the latest SDK every year by August, Capacitor major versions are created to properly target the latest SDK before the google deadline. While you could not update the capacitor version and only change the targetSDK version in your app, that always cause issues on some plugins when running in Android 13 devices if they need new code to properly work there. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Obviously we need to keep software up-to-date for many reasons. But when you have a number of community plugins that may not be supported in the latest version of capacitor, you have to weigh the tradeoffs.
I would like to suggest the capacitor team give us the main reasons and benefits for each major update, so we can determine the priority of doing upgrade work in our apps, and which breaking changes we may not be able to support. And also if we need the latest version to support the latest iOS/Android. Thanks!
Beta Was this translation helpful? Give feedback.
All reactions