feat: Could we start with Capacitor 3.0 by fixing the existing issues in 3.0

[sundeepdev]

Feature Request

Could we start with Capacitor 3.0 by fixing the existing issues in 3.0

Description

Could we start with Capacitor 3.0 by fixing the existing issues in 3.0 considering that it has some major changes and has better structuring of core and plugins. That way it would be easy to merge the latest optimisation and fixes available in capacitor 3.0.
I'm not sure if you've done some R&D in fixing the Android issue reported in #4379. If it is a fixable thing, then it is better to fix it and fork from 3.0. Please share your thoughts. Appreciate all the hardwork.

Platform(s)

• iOS
• Android
• Web

[fkirc]

Yes I agree that Capacitor 3.X has a much better plugin-model.
Also, I guess that ionic-team/capacitor#4343 should not be too much effort to fix.
However, I observed too much instability right now and therefore I cannot upgrade to Capacitor 3.X right now (not only because of #4343).
But in a few months from now, it is clear that Capacitor 3.X will be the preferred choice.

[sundeepdev]

Got it @fkirc. I'm surprised to see so much instability as they mentioned Capacitor 3.0 RC was released and it would be in GA in few weeks.
Do you want to see the issues that you face in doing the upgrade and as they could also be due to the new structuring of the plugin. So they may need to be fixed as part of this repo if this repo supports Capacitor 3.0.

[fkirc]

I would like to build a beta-version of this project for Capacitor 3.X, but unfortunately I don't have the time for it right now.
If you are willing to step in, then I would be happy to mention your effort within the README.
Right now, the most pressing issue seems to be ionic-team/capacitor#4343, but I have not done a lot of Capacitor 3.X testing until now.