@rajdevwilson0991 Are you the same user who sent us a support ticket regarding the same issue under Frank De Smedt name? If so, we have replied back to your ticket since October 17th with a backup version of your project as well. Please check it out. I’ve just replied back to you again today. Sorry for the inconveniences.

@rajdevwilson0991 Are you the same user who sent us a support ticket regarding the same issue under Frank De Smedt name? If so, we have replied back to your ticket since October 17th with a backup version of your project as well. Please check it out. I’ve just replied back to you again today. Sorry for the inconveniences.

@khemry, finally a success.
I created a new app in Monaca Local Kit, then compared various folders with my troublesome project.
I replaced the www\lib folder with the files from the new project.
Then noticed that in package.json dependencies that “monaca-plugin-monaca-core” was not the latest, so I changed to “monaca-plugin-monaca-core”: “3.2.1”, then uploaded the app to Monaca IDE, and viola!
Jamal

@khemry That indeed resolves the delay, however how’s that not a bug? The content of Plugins folder should be just like other files, be compared and uploaded when necessary, why’s it taking so much time when they’re there?
p.s.
How did you derive the conclusion that most plugins aren’t being used? Two or three are being experimented with and the rest are used.

@wilsonmfg The latest recent update of MonacaBackend plugin is related to build issues with some Cordova plugins only. There are no changes to the Backend configuration or Backend APIs. Therefore, you don’t need to change anything. However, I still recommend to rebuild your app using the latest version of MonacaBackend plugin.

@rmoore It seems like you are using Firebase plugin or PushPlugin in your project. These plugins requires Firebase configuration files (google-servcies.json & GoogleService-info.plist` files). You need to get these files from Firebase and upload them at the root of your project. Read more here.

@flavio For Android debug and custom debugger builds, a dummy keystore is used. The keystore is always the same. When you got the error Android App Not Install..., did you try to install two different types of builds (debug & custom debugger) on the same device? Normally, if you try to install the same build, there should not be such error.

@khemry So I’m running development fine for the project in Visual Studio. It’s not anywhere nice a Monaca but I save $500.
You’ve also potentially lost sales. I picked the project up for an overstretched app developer studio with 4 or 5 developers. If I had been able to use Monaca then they’d have seen the app running in the debugger by way of demonstration. As it is, they won’t.
The ability to run all plugins - or at least many more of the common ones such as encryption and purchase - should be standard with all paid versions. It may seem like you’re forcing people to upgrade, but with your current price structure they’ll just go elsewhere. It’s not like anyone has to develop in Monaca, there’s plenty of alternatives - but what you do have is very sleek. Just not $500 pa worth of sleek.

@anupriya-wdev Currently, there is a synchronization issue between Monaca Debugger and Localkit. We are working on it now. You can see the live status of this issue here. We are sorry for the inconveniences and thank you for understanding.

@rajkaran Currently, there is a synchronization issue between Monaca Debugger and Localkit. We are working on it now. You can see the live status of this issue here. We are sorry for the inconveniences and thank you for understanding.