I have a release version cordova application and trying to stop a chrome remote debugging. I have set setWebContentsDebuggingEnabled(false) on webview but still it cant stop remote debugging on chrome:inspect. It is very strange that I have an app build in release version but chrome inspects still showing this application. Is there any way to block this feature and available only on demand?
Related
I have installed my android app in my device. But getting "Unfortunately, app has stopped."
How can I debug the installed app? Is it possible to debug the app directly installed in the device?
Since code is not available with me
You can't connect debugger to an application if it uses a release build type where all of the information necessary for debugging is stripped out
(true for apps from play market).
If you don't want to use a debugger but just to see logs you may see log in android studio or just by running adb logcat in terminal.
Android Studio 3.0 also has a feature of Profile and Debug Pre-built APKs but only if they were built with debugging enabled
I'm trying to debug a Cordova app by inspecting it remotely using the browser.
Per example, on my iPhone, I could access the webView by Safari Developer Menu, or in my Android, using Google Chrome chrome://inspect.
It works good when I install the app on the device by the CLI
cordova run ios
cordova run android
but, when I download the same app from the store, where I published it, I can't inspect it anymore, in fact I can't find it to inspect it in Chrome/Android nor Safari/iOs.
Is there a way to inspect the production app?
How am I supposed to debug it otherwise (e.g. the bug happens only in production)?
Thanks.
I didn't verified it on Cordova but I discovered it is possible to debug a production android app by adding
android:debuggable="true"
to the manifest as an <application> tag attribute.
It's no longer possible to upload a debuggable apk:
You need to enable debugging for webviews in android application.
if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.KITKAT) {
WebView.setWebContentsDebuggingEnabled(true);
}
add above code in main activity file.
more info about remote debugging :
https://developer.chrome.com/docs/devtools/remote-debugging/webviews/
Note : It is not recommended to turn on debugging on live playstore apps.
I have been using the Chrome remote device inspector to debug my Cordova app. The debug version of my app has been working fine without errors. However, now I made a signed APK for the first time, which installs and opens up, but hangs in a loading screen when try to use the login functionality in my app.
I believe this could be caused by some error in a plugin, or perhaps Google Maps Javascript API failing to load, but I cannot find out what it is because the Chrome debugging is disabled in a signed app. Is there any way I can turn on the debugging?
It turns out you can turn on debugging by adding android:debuggable="true" in AndroidManifest in manifest and application tags.
I'm building cordova apps using the phonegap build tool, but i can't debug it.
If I go to chrome inspect, I cannot see my application, even though I enabled the debug mode on my android phone and i already opened my app.
I'm making a todo list app, using meteor and cordova full code is at: github.
I've added an Android app version. Login is via accounts-password.
The server is running via nodejs with an nginx frontend.
The problem:
If I build the server with the android-platform then connect an android device to it the login buttons appear briefly but then the screen refreshes and they're gone and will not return unless the app cache is cleared.
If I build the server without the android-platform then it works fine. This happens with meteor run android (emulated). meteor run android-device and via loading an APK from the play store.
I assume what is happening is building the server with android platform results in a different version of the code being put on the server which then gets pushed to the phone when it connects.
But I have no clue how to debug this.