@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.

I am trying to build out a custom debugger testing crosswalk for webRTC compliance. The build is successful (twice now), but it won’t deliver a file. Here is the last bit of the log:

BUILD SUCCESSFUL

Total time: 33.556 secs
Built the following apk(s): 
	/private/tmp/monaca/5a46698fe78885c81a8b4567/project/platforms/android/build/outputs/apk/android-debug.apk


- postBuild -
Built App Path: null
App File not found. null
Remove working directories...
Build Error: Error: App File not found. null

Edit: So removing Crosswalk fixes the issue. I rewrote the application to not need it but now have a new issue. Hopefully @Fran-Diox or @khemry will be able to chime in.

@timwd Have you checked out https://tutorial.onsen.io/?

@timwd Depending on the component, yes you can. For navigator, check the docs here:

https://onsen.io/v2/api/js/ons-navigator.html

I also highly recommend reading the API docs here:

https://onsen.io/v2/guide/fundamentals.html#attributes-properties-methods-and-events

@timwd said:

So, it’s not possible to have splitter and tabbar?

No, it absolutely is. I was showing you there are several tutorials on using tabbar with other components. You just have to follow them which is what @jamal provided.

@timwd In the dropdown of the tutorial site, are some common patterns. Although you want splitter and tabbar there is navigator and tabbar which is similar. http://tutorial.onsen.io/?framework=vanilla&category=common patterns&module=navigator_tabbar

@mmike If I was doing what you describe, I would have page B on init calling the function for the data, so that way on pop of C, I can just recall that function. There is no refresh option that you mention that I am aware of. Another option is to use resetToPage(‘b’). This basically pops everything down to A and then reloads B.