4.0.1 (2019-03-26)
- ios: Fix autofocus on iOS 12.2 (#334) (cb4c491), closes #330
- account port on resolving uri path (#321) (fdfe8aa)
4.0.0 (2019-02-18)
- ios: Make iOS app Scheme configurable with a preference (#307) (d52d37e), closes #282
- ios: Remove WKSuspendInBackground preference (#309) (73b6659), closes #286
- ios: Remove the WKSuspendInBackground preference, so app relying on that prefere will not behave as expected
3.1.2 (2019-02-04)
- Android: Handle Range Requests for proper media file handling (#298) (6f18248), closes #248 #205 #141
3.1.1 (2019-01-18)
3.1.0 (2019-01-17)
- ios: Fix video playback of files with uppercase extension (#264) (2c4b225), closes #260
- Set engines to require Cordova CLI 7.1.0 or newer (#276) (40f42e1), closes #263
- Use a single scheme for all files (#270) (3d1bcdd), closes #258
3.0.0 (2019-01-03)
- Allows configuration of Mixed Content Mode (#240) (486d412), closes #231
- Android: Implement ionic-file and ionic-content urls (#242) (8ef0c30), closes #204 #183
- iOS: Remove GCDWebServer (#244) (0dee0cf)
- WebViewLocalServer.java: return 404 error code when a local file is not found (#217) (f7a551e), closes #216
-
iOS: Sets deployment-target to 11, so will only work on iOS 11+
-
Address changes
-
changes the default from 1 (never) to 0 (always)
-
WebViewLocalServer.java: Until now, the Android part of the plugin was returning a 200 http code even though the requested file didn't exist. This behavior was inconsistent with the historical behavior of the iOS webView. This change makes them both work in the same manner but introduces a breaking change for the current Android users that are expecting a 200 http code no matter what and are testing the not found error just by checking if the body is null.
2.3.1 (2018-12-06)
2.3.0 (2018-12-05)
2.2.5 (2018-11-20)
2.2.4 (2018-11-20)
2.2.3 (2018-11-09)
- Remove main and fix description (d52db66)
2.2.2 (2018-11-09)
2.2.1 (2018-11-07)
- Fix issue where two apps running on the same port could conflict with each other (#169 & #186)
- Add kitkat support (API 19) (#144) @leo6104
- Fix issue where local server was being used if launch URL is external (#169)
- Allow Ionic Deploy
DisableDeploy
preference to disable loading of deploy updates (#172)
- Make server path relative (#164)
- Return 404 response when file doesn't exist (#162)
- Load local assets if the app is a freshly installed binary (#155)
- Reset stored server path on new binary (#161)
- Allow range requests for local files (#154)
- Add support for
cordova-android
6 (#150)
- Fix nil reference by setting up the server URL before routes are set up. (#135) @matejkramny
- Resolve issue when app is launched in background. (#124) @ghenry22
- Immediately load new server base path upon setting it. (#132)
- Avoid "not modified" response on iOS by always overriding last modified date. (#127)
- BREAKING: HTTP server now runs for iOS and Android, instead of just iOS. The server is configured the same for both platforms.
- BREAKING: HTTP server now loads the app from a base href of
/
. The app URL behaves likehttp://localhost:8080/index.html
instead ofhttp://localhost:8080/Users/.../index.html
. - BREAKING: HTTP server is configured to run in HTML5 routing mode (push state) by default.
- BREAKING: File access through the Web View must be served by the HTTP server to avoid security errors in the Web View. Loading files via
file://
is not allowed by the Web View. The HTTP server will serve files via the_file_
prefix, e.g.http://localhost:8080/_file_/Users/.../file.png
. window.Ionic.normalizeURL()
has been deprecated. Usewindow.Ionic.WebView.convertFileSrc()
.- iOS update HTTP server to latest upstream version (GCDwebserve 3.4.2)
- iOS update HTTP server to restart sockets with error state when resuming from background
- iOS enable HTTP server to continue running in background if the webview is running.
- iOS enable Webview to continue running in background. Requires background mode capability enabled in xcode + valid use case as per app store requirements. If your app is not performing valid background tasks it will still be suspended by the OS as usual. As long as valid background tasks are running the webview will continue to function as expected.
- iOS add config.xml options:
- WKSuspendInBackground - defaults to true, if set to false then the webview and HTTP server will continue to run when the app is in the background or screen is locked
- WKPort - defaults to 8080, define the port that the HTTP server will listen on
- WKBind - defaults to localhost, if set to 127.0.0.1 then this IP will be used instead of the localhost hostname for the HTTP server
See Github releases for earlier changes.