If users do extra initialization, we can get NPEs when hitting the back
button before loadUrl() has been called.
-Null fenced code in startOfHistory() that gave us an NPE when hitting
Back button with useBrowserHistory=true
-Call finish() in Back button code when no history since with
useBrowserHistory=true it would just hang while the app inits
-Call loadUrlIntoView() first in handleDestory() since with
useBrowserHistory=false, the default behavior would try to use the baseUrl
which is null
I installed the android sdk via homebrew, which does not install any build targets by default.
That resulted in the create throwing the following somewhat cryptic error.
An unexpected error occurred: "$ANDROID_BIN" create project --target $TARGET --path "$PROJECT_PATH" --package $PACKAGE --activity $ACTIVITY >&/dev/null exited with 1
This just adds a check that the variables that are set to the values of the build targets are properly set, and exit if they are not.
This is mostly the same as FILE_URI on Android.
Also replaced calls to `stripFileProtocol` with the more general-purpose `getRealPathFromURI`. This helps support some operations on content URIs.
- Fix warnings about toLowerCase()
- Don't assume connections are HTTP (fails for file://)
- Use StringBuilder
- Remove no-ops of disconnect() & keep-alive
* Moved Config.init call into DroidGap for the most common use-case
* The CordovaWebView docuemntation still has to be updated
* The template has to be changed, since we don't want to have two different types of config
- Removed BinaryEcho; made Echo support a new binaryEcho action.
- Added CordovaArgs wrapper for JSONArray, and a new overload for
execute that accepts a CordovaArgs. There is now a default
implementation for the JSONArray version of execute that builds a
CordovaArgs and calls that version of execute. The default
implementation for the CordovaArgs execute is to return false.
- Added byte[] version of success() in CallbackContext.
