I am not very familiar with Python, but any project that converts Python to JavaScript should work for Onsen UI, since it is just plain JavaScript.

We will need the full error message as this does not currently give enough information.

You can also try contacting Monaca Support Team if you have a paid plan.

You can try listening for the page’s init event.

See here for more details of a case where a user had the same flickering problem:
https://community.onsen.io/topic/3568/page-beforeshow-event

I’m not sure whether this is a quirk of Monaca Debugger (although I don’t think so) or to do with the library code you are using to load the picture. Maybe you can try one of the examples here and check if it works for your case:
https://github.com/apache/cordova-plugin-camera#sample-take-pictures-select-pictures-from-the-picture-library-and-get-thumbnails-

Can you try running your app in the Preview window in Monaca Cloud IDE and then checking the network tab of your browser’s debug tools? There you should be able to see the request and response in full.

Also, this might be relevant if you’re using Android:
https://en.docs.monaca.io/reference/power_plugins/in-app_updater#notes-on-android-9+

The tabbar is currently not written in a way that allows for dynamically added tabs. This is something that we are considering for a future release but unfortunately it is not possible right now with the plain JS version of Onsen UI.

Since you are on Pro plan, it might be easiest to open a support ticket with Monaca Support Team. They will be able to access your project and debug it. From the information you provided here it’s not possible to say what the problem is. If you need further help, please let us know.

There is nothing like this in Onsen UI as far as I know. Actually, I’m not sure what you would call this effect either. Can you tell me what app uses this effect as an example?

If the plugin variable is undefined, check the following:

1. The plugin is being installed during the build. You should see it in the build log.

2. You are accessing the plugin variable after the deviceready event. You can make sure of this by adding an event listener and using the plugin variable in the callback function e.g.:

document.addEventListener(‘deviceready’, () => {
// call the variable here
});

3. You are calling the correct variable. You can verify the correct variable by going to the plugin’s plugin.xml file (usually available on the plugin’s GitHub page) and checking the target of the clobbers tag e.g.:

<clobbers target=“FirebasePlugin” />

This means the variable is window.FirebasePlugin.

4. If you are using Monaca Debugger, make sure you are using a Custom Build Debugger, not the App Store version of the Debugger. The App Store version only includes the core plugins, not third-party plugins, so you need to create a Custom Build Debugger by selecting the ‘Custom Build Debugger’ option from the Build for iOS or Build for Android page. This will create a version of Monaca Debugger with all your project’s plugins.

Unfortunately it doesn’t seem there is much that can be done about it from the user-end. I meant that if you manually split the lines (so you don’t have very long lines), it shouldn’t be a problem - is that the case?