PhoneGap can't control what goes on regarding third-party plugins, so I would suggest reaching out to the plugin developers and filing an issue with them.
Understood but There must be a reason behind retiring existing plugins or is it j developer who does this?
what is reccomended in this case by phonegap to have smooth and consistent support for customers?
PGB users were notified over a year ago, and deprecation occurred a little more than a year after that initial notice. Here are the relevant posts:
- Notice of this deprecation was made on September 4, 2015: Deprecation of Public Plugins on PhoneGap Build
- Deprecation actually occurred on October 13, 2016: PhoneGap Build Public Plugin Repository Shutting Down
Given that plugins are now hosted on npm, whether a plugin is available on npm and whether or not it works correctly with PhoneGap Build is largely up to the plugin developer. The only plugins that PhoneGap maintains any control over are their own core plugins (e.g., phonegap-plugin-push). The core Cordova plugins are maintained by Cordova (e.g., cordova-plugin-device), but in both cases there are very few of these (about 20 or so core Cordova plugins, give or take). The vast majority of plugins are third-party, and as such, supported only by the third-party developer, which is why I suggested you file an issue with the plugin developer.
You might be able to install an older version of the plugin if the plugin developer published those to npm. Keep in mind that older versions of plugins might not work with newer versions of PhoneGap. You can see versions on npm using "npm info com.lampa.startapp versions" from the command line (which gives me [ '0.0.6', '0.0.7', '0.1.0', '0.1.1', '0.1.3', '0.1.4' ]).
Your best option for support (if an older version of the plugin doesn't work for you) is to contact the plugin developer. Their issues page is: Issues · lampaa/com.lampa.startapp · GitHub