@gb Can you post your JS code?

@gb All products are in continuous development. The forums have died down significantly with the exit of their community relations manager. The discord is more active, but still its community driven. Regardless, Onsen is open source so you will always have the product. Asial, the parent company, is very much alive.

Is there anyway or can it be added to disable the file docking? Currently, if I double-click by accident on the tab with the file I am working on, it switches doc position which drives me nuts. I would love if I could toggle this off in the workspace configuration page.

@matthewk5 Just use:

.tabbar__badge.notification {
background-color: blue;
}

@munsterlander Solved: https://stackoverflow.com/questions/57838790/camera-works-in-monaca-debugger-but-not-in-debug-build/57847276#57847276

So, I am working on a new app that uses the camera for real-time video OCR. Anyway, the app works great in the Monaca debugger. When I then do a debug or release build, the camera will not work. Upon initial load, the app prompts to allow camera but the permission response is permanently denied even after hitting allow. I have tried the Android permissions plugin, diagnostics plugin, and the custom config plugin, but neither can get around this. I remember we encountered this once before, but I cannot remember the solution. Does anyone have an idea?

@khemry While in general I agree, I am confused though as to why it works on CodePen, for example, this very basic example: https://codepen.io/munsterlander/pen/rWWvNN

@khemry If you are looking at the current project, it is significantly different as I had to work around that error. The current code base was set for export so I could do a local cordova build and consequently the splash screen images are different.

@Faisal-Naseer It should be outside of the ons-ready function. Here is a working example: https://codepen.io/munsterlander/pen/JWvNRX

So based on the other thread, but completely different. I have figured out the issue. Doing a release build is removing the CAMERA permission in the AndroidManifest.xml. I am using this in the config.xml:

<preference name="android-manifest/uses-permission/[@android:name='android.permission.CAMERA']/@android:name" delete="true" />
<preference name="android-manifest/uses-permission/[@android:name='android.permission.READ_EXTERNAL_STORAGE']/@android:name" delete="true" />

READ_EXERNAL_STORAGE makes it into the APK, but not camera. I verified this by decompiling the APK.

I have confirmed this is an issue with Monaca remote build and the custom config plugin. Although the Monaca docs state the aforementioned code will work, the docs for the plugin state that remote builds will fail. Not certain the exact cause here, but I did a straight Cordova local build with the exact same plugins minus the Monaca ones and doing a release build works exactly like it is supposed too.

Since I am using navigator.mediaDevices.getUserMedia as I need webRTC access, I am using this plugin to request permissions at runtime: https://github.com/dpa99c/cordova-diagnostic-plugin. There is some issue with the remote build and custom-config plugin that is removing the camera permission but not the others. Interesting bug none-the-less and local building with a traditional cordova project solves the issue.